Skills
96,770 packaged capabilities and playbooks for agents. Install any of them with one command.
Documents
Creates and manages developer-focused presentations using Slidev, a markdown-based presentation framework. Helps with creating slides, adding code examples, diagrams, animations, and exporting to various formats (PDF, PPTX, PNG). Ideal for technical talks, code demos, and developer documentation presentations.
Tabular review — one row per document, one column per data point, every cell citing its source. Built for M&A diligence ("review these 200 target contracts for change-of-control, assignment and MAC clauses"), but works for any bulk review that needs to produce a spreadsheet. Use when the user says "tabular review", "review grid", "build a grid", "extract these fields from these contracts", "review these documents for X, Y, Z", "give me a spreadsheet of...", "bulk review", or points at a folder and asks for a comparison.
Draft "notice-and-takedown" notices (under the Regulations on the Protection of the Right to Network Dissemination of Information), triage received notices, or draft counter-notices. Use when asserting rights via a copyright notice and needing to verify statutory fair use circumstances and the authenticity of the notice, when a received notice must be triaged into accept/counter-notice/negotiate/no action for now options, or when a counter-notice complying with Chinese law requirements must be drafted.
Create, inspect, and edit Microsoft Word documents and DOCX files with reliable styles, numbering, tracked changes, tables, sections, and compatibility checks. Use when (1) the task is about Word or `.docx`; (2) the file includes tracked changes, comments, fields, tables, templates, or page layout constraints; (3) the document must survive round-trip editing without formatting drift.
Write or overhaul a project's README.md, drawing on patterns from the most-starred GitHub readme-template repos and guides (othneildrew/Best-README-Template, the standard-readme spec, makeareadme.com, awesome-readme). Use this whenever the user asks to write, create, improve, restructure, or "make my README look better/more professional", asks for a README for a library/CLI/API/app, asks about badges/shields, a table of contents, "getting started" or "installation" sections, a Support or Project Status section, or wants their GitHub profile README (the special username/username repo) polished. Covers picking the right template variant (library, CLI tool, application, monorepo, or profile README), section ordering, badge selection, and common mistakes that make READMEs look templated or get skipped by readers.
Comprehensive spreadsheet creation, editing, and analysis with support for formulas, formatting, data analysis, and visualization. When Claude needs to work with spreadsheets (.xlsx, .xlsm, .csv, .tsv, etc) for (1) Creating new spreadsheets with formulas and formatting, (2) Reading or analyzing data, (3) Modify existing spreadsheets while preserving formulas, (4) Data analysis and visualization in spreadsheets, or (5) Recalculating formulas
A complete coaching skill for Taiwanese nurses writing evidence-based nursing reports (evidence-based reading reports, evidence-based case analyses), designed for N1–N4 promotion in the nursing clinical ladder system and for the review formats of the Taiwan Nurses Association and the Taiwan Evidence-Based Nursing Association. Trigger this skill whenever the user mentions "實證護理報告", "實證案例分析", "實證讀書報告", "N2 報告", "N3 報告", "N4 報告", "護理進階報告", "護理升等", "PICO", "5A 步驟", "CASP 評讀", "護理 EBP", "EBN", "evidence-based nursing", "實證照護", "證據等級", "文獻評讀", or whenever a nurse asks about promotion writing, turning a clinical question into an evidence-based topic, evidence search strategies, CASP appraisal forms, Oxford levels of evidence, APA 7th edition format, applying an evidence-based intervention to a case, challenging nursing routines, or dispelling nursing myths. Even if the user only casually asks "我要寫報告", "我要升 N3", "幫我找主題", "幫我設 PICO", or "這篇文獻要怎麼評讀", you should proactively activate it to provide complete structure, sentence patterns, and writing strategies with the highest review pass rate.
Generate professional slide deck images from content. Creates comprehensive outlines with style instructions, then generates individual slide images. Use when user asks to "create slides", "make a presentation", "generate deck", or "slide deck".
Template-based routine client letters — appointment confirmations, document requests, "filed" briefs. Plain language, required elements, supervision routing. No substantive advice. Use when a student needs to send a routine letter, appointment confirmation, document request, or a short status note to a client.
Synthesize due diligence findings into audience-appropriate deal team briefings — executive summaries for leadership, working summaries for the team. Use when the user says "brief the deal team", "where does diligence stand", "summarize findings for [audience]", "deal update", or on a briefing cadence.
Professional diagram generation skill: automatically selects the appropriate chart type based on the requirement and generates PNG charts that conform to the design spec. Covers 29 chart types: structural diagrams (flowchart, swimlane diagram, sequence diagram, architecture diagram, state diagram, ER diagram, class diagram, mind map, Gantt chart, Kanban, Git Graph, etc.) and statistical charts (bar chart, line chart, pie chart, radar chart, heatmap, scatter plot, Sankey diagram, funnel chart, waterfall chart, treemap, bar-line combo chart, etc.). Unified toolset: HTML/SVG + inline JS layout computation. ER/class diagrams use the ELKjs layout engine. All charts follow a unified design spec (color/font/component/spacing) with a modern, clean style. Supports three outputs: PNG (default), HTML (rich document embedding), DSL (Mermaid text, embedded in MD documents). Trigger words: draw a diagram, draw one, generate a chart, flowchart, architecture diagram, sequence diagram, bar chart, comparison chart, relationship diagram. Even if the user does not say "draw a diagram", this skill should trigger whenever the request involves visual presentation (process, architecture, data comparison, relationships). When called by other skills such as deep-research, it likewise follows this spec to generate diagrams.
Guide users through a structured workflow for co-authoring documentation. Use when user wants to write documentation, proposals, technical specs, decision docs, or similar structured content. This workflow helps users efficiently transfer context, refine content through iteration, and verify the doc works for readers. Trigger when user mentions writing docs, creating proposals, drafting specs, or similar documentation tasks.
Comprehensive patterns for AI-powered document understanding including PDF parsing, OCR, invoice/receipt extraction, table extraction, multimodal RAG with vision models, and structured data output. Use when "document parsing, PDF extraction, OCR, invoice processing, receipt extraction, document understanding, LlamaParse, Unstructured, vision document, table extraction, structured output from PDF, " mentioned.
Comprehensive document creation, editing, and analysis with support for tracked changes, comments, formatting preservation, and text extraction. When Claude needs to work with professional documents (.docx files) for: (1) Creating new documents, (2) Modifying or editing content, (3) Working with tracked changes, (4) Adding comments, or any other document tasks
Review a DPA against your playbook — automatically detect whether you are the processor or the controller and apply the correct half of the playbook. Use when the user says "review this DPA", "check this data processing addendum", "a client sent us their DPA", "is this DPA okay", or attaches a DPA.
Diff proposed policy changes against the current version, flagging knock-on effects and provincial supplementary clause impacts. Use when the user says "update the policy", "add this to the policy", "policy change", or a policy is ready to be incorporated.
Write HLD, High-Level Design, 写技术设计文档. Use when: system architecture design, technology selection, and technical solution definition are needed after the PRD and API Contract are complete. Also used for limited incremental updates to existing related documents.
Remove signs of AI-generated writing from academic medical papers. Use when editing or reviewing manuscripts to make them sound more natural and professionally written. Based on Wikipedia's "Signs of AI writing" guide, adapted for medical literature. Detects and fixes patterns including: inflated significance claims, superficial -ing analyses, vague attributions, AI vocabulary words, copula avoidance, excessive hedging, generic conclusions, informal word choices (linked/beyond/via/where/yield), overly assertive causal claims, and artificially condensed expressions. Preserves legitimate academic transitions (Notably, Prior studies have shown, etc.).
Draft audience-specific summaries from an investigation memo — an HR version, a management version, or an outside-counsel version. Use when the investigation memo needs to reach audiences that should not see the full confidential work product.
Automatically organizes invoices and receipts for tax preparation by reading messy files, extracting key information, renaming them consistently, and sorting them into logical folders. Turns hours of manual bookkeeping into minutes of automated organization.
Comprehensive toolkit for preparing ISO 13485 certification documentation for medical device Quality Management Systems. Use when users need help with ISO 13485 QMS documentation, including (1) conducting gap analysis of existing documentation, (2) creating Quality Manuals, (3) developing required procedures and work instructions, (4) preparing Medical Device Files, (5) understanding ISO 13485 requirements, or (6) identifying missing documentation for medical device certification. Also use when users mention medical device regulations, QMS certification, FDA QMSR, EU MDR, or need help with quality system documentation.
Transform text content into professional Mermaid diagrams for presentations and documentation. Use when users ask to visualize concepts, create flowcharts, or make diagrams from text. Supports process flows, system architectures, comparisons, mindmaps, and more with built-in syntax error prevention.
Implicit use requires an explicit or already-established Nature Portfolio context. Simulate a pre-submission referee assessment of a supplied full or partial manuscript, abstract, or manuscript package, with reports and a synthesis on novelty, significance, rigor, evidence, reproducibility, and readability. Within that scope, use for 模拟审稿、投稿前自审 or reviewer report. Do not draft real rebuttals, polish prose, or perform a statistics-only reporting audit
Generate presentations in NetEase Red + White (网易红) style as both HTML slides and PPTX files. Use when user says "红白风格PPT", "网易红演示", "红白slides", "netease red slides", "做个红白PPT", "做个红白HTML演示", or wants to create presentations matching the NetEase brand aesthetic (red D51312, RGB 213/19/18 + white, Swiss Modern style with diagonal clip-path accents). Supports two output formats: interactive HTML (with animations, nav, inline editing) and static PPTX (via PptxGenJS). Can generate both from the same content.
Build or extend a course knowledge outline from class notes and textbooks in your format. Provides the scaffolding — it does not write the outline for you. Use when the user says "outline [subject]", "add to my outline", "build an outline from [material]", or points to class materials.
Use when user wants to create a full slide deck or presentation using PaperBanana image generation, OR modify/regenerate an existing PaperBanana slide deck, OR build an editable PPTX with native text/tables/charts. Triggers on "make slides", "create presentation", "PPT", "slide deck", "regenerate slides", "update slides", "paperbanana slides", "editable PPTX", "editable slides". Also triggers when user has an existing slide-deck directory with outline.md and wants to regenerate images or make changes. This is the PRIMARY slide deck skill — always prefer over baoyu-slide-deck.
Generate a Personal Information Protection Impact Assessment (PIA) in an internal format for new features, products, or processing activities, using the structure learned from seed PIAs. Use when the user says "write a PIA," "personal information protection impact assessment," "do we need a PIA for this," "do a privacy review for this feature," or describes a new personal information processing activity.
Keep personal information processing rules aligned with practice. Two modes: a weekly scan of saved PIAs, DPA reviews, and triage results to find processing rule drift; or a direct query against proposed new practices. Use when the user asks "do our processing rules cover this," "we want to start doing X — do the processing rules need updating," "run the processing rule monitor," "processing rule scan," or wants to find where the processing rules no longer match what the team actually does.
Produce a proposed policy revision (marked-up version) that closes a gap. Triggered by a gap found by /regulatory-legal:gaps or /regulatory-legal:policy-diff. A first draft for internal review — not applied directly to the approved policy document. Use when the user says "rewrite the policy", "draft a policy fix", "mark up the policy", or gap-surfacer passes over a gap for drafting.
Use this skill any time a .pptx file is involved in any way — as input, output, or both. This includes: creating slide decks, pitch decks, or presentations; reading, parsing, or extracting text from any .pptx file (even if the extracted content will be used elsewhere, like in an email or summary); editing, modifying, or updating existing presentations; combining or splitting slide files; working with templates, layouts, speaker notes, or comments. Trigger whenever the user mentions \"deck,\" \"slides,\" \"presentation,\" or references a .pptx filename, regardless of what they plan to do with the content afterward. If a .pptx file needs to be opened, created, or touched, use this skill.
Professional product requirements document (PRD) writing assistant. Used to turn product requirements into clearly structured, complete PRD documents. **Use cases:** (1) writing requirements documents for new product features (2) requirements documents for optimizing existing features (3) turning user stories into PRDs (4) quickly generating a PRD draft. **Trigger words:** "写PRD", "生成PRD", "产品需求文档", "PRD文档"
Write product requirements documents (PRD) and generate interactive prototypes. Triggered when the user mentions "需求文档", "PRD", "产品需求", "写需求", "原型", "feature list" and similar keywords. Integrates the UI-UX-Pro-Max design system and supports Cloudflare Pages deployment.
Surface internal contradictions, conflicting requirements, and edge cases that expose hidden conflicts in a document, spec, plan, design, or set of requirements. Use when something feels off but you can't pinpoint why, before committing to a design, or when requirements have grown incrementally and may have drifted out of sync. TRIGGERS: 'consistency check', 'find contradictions', 'does this spec make sense', 'check for conflicts', 'something feels wrong here', reviewing requirements docs, technical specs, architecture plans, product briefs, or any document where internal coherence matters.
New to MCP?
From what the protocol is to installing your first server, these answers cover most first questions.
An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.