Skills
96,981 packaged capabilities and playbooks for agents. Install any of them with one command.
Documents
Draft a lawyer's letter from a completed engagement intake — passes through a confidentiality/admission risk/settlement-negotiation posture checklist gate, outputs a .docx with a post-send checklist, and offers the option to create a matter. Use when the user says "draft a lawyer's letter", "write a [type] letter", or a completed engagement intake is ready to become a send-ready draft.
Maintain an append-only, no-rewrite project document/log history mechanism: for each change, create YYYY-MM-DD_主题.md and link them together with an INDEX.md timeline index, so agents such as CodeBuddy / Claude Code / Codex can read the full history. Use when the user says "记录一下", "写个日志", "追加文档", "整理文档历史", "建个 docs 索引", or "把这次改动记下来". model-invoked.
This skill is used to create organized technical documents in /docs (specs, implementation plans, ADRs, reference documentation). It activates when the user says "crear documento", "escribir spec", "documentar esto", "creame una spec", "escribime documentacion", "hacer documentacion", "write a spec", "create documentation", "write an ADR", or wants to add technical documentation to the project.
Write or update documentation for engineering changes — both product-facing (user docs, API reference, guides) and internal (architecture docs, runbooks, inline code docs). Builds a world model of what changed and traces transitive documentation consequences across all affected surfaces. Discovers and uses repo-specific documentation skills, style guides, and conventions. Standalone or composable with /ship. Triggers: docs, documentation, write docs, update docs, document the changes, product docs, internal docs, changelog, migration guide.
Produce properly-formatted tracked changes for a Word document. Use when asked to redline a document, suggest edits to a contract or document, create tracked changes for review, or mark up a document with proposed revisions. Produces a complete redline with insertions, deletions, and margin comments that can be applied to the source document. Best used with Claude Opus 4.7 or newer for reliable tracked changes handling.
Use when working in a Doom documentation repository to turn requirements into repository-aligned documentation diagnosis, plans, drafts, and AI-usability reviews. Supports modifying authoritative existing pages, adding focused scenario documents, separating user-facing docs from engineering-truth docs, planning doc-tree restructures, read-only convention or AI-usability reviews, and explicitly requested `yarn build` or `yarn translate` tasks. Explicit target repository rules override skill defaults; when the repository is silent, built-in product documentation standards govern new product docs.
Create, inspect, and edit Microsoft Excel workbooks and XLSX files with reliable formulas, dates, types, formatting, recalculation, and template preservation. Use when (1) the task is about Excel, `.xlsx`, `.xlsm`, `.xls`, `.csv`, or `.tsv`; (2) formulas, formatting, workbook structure, or compatibility matter; (3) the file must stay reliable after edits.
Feishu document to Markdown tool. Converts Feishu document links to Markdown format, supporting text, tables, images, code blocks and other elements. Use cases: (1) convert Feishu requirement documents into local Markdown files, (2) back up Feishu document content, (3) use Feishu document content with other tools.
Feishu cloud document content optimization and formatting. Use this skill when the user needs to optimize the layout, structure, formatting, or visual appeal of Feishu documents. Supports: (1) reading Feishu document content (2) optimizing document structure and hierarchy (3) clearing and replacing document content (4) editing documents via browser automation. Trigger words: optimize Feishu document, beautify document, organize document format, document layout.
Write a structured grant proposal or funding application for any grant type. Use when asked to write a grant proposal, funding application, research grant, charitable grant, or innovation fund application. Produces a complete proposal with project summary, rationale, methodology, impact, and budget narrative.
Generate polished single-file HTML slide presentations with interactive components (flip cards, charts, tables, code blocks, architecture flows, stats, timelines, and more) or creative visual themes. Use this skill whenever the user wants to create slides, presentations, decks, or any visual slide-based content as HTML. Also trigger when the user invokes /html-slides or mentions creating an HTML presentation, pitch deck, or slide deck.
This skill should be used when the user needs to translate PowerPoint presentations (.pptx) between languages, preserving formatting and layout. Supports parallel slide-by-slide translation with per-slide validation and retry. Default languages are Portuguese and English but any language pair is supported.
Develop consulting pursuits, RFP responses, proposals, statements of work, value propositions, and pitch decks. Use for winning and scoping an engagement; use client-deliverables when available for reports and presentations during delivery.
Prepare cohesive image prompts for presentation slides by combining a chosen theme with concise factual team and technology references. Use when the user asks to prepare image prompts or backgrounds for presentation slides. Russian discovery terms: промпты слайдов, фоновые изображения, тема презентации, графика для слайдов.
Generates clean, publication-ready flowcharts as SVG code. Use when the user asks to draw a flowchart/流程图, requests SVG flowchart output, or needs a论文风格流程图 from steps/decisions/modules. Supports converting from structured text, natural language, or JSON spec to SVG; optional SVG-to-PDF export for LaTeX. Produces academic, low-saturation styling and can save SVG/PDF files into the repo.
Prepare an evidence-based team retrospective, monthly delivery review, report, or presentation from a private team profile; it collects its own planning and delivery evidence, unlike briefing. Use when the team runs a retrospective or monthly delivery review, or needs a report or presentation from its own profile. Russian discovery terms: ретро, итоги месяца, месячный отчёт, презентация команды.
Toolkit for styling artifacts with a theme. These artifacts can be slides, docs, reportings, HTML landing pages, etc. There are 10 pre-set themes with colors/fonts that you can apply to any artifact that has been creating, or can generate a new theme on-the-fly.
Run Chain-of-Verification (CoVe) on a draft or a block of text with factual claims. Spawns the `claim-verifier` agent in a fresh context (never a conversation fork) so it never sees the draft — then reports which claims are supported, contradicted, or unverifiable. Use when user says "verify these citations", "check the claims in X", "did I hallucinate anything", "fact-check this draft", "run CoVe on this", or after any text generation that asserts facts about papers, datasets, or numerical results. NOT for style/grammar review (use `/proofread`) or substance review (use `/review-paper`).
Transform Obsidian video notes from the Vault into published notes on joelclaw.com. Use when publishing video notes, converting vault video content to the site, or when asked to 'publish a video note,' 'turn this video into a note,' 'publish from vault/videos,' or any task involving /Vault/Resources/videos → joelclaw content. Triggers on references to video notes, vault video files, or publishing video content to the blog.
Use when starting or adapting an A4 single-column OpenPress academic / research paper starter for conference drafts, journal preprints, course papers, technical reports, or thesis-style chapters with abstract, numbered sections, figures, tables, and a references list.
Use when the user wants to humanize, de-AI, polish, or warm up an AI-generated document, in English or Chinese. Good for social posts (X/Weibo/Jike/RedNote), Reddit and forum comments, blogs, podcast show notes, README cleanup, product docs, landing page copy, proposals, founder notes, and technical memos. Removes templated phrasing, consultant-speak, vague abstraction, emoji or icon headings, markdown templates, overly balanced tone, and the typographic tells that flag generated text (em-dashes `—`/`——`, smart quotes, the `…` character) while preserving meaning. Supports optional voice modes: human-texture (light irregularities) and learning mode (match a specific host's style from samples).
Scan all blueprint documents and assign IDs to those missing them, update manifest registry. Use when the user asks to "sync document IDs", assigns PRD-NNN / ADR-NNNN / PRP-NNN / WO-NNN IDs to docs missing them, wants to build GitHub issue index for orphans, creates issues for unlinked documents with --link-issues, or previews ID changes with --dry-run.
Creates beautiful, branded HTML content assets — industry reports, landing pages, comparison sheets, one-pagers — from structured data. Uses Gamma API (preferred), v0.dev Platform API, or a self-hosted HTML template system with Tailwind CSS. Outputs self-contained HTML files that can be hosted as web pages or converted to PDF.
Review contracts against your organization's negotiation playbook, flagging deviations and generating redline suggestions. Use when reviewing vendor contracts, customer agreements, or any commercial agreement where you need clause-by-clause analysis against standard positions.
Fetch web content. Use when the user asks to extract text from PDFs, Word docs, PowerPoint, Excel, images, audio, EPUBs, MHTML, YouTube transcripts, or any URL — even if they say 'read this file', 'get the text from', 'extract content', or 'transcribe'.
Turn a finished CodeSpring plan into the pack a paying client actually receives — a plain-English summary of what is being built, the mockup and its style guide, the plan and task links, an honest phase-by-phase build order, what was assumed, what is still open, what is needed from them, and exactly what to do next to start building. Written at a reading level a non-technical owner can follow, with no file paths and no jargon. Run it once the map, notes, PRDs and tasks exist and the plan is about to leave your hands. Triggers, "hand this over to the client", "create the client pack", "write the handover", "send them the plan", "what do I send the client", "onboard them onto this plan", "package this up for delivery".
Create an Architecture Decision Record (ADR) - Layer 5 of the SDD flow, documenting one architecture decision with Context-Decision-Consequences. Use after BDD when an architectural choice needs recording. Single-document authoring primitive; for end-to-end or batch generation the autopilot (`doc-adr-autopilot`) drives this skill.
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.
Render a documentation-style Cursor Canvas that organizes architecture notes, API references, walkthroughs, and how-tos into a navigable layout with sections, tables of contents, and cross-references. Use when the user asks for a docs canvas, documentation overview, architecture walkthrough, API reference page, or wants to render structured documentation as an interactive canvas.
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
Cria e mantém o TRD (Technical Requirements Document) em `docs/trd.md` — stack, arquitetura, requisitos não-funcionais, dependências externas, padrões e decisões globais do projeto. Também cria ADRs (Architecture Decision Records) no Modo Decision: registra uma decisão técnica em `docs/adrs/` e atualiza a seção Decisões Globais. O TRD é o contexto técnico consultado pelas skills do fluxo sdd (`sdd-especificar` em diante). Use ao criar um TRD, documentar a stack, registrar padrões de arquitetura, começar projeto novo sem TRD, quando a stack mudou, ou quando o `sdd-especificar` pedir contexto técnico por falta de `docs/trd.md` — mesmo sem usar o termo "TRD". Use o Modo Decision quando o usuário quiser "registrar uma decisão", "criar um ADR", ou disser "decidimos usar/trocar X por Y" — é decisão técnica/arquitetural, distinta de decisão de produto (que fica no PRD).
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.