Skills
96,770 packaged capabilities and playbooks for agents. Install any of them with one command.
Documents
Downloads YouTube video transcripts/subtitles and cover images by URL or video ID. Supports multiple languages, translation, chapters, and speaker identification. Caches raw data for fast reformatting. Use when the user asks to “get YouTube transcript”, “download subtitles”, “get captions”, “YouTube字幕”, “YouTube封面”, “视频封面”, “video thumbnail”, “video cover image”, or provides a YouTube URL and wants the transcript/subtitle text or cover image extracted.
HTML PPT Studio — author professional static HTML presentations in many styles, layouts, and animations, all driven by templates. Use when the user asks for a presentation, PPT, slides, keynote, deck, slideshow, “幻灯片”, “演讲稿”, “做一份 PPT”, “做一份 slides”, a reveal-style HTML deck, a 小红书 图文, or any kind of multi-slide pitch/report/sharing document that should look tasteful and be usable with keyboard navigation. Triggers include keywords like “presentation”, “ppt”, “slides”, “deck”, “keynote”, “reveal”, “slideshow”, “幻灯片”, “演讲稿”, “分享稿”, “小红书图文”, “talk slides”, “pitch deck”, “tech sharing”, “technical presentation”
AI-driven presentation workflow for generating editable PPTX decks and slides, reconstructing page visuals, creating reusable Brand/Style/Layout/Deck workspaces, filling native PPTX templates, and enhancing finished PPTX files. Use when the user asks to create, generate, reconstruct, regenerate, beautify, redesign, template, fill, or enhance a presentation, PPT, PPTX, slide deck, or courseware — including adding narration or animation to one — requests a presentation-authored narrated/self-running video, or mentions ppt-master
WeCom Smart Sheet content operations skill—focused on managing smart sheet (smartsheet) data, structure, and styles: read table structures and records; manage subtables, fields, records, views, and charts; and modify row and column styles (fill colors/highlights). If adding or updating records fails with 851003 / no authority, use Webhook as a fallback for writing. Trigger when the user mentions smart sheets, WeCom sheets, smartsheet content operations or style changes, or a link like https://doc.weixin.qq.com/smartsheet/s3_xxx. WeCom sheets come in two types: “Smart Sheets” and “Online Sheets”; this document covers skills for Smart Sheets. Smart Sheets contain subtables (sheet), views (view), and fields/columns (field). Each record uses `record_id` as its primary key, with a structure similar to a relational database. Unless the user explicitly specifies “Online Sheets,” default to the more capable Smart Sheets (this skill).
Use when writing, restructuring, or revising technical documents—specs, design docs, READMEs, reference documentation, plans, reports—or any prose that must survive being read twice by someone in a hurry. Encodes the house style, truth and sourcing rules, and banned-constructions list. Use whenever you produce repository-bound text longer than a paragraph, even if nobody says “document.” Foundation for the sibling document-type skills
Set up, write, and publish documentation sites with Mintlify, and work on existing Mintlify projects. Use when the user wants to create a docs site for a repo or product, turn a docs/ folder or README into a hosted docs site, document an API from an OpenAPI spec, migrate docs from Docusaurus, GitBook, ReadMe, Fern, or another platform, preview docs locally, or publish docs to a shareable URL. Also use when editing a project with docs.json, including pages, navigation, components, API references, and customizing appearance or browser behavior with CSS, JavaScript, React, and snippets.
Use when writing a proposal, RFC, design document, spec, or migration plan—anything that argues for a change, records a design, or asks readers for input on one. Encodes the proposal skeleton, the Why & What decision box, and the completeness checks. Use whenever a change needs arguing or scoping in writing, even if the user just says “write up the approach.”
Use when reviewing, rewriting, or editing someone else's technical text, writing a review report on a document, or performing the final check before delivering any document. Encodes the severity mapping, findings format, what-not-to-flag list, and delivery checklist. Use before any document ships, even when it looks fine
Use when writing operational documentation—runbooks, setup guides, release procedures, migration guides, deprecation guides, troubleshooting entries, or any ordered procedure someone will execute under time pressure. Encodes the runbook skeleton, risk legend, symptom-first troubleshooting format, and migration-guide rules (mapping table, mandatory rollback, deprecation dates, built-in expiry). Use whenever someone will execute the text, even if it is called a “guide” or “setup notes.”
Use when writing a changelog entry, release notes, or a “what shipped” summary after completing work. Encodes the entry structure, handover template, and honesty conventions. Use after shipping meaningful work, even if the user just says “summarize what we did.”
Use when writing a postmortem, incident report, or root-cause analysis after an outage, a defect that reached users, a data issue, or a near miss—or when turning an incident channel, alert log, or war-room thread into a durable document. Encodes blameless framing, an evidence-only timeline, contributing factors, and owned action items. Use whenever something broke and the write-up must outlive the incident
Use when a decision needs recording—an ADR, a decision log entry, or a request to document why something was chosen, rejected, or superseded. Encodes ADR and decision-log formats. Use whenever a choice was made that would otherwise live only in chat, even if nobody says “ADR.”
Use when writing or refining tracker items—epics, stories, tasks, bug reports, spikes, or acceptance criteria—or turning a discussion, review finding, or plan into tickets. Encodes the survives-without-you test, issue-type glossary, and story and bug skeletons. Use whenever work is written into a tracker, even from a rough verbal dump
Use when documenting an existing codebase whose documentation is missing, stale, or untrusted—an inherited system, a legacy application, or a repo where the docs lie—or when aligning a documentation tree with the code, or when someone asks what a system actually does. Encodes the survey-first inventory, writer-side evidence hierarchy, depth-per-surface rules, refactor test, dead-or-alive proofs, quirks-and-findings split, coverage ledger, parallel campaign, and docs-tree skeleton. Use whenever documentation must be reconstructed from code rather than written alongside a change.
Use when a business process, workflow, lifecycle, or interaction between systems needs a diagram — a flow that prose serializes badly, a state machine, a message sequence, an enterprise process map — or when drawing the process documentation of a legacy campaign. Encodes diagrams-as-source, the notation ladder from ArchiMate to PlantUML, the kind-per-question table, behavior-level participants, the diagram index, and the same-change maintenance rule. Use whenever a document needs a graph rather than more paragraphs, even if nobody says "PlantUML".
Use when documenting an HTTP API, message payloads, queue contracts, DTOs, file formats, or webhooks — or when writing the api-reference of a legacy campaign, or when callers keep asking what a field means or which errors an endpoint returns. Encodes the four detail levels, the DTO-first catalog, wire types with source anchors, the generated-spec one-home rule, and omitted-versus-null semantics. Use whenever a machine interface needs documenting for its callers, even if nobody says "API docs".
Convert Markdown into HTML that can be pasted into the WeChat Official Accounts backend, with 15 built-in styles. Use when the user asks to generate HTML for an official account, create a WeChat version, or format an official account article.
Polish, translate, or tighten existing academic prose while preserving facts, terminology, and evidence boundaries. Use for 论文润色、学术翻译、正文精简, or manuscript LaTeX layout fixes. Use nature-writing when the main task is drafting new sections or rebuilding the manuscript argument.
Produce a polished, self-contained HTML "readout" document under ~/.readouts (with an auto-maintained index page), either by snapshotting the findings accumulated in the current conversation or — when invoked fresh, e.g. "/readout on how github webhook events are processed" — by sharpening scope with clarifying questions and researching the codebase before documenting. The work runs in a child agent so the main conversation's context stays clean. Use whenever the user invokes /readout, says "write this up", "turn this into a doc/page", "make a readout", or asks for a readable, shareable document capturing findings or explaining how something works.
Draft or restructure scientific manuscript arguments, sections, and initial-submission materials from author-provided evidence. Use for 论文写作、章节起草、论证重构、正文压缩、首次投稿材料. Use nature-polishing for language-only edits to existing prose and nature-response for post-decision correspondence.
Find and verify Nature/CNS-family literature supporting manuscript claims, with claim-to-source mapping and reference-manager export. Use for Nature系列引用、CNS支撑文献、分段补引用 when this journal scope is requested; use broader literature search for unrestricted sources.
Search literature across sources, verify or manage citations, and build MeSH strategies or citation-impact audits. Use for literature searches, citation checks, reference management, strict analysis of citations by others, and evidence-backed citer profiles; not for translating a paper or drafting manuscript prose
Draft, audit, or revise responses to peer review, revision cover letters, and marked-manuscript or LaTeX revision packages. Use for responses to reviewer comments, point-by-point replies, revision letters, rebuttals, and edits to existing response drafts. Initial-submission materials belong to nature-writing; simulated peer review belongs to nature-reviewer
A skill for refining AI-generated Japanese. Use only when the user explicitly names yomiyasu and asks for it (such as “/yomiyasu,” “$yomiyasu:yomiyasu,” or “refine this with yomiyasu”), or clearly asks to refine Japanese using the skill. Also treat instructions to use yomiyasu in CLAUDE.md, AGENTS.md, custom instructions, and similar as an explicit request by name. Do not use it for requests to write Japanese text without naming it, or to update code, settings, or documentation. Preserve meaning and conditions while improving unnatural metaphors, ambiguous subject-predicate relationships, and unnecessary ornamentation or copy-like phrasing.
Read when the user asks what OpenKnowledge is, wants to install it on a repository, open or preview a standalone Markdown file that is not part of an OpenKnowledge project, share an OpenKnowledge project with collaborators, asks whether OpenKnowledge supports a capability, or asks how `ok init` / `ok cowork` / OK Desktop set up a project. Do NOT load this to perform OpenKnowledge reads or writes—the runtime guidance for editing Markdown in an initialized OK project is a separate project-local skill, installed into each detected agent's skills directory (for example, `.claude/skills/open-knowledge/`) whenever `ok init` runs.
Draft the terms and conditions an affiliate accepts when joining a commission-based program - the affiliate program agreement, with the canonical clause set, prohibited-tactics clauses and enforcement ladder, commission validation, clawback and termination mechanics, and jurisdiction overlays (FTC endorsement rules, EU P2B, UK ASA/CAP, GDPR roles). Output is a clause-complete draft flagged for mandatory legal review, for B2B SaaS and B2C ecommerce alike. Use whenever the user mentions affiliate program terms, an affiliate agreement, prohibited tactics, or a brand-bidding policy, even if they only ask what affiliates must agree to. Do NOT use for reviewing a published post's disclosure label - use mbfinotti/partnerships-skills@affiliate-disclosure-compliance instead.
All-in-one WeCom suite covering contacts, documents, online spreadsheets, smart spreadsheets, smart documents, PPT presentations, schedules, meetings, to-dos, WeDrive, email, messages, media files, and more. Always trigger when a link contains doc.weixin.qq.com or page.weixin.qq.com. Trigger when WeCom is mentioned or when any of these functions are needed: find contact information; search, rename, or grant access to documents; create, read, or edit online doc documents; create or modify online spreadsheets; create/import and read or edit smart spreadsheet subtables, fields, records, views, charts, and styles such as fills and highlights; create and edit smart documents, including forms and dashboards; create and edit online PPT presentations or import local .ppt/.pptx files as online documents (provide the online document link); create, query, modify, or cancel schedules and check availability, office buildings, and meeting rooms; book and manage online meetings, including minutes, to-dos, and raw transcripts; create, query, modify, complete, delete, or leave to-dos; search and upload WeDrive files, download offline files, rename supported files, and create folders; send, reply to, forward, search, and read email; send text/Markdown/image/file/voice/video messages to the currently authorized user or the most recently active conversation; and upload or download media files. Even if WeCom is not explicitly mentioned, trigger this skill for office tasks involving people, documents, spreadsheets, schedules, meetings, to-dos, WeDrive, email, or messaging. Phrases such as “make a PPT”, “generate a presentation”, “presentation PPT”, or “import PPT” also trigger it. For unspecified “documents”, default to smart documents; for “spreadsheets” without an explicit “online spreadsheet” specification, default to smart spreadsheets. Always trigger when a link contains drive.weixin.qq.com.
Create and present web-based slide decks for developers using Slidev with Markdown, Vue components, code highlighting, animations, and interactive features. Use for technical presentations, conference talks, code walkthroughs, teaching materials, or developer decks
Write or rewrite text in plain, layman-readable English in the spirit of ASD-STE100 Simplified Technical English: short sentences, active voice, simple tenses, one word one meaning, condition before command, every technical term defined at first use, no AI slop. Default mode is Plain. Strict mode applies full STE vocabulary compliance when the user names STE, ASD-STE100, or compliance. Use for documentation, READMEs, runbooks, procedures, error messages, release notes, incident reports, API guides, and explanations for readers outside the field. Also use when the user says "STE", "Simplified Technical English", "ASD-STE100", "plain English", "layman's terms", "explain it simply", "no jargon", "de-slop", "make this readable", "write for non-native readers", or asks for docs that translate well. The same rules govern the reply: answer first, prose only.
Internal shared-reference support package for installed Nature Skills, including nature-writing, nature-polishing, nature-response, nature-reader, and nature-paper2ppt. Do not invoke it as a standalone user workflow. Load only the specific core or journal-format file requested by another Nature skill
Create stunning, animation-rich HTML presentations from scratch or by converting PowerPoint files. Use when the user wants to build a presentation, convert a PPT/PPTX to web, or create slides for a talk/pitch. Helps non-designers discover their aesthetic through visual exploration rather than abstract choices.
Create and present web-based slide decks for developers using Slidev with Markdown, Vue components, code highlighting, animations, and interactive features. Use for technical presentations, conference talks, code walkthroughs, teaching materials, or developer decks
Generate self-contained HTML visualizations with Plannotator theming. Use for implementation plans, PR explainers, architecture diagrams, data tables, slide decks, and any visual explanation of technical concepts. Plans and PR explainers follow Plannotator's prescriptive approach; all other visual content delegates to nicobailon/visual-explainer.
Convert Word (.doc, .docx), PowerPoint (.ppt, .pptx), Excel (.xls, .xlsx), OpenDocument (.odt, .ods, .odp), RTF, EPUB, CSV, and PDF files to GitHub-Flavored Markdown. Use when a task needs the contents of an office document, spreadsheet, presentation, ebook, or PDF you cannot read directly.
Cross-validate academic references against multiple sources, comparing authors, titles, years, volumes, issues, and page numbers field by field. Flag volume/year or DOI/year conflicts, unusual author order, page discrepancies, and other issues, then produce a structured verification report. Process reference lists from entire papers or proposals in batches, or check individual references. Supports syncing corrections with Zotero.
Runs one or more installed review lenses — adversarial critique, edge cases, verification gaps, structure, prose — and reports triaged findings. Use when, and only when, the user asks you to review a diff, a pull request, or an artifact — code or documents, one or many — and actually says "review"; an explicit skill:bmad-review directive from another skill counts as that ask. A request to act on feedback from an earlier review is a change, not a review. Never invoke this uninvited, including on edits you just made.
Audit or improve manuscript statistical reporting, including experimental units, replication, uncertainty, tests, and figure statistics. Use for 统计审查、统计方法小节、图注统计 and reviewer concerns; compute new analyses only when requested with data.
Compress natural-language memory files (CLAUDE.md, todos, settings) into a caveman format to reduce input tokens. Preserve technical content, code, URLs, and structure completely. The compressed version overwrites the original file, and the human-readable version is saved as FILE.original.md. Trigger with “/genshijin-compress <filepath>” or “compress memory file”.
WeCom online spreadsheet document management: create online spreadsheets, import CSV/Excel as online spreadsheets, read spreadsheet information and data, modify spreadsheet contents, append rows, and manage sub-sheets. Trigger when the user mentions “spreadsheet,” “online spreadsheet,” or “Excel spreadsheet,” or shares a link like https://doc.weixin.qq.com/sheet/xxx. For general document operations, use wecomcli-doc-manage; for doc document operations, use wecomcli-doc; for smart spreadsheet CRUD, use wecomcli-smartsheet.
A skill for operating WeCom Smart Docs (smartpage). Create documents, import .md files as documents, read and edit document content (rewrite entire pages, make local edits, add or remove subpages), upload attachments, and build data system pages with dashboards/charts and information collection forms. Use this skill when users mention documents, Smart Docs, or Smart Home; provide a https://doc.weixin.qq.com/smartpage/xxx or https://page.weixin.qq.com/smartpage/xxx link; ask to organize content into a document; or make requests such as “create a document” or “import md as a document” without specifying a document type
Design or redesign frontend UI, presentations, and graphics on the Superdesign canvas with a choice of leading AI models. Use whenever the user wants to design a page, feature, flow, slide deck, or brand-new product; improve or reproduce existing UI; compare design results across top models; explore visual variants; set or extract a design system; build reusable components or multi-page flows; create presentations; or create posters and marketing graphics, even if they never say the word 'design tool'. Also supports generating supporting image or video assets when a design needs them.
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.