Skills
96,981 packaged capabilities and playbooks for agents. Install any of them with one command.
Documents
Write characters from pinyin — input Chinese text to get pinyin annotations and a practice sheet PDF, generated locally. Suitable for toddler character practice and Chinese language teaching. [Important] You must first read the original skill text to get the correct command format; do not guess.
Investor pitch deck structure with a slide-by-slide framework, visual design rules, and data presentation. Covers the 12-slide framework, chart types, team slides, and common investor turn-offs. Use for: fundraising decks, investor presentations, startup pitches, demo days, grant proposals. Triggers: pitch deck, investor deck, startup pitch, fundraising deck, demo day, pitch presentation, investor presentation, seed deck, series a deck, pitch slides, startup presentation, vc pitch, investor meeting
Expert in creating, editing, and automating PowerPoint presentations using python-pptx and PptxGenJS. Use when generating slides programmatically, modifying presentations, or building report automation. Triggers include "PowerPoint", "PPTX", "slides", "presentation", "python-pptx", "PptxGenJS", "slide deck".
Work with Yuque OpenAPI for reading, searching, creating, and updating users, groups, repos, docs, TOC structures, versions, and statistics. Use when Codex needs to operate on Yuque knowledge bases or documents, reorganize document placement in a repo, inspect API capabilities, or prepare guarded plans for destructive Yuque actions.
Use when a visual artifact needs a consistent color and type system applied — slide decks, reports, HTML pages, dashboards, PDFs, docs — or when asked to "theme this", "restyle with a palette", "make these slides look consistent", "pick colors and fonts", or to build a custom theme from a brand or a description. Provides 10 contrast-verified themes with semantic tokens and a checker script.
Use when authoring (or amending) a technical-design document (a TDD / engineering design doc / design RFC) for one feature or component — the detailed implementation design for building it within an existing system. Guides the METHOD, not the outline: grounding the design in established practice and the project's real constraints, tracing every decision bidirectionally to a requirement, comparing at least one real (non-strawman) alternative with a stated decision criterion, referencing the architecture-doc / API spec / data-model rather than duplicating them, naming the failure modes, the observability signals, the testing, and the rollout — and amending an approved design as a versioned, ripple-analyzed delta — to a bar where an engineer can implement without re-deriving the design. Assumes the approved PRD + feature-spec as upstream input, never a blank page. Not for system-wide architecture, not for the API contract or data schema, and not for reviewing a finished TDD.
One-click full-pipeline PPT: first use GordenImagePPTGen to generate an image-format PPT, then use GordenImage2PPTX to reverse-convert it into an editable .pptx. Packages and orchestrates these two sub-skills in sequence, delivering the image-based PPT + editable pptx + all intermediate artefacts together. Orchestrates image-PPT generation and image→editable-PPTX conversion end to end. Use when the user only provides a topic/content and wants a complete, both good-looking and editable PPT deliverable, or does not name a specific function.
This skill should be used to review, lint, or fix Markdown formatting in READMEs, ADRs, runbooks, how-tos, design docs, or any `.md` file. PROACTIVELY activate on "review this markdown", "lint this doc", "lint this README", "style-check this doc", "fix the formatting", "review my README", "is this markdown valid?", "fix the headings", "fix the list indentation", "ATX vs setext", "should I use a TOC?", "markdown style guide", or "Markdown linter." Provides: two-pass syntax/style review with line-referenced findings.
Handle a hand-edited Office artefact that is now the authoritative version: repair a feature-rich Excel workbook in place through COM (broken slicers or dropdowns, #REF!, circular reference warnings), or promote a generated .docx/.pptx/.xlsx to canonical hand-edited source and retire its generator. Use when Ane reports a damaged workbook or declares an edited file the source of truth. Distinct from office-review-pass (Word review cycle), the ane_package.reporting builders (generate new branded files), and check-deliverable (read-only QA verdict on prose).
Work on a Word deliverable inside the .docx itself: read and engage reviewer comments, insert review findings as margin comments authored as Ane into her working copy, apply real Word tracked changes a counterparty can accept or reject, make scoped formatting-preserving fixes via Word COM, or add a branded glossary and verified source annex. Use when Ane hands over a commented or hand-edited .docx for review, markup, or in-file edits. Distinct from ane-voice (prose voice only, never touches the file), localise (target-language work), check-deliverable (read-only QA verdict), meeting-notes marginalia (reads comments, never writes them), and tor-procurement (builds ToRs).
Drafting Python Enhancement Proposals (PEPs) — proposing a Python language feature, a standard library change, an interoperability standard, or an informational/process document for the Python community. Covers all three PEP types (Standards Track, Informational, Process): choosing the right type, scaffolding a valid reStructuredText pep-NNNN file, filling each required section to the acceptance bar, linting the headers, and navigating the sponsor / submission / Steering Council review process. Trigger on "write a PEP", "draft a PEP", "propose a Python feature", "create a Python Enhancement Proposal", "PEP template", or when someone is preparing a proposal for the Python Discourse or python-dev. Use it even if the user only says "PEP" or doesn't mention reStructuredText — the headers, sections, and process are exactly what trips PEP authors up.
Use when reviewing or judging a finished PRD (product requirements document) to decide whether the downstream build can be planned from it — an acceptance gate, not authoring. Judges the PRD against a 12-condition plannability bar: the problem is evidenced (not asserted), users are concrete, success metrics are measurable (with guardrails where gameable), the MVP boundary is defensible, features + acceptance criteria are concrete, non-functional requirements carry numeric targets, the problem→goal→metric→feature→AC chain is traceable (no orphans), dependencies are named, no evidence is fabricated, and open questions are surfaced. Also reviews an AMEND as a delta-scoped review. Emits exactly `VERDICT: approve|revise` plus actionable findings. Approves a PRD that meets the bar (no false-revise on a thin one) and revises only on a real, named gap. Not for authoring or fixing a PRD, not for engineering design docs (specs, ADRs, RFCs), and not for other document types.
Create and read XMind mind map files (.xmind), supporting both modern (XMind Zen/2020+) and legacy (XMind 8) formats. Use this skill whenever the user mentions mind maps, brain maps, XMind, brainstorming diagrams, flowcharts, Gantt charts, project planning with visual maps, or wants to analyze/search existing .xmind files. Trigger on both English and Chinese expressions: "思维导图", "脑图", "脑图文件", "xmind", "mind map", "mindmap", "画个脑图", "做个思维导图", "创建脑图", "打开脑图", "分析思维导图", "看看这个xmind", "甘特图", "流程图", "逻辑图", "项目计划图", "鱼骨图", "时间线". Also trigger when the user asks to read, open, search, compare, or extract nodes from .xmind files, even if they don't explicitly say "XMind" — e.g. "帮我看看这个文件", "找一下脑图", "哪些任务没完成", "对比这几个文件".
Use when writing or updating any Bagisto documentation site — the developer documentation, the merchant user guide, or any other Bagisto docs repository — covering page content, code samples, screenshots, the sidebar, image naming, and moving or deleting pages. Trigger phrases include "docs", "documentation", "user guide", "developer documentation", "dev docs", "merchant documentation", "marketplace docs", "document this", "update the docs", "add a doc page", "screenshot", "ImagePopup", "redirect a doc page".
Fetch presentation slides from a URL and convert them to PDF. Supports direct PDF URLs, PPTX URLs, OneDrive sharing links, and RevealJS HTML presentations. For RevealJS, also extracts slide text content and links to a markdown file. USE FOR: download slides, fetch slides from URL, convert PPTX to PDF, get RevealJS slides, OneDrive slides.
Review and apply annotations left on a Markdown file with mdnote (highlight-and-comment review for .md files). Trigger when the user says "I left notes", "check my annotations", "review my notes on <file>", asks you to look at feedback on a doc, or after you've pointed the user at a Markdown file for review.
Create polished, audience-tailored presentations from outlines or documents, with support for Marp, reveal.js, Google Slides, and PPTX output formats. Use when the user requests presentation creation or provides relevant inputs for this workflow.
Kingsoft Docs (WPS / Kdocs): create, read, edit, search, share and organize online documents and knowledge bases. Use when the user works with online documents (e.g. writing weekly reports, clipping web pages to documents, splitting PDFs, AI-generating PPTs, beautifying spreadsheets, converting relay lists to tables).
Write, fix, or review Azure DevOps wiki Markdown, Mermaid, _TOC_, _TOSP_, details blocks, query tables, mentions, work-item links, KaTeX, videos, and code fences. Use for Azure DevOps surface quirks. Do NOT use for GitHub-only or non-Azure docs.
Agent-callable Dropbox tools — upload, organize, find, and share files and folders. Use when the user wants to manage Dropbox content (save, move, search, share, list, or read files), including requests that don't name Dropbox explicitly, e.g. "save this report to my cloud storage" or "share that folder with Sam".
Use when a manuscript or response-to-reviewers letter reads as AI-written. Scans for 27 AI writing patterns and rewrites flagged passages, preserving technical accuracy and bounding how much text changes. Not general copy-editing; that is /polish-language.
Write clear, searchable help center articles and FAQ entries based on support data, product documentation, and common customer questions. Use when the user requests knowledge base article writing or provides relevant inputs for this workflow.
Extract valuable legal Q&A pairs from lawyer-client communications and generate structured knowledge base content. This skill should be used when the user needs to organize client consultation records, extract reusable legal knowledge from conversations, create a Q&A knowledge base, or prepare content marketing material. Supports strict client information anonymization.
Modao prototype capture tool. Automatically captures all pages, screenshots, and annotations from a Modao prototype link and generates a Markdown document. Use cases include: (1) capturing prototype pages (2) generating page screenshots (3) extracting annotation content (4) exporting Markdown documents.
Create or redraw concept diagrams, research-content relationship diagrams, and technical roadmap diagrams for NSFC grant proposals; when the deliverable needs editable source diagrams, stable layout, or verifiable export, prefer generating Draw.io XML. Pure data/statistical charts, photo editing, or reuse of original figures from papers should not trigger this skill.
Converts PDF files to Markdown format using PyMuPDF, extracting text content and embedded images. Fast and lightweight. Automatically fixes LaTeX umlauts (¨a → ä, etc.) and converts ß to ss (Swiss German). Use when converting PDFs to Markdown, extracting document content, or processing PDF files for text analysis. Generates one .md file and 0..n .png files for images.
Use when modifying EXISTING Datex Studio reports on a branch. Handles label/style changes, field rearrangement, adding/removing columns, datasource modifications, and adding new data sections. Trigger for: "edit a report", "modify a report", "change the label", "add a column", "update the report on branch X", "fix the report layout". For creating NEW reports from scratch, use `report-creator`.
Use when authoring a PRD (product requirements document) for a software or product project — turning a product idea into a comprehensive, plannable requirements doc. Guides the producer through the METHOD, not the outline: grounding the problem in evidence (jobs-to-be-done), defining measurable success metrics with guardrails, drawing a defensible MVP boundary, specifying functional + a non-functional taxonomy with numeric targets, writing testable acceptance criteria, keeping the problem→goal→metric→feature→AC chain traceable, naming dependencies, and surfacing risks + open questions — to a bar an engineer can plan milestones from. Also amends an existing PRD as a versioned, changelogged delta. Composes with a separate PRD template tool (the section structure) and a deep-research capability. Not for reviewing a finished PRD and not for authoring other document types.
Apply communication best practices when generating or reviewing any document, presentation, report, memo, slide deck, proposal, or email. Use this skill when asked to write, create, draft, or generate a document or presentation — apply the principles at generation time, not as an afterthought. Also use when asked to "review my doc," "look at this deck," "does this make sense," "is this clear," "improve this proposal," "check this before I send it," "make this more effective," or any request to evaluate whether a document will land with its audience. Use this skill even when the request seems minor — a "quick look" or a "short memo" is exactly when these principles matter most.
Generate draw.io editable diagrams (.drawio, .drawio.svg) from text, images, or Excel. Orchestrates 3-agent workflow (Analysis → Manifest → SVG generation) with quality gates. Use when creating architecture diagrams, flowcharts, sequence diagrams, or converting existing images to editable format. Supports Azure/AWS cloud icons. Triggers on draw.io, drawio, ダイアグラム, アーキ図, フローチャート, シーケンス図.
Process and analyze file references uploaded by the user, extract key information, and provide application suggestions. Suitable for parsing @-symbol references and natural language references, and extracting information related to short drama planning
Audit a doc, guide, README, or block of prose against the good-docs-writing style guide and report violations. Use when the user asks to review, critique, lint, or check the voice and tone of documentation or text. Produces a structured findings report (file:line, rule violated, offending text, suggested rewrite) and does NOT edit files unless explicitly asked.
Writing style guide derived from Modal's documentation voice. Apply when writing or editing docs, guides, tutorials, or technical prose that should read direct, second-person, confident, low-jargon, and example-first. Use to draft new docs in this voice or to revise existing prose toward it.
Work with Google Drive through its MCP tools - search, read, create, organize, share, comment, and export files. Use when creating files in specific folders, moving or renaming, converting Markdown/CSV into Docs/Sheets, managing comments, or exporting a rendered PDF.
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.