Generate or update the CLI documentation under `docs/docs/reference/cli/` from the Cobra command code in `cli/`. Use this skill whenever the user asks to "update the CLI docs", "actualize/sync the CLI documentation", "document the CLI", "the CLI docs are out of date", "regenerate the runner/user/vault/project/migrate docs", or after adding or changing a Cobra command, subcommand, flag, alias, or required-argument check anywhere under `cli/cmd/`. Covers every command group (`users`, `projects`, `vaults`, `runner`, `migrate`) plus the operational commands (`server`, `setup`, `version`) and the global flags on the root command. Trigger when the user adds a new `*Cmd` Cobra command, a new `PersistentFlags()` call, or renames/removes a CLI flag.
No other project uses it yet
14k24d agoReviewMountCreate a free account to mount
Documentation guidelines for Mastra. Use this skill when creating, editing, moving, deleting, or reviewing Mastra documentation, sidebars, redirects, or docs components.
29k28d agoReviewMountCreate a free account to mount
Keep documentation in sync with a code or contract change in the SAME PR. Use whenever you change an interface, wire field, endpoint, config field, default, harness/backend value, or runtime behavior, and after any implement-feature slice that lands such a change. Triggers - "keep docs in sync", "update the docs too", "the docs drifted", "document this change", "did we update the inventory". Maps a change to every doc that describes it (design docs, the agent-workflows documentation/ pages, the interface inventory + its index, AGENTS.md, skills) and enforces one source of truth.
Steady16 mentions in 2 weeks
No other project uses it yet
4.9k4mo agoReviewMountCreate a free account to mount
Manually run the extended DeepSeek Harness bilingual-document workflow, including generated briefings, delegated prose translation, whole-document translation, and scoped pairing verification.
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.
Review documentation changes for compliance with the Metabase writing style guide. Use when reviewing pull requests, files, or diffs containing documentation markdown files.
Steady2 mentions in 2 weeks
25 projects use a version of this
50k12d agoReviewMountCreate a free account to mount
Write documentation following Metabase's conversational, clear, and user-focused style. Use when creating or editing documentation files (markdown, MDX, etc.).
Steady2 mentions in 2 weeks
1 project uses a version of this
50k12d agoReviewMountCreate a free account to mount
Reorganize NemoClaw documentation pages, navigation, or content ownership while preserving published routes. Use for structural documentation refactors.
Steady2 mentions in 2 weeks
No other project uses it yet
23k12d agoReviewMountCreate a free account to mount
Generate a model card for an OpenMed clinical NER or de-identification model documenting intended use, quantitative metrics, subgroup performance, limitations, and a medical-device disclaimer for clinical AI governance. Use when the user wants to write or update a model card, a README model section, or governance documentation, or to turn OpenMed eval outputs (release gate report, fairness_report, error_report) into the card's metrics and limitations sections. Trigger on \"model card\", \"intended use\", \"model documentation\", \"governance\", \"limitations section\", \"datasheet\", or \"FDA/ONC transparency\" for an OpenMed model.
Steady3 mentions in 2 weeks
No other project uses it yet
5.8k3mo agoReviewMountCreate a free account to mount
Use when creating a compound skill — a structured knowledge base for a project or topic that uses a SKILL.md routing table and reference documents. Covers the research phase, topic decomposition, SKILL.md frontmatter and routing table format, reference document structure, cross-referencing, and maintenance. Triggers on: "compound skill", "create skill", "write skill", "skill template", "skill structure", "routing table", "reference document", "skill authoring", "skill creation guide".
Steady21 mentions in 2 weeks
No other project uses it yet
1.5k23mo agoReviewMountCreate a free account to mount
Use this skill to create fillable Word forms (.docx) with real Content Controls (SDT) + legacy FormField checkboxes + MERGEFIELD mail-merge placeholders + document protection. Trigger on: 'fillable form', 'form fields', 'content controls', 'SDT', 'word form', 'fill in', 'only editable fields', 'protect document', 'onboarding form', 'HR intake', 'survey template', 'contract / SOW template', 'mail-merge template', 'compliance checklist', 'medical intake questionnaire'. Output is a single .docx where specific fields are editable and the rest is locked. This skill is INDEPENDENT, not a scene layer on docx — payload is `w:sdt` + `w:ffData` + `w:fldChar` + `documentProtection`, none of which docx base skill covers. Do NOT trigger for regular reports, letters, memos, academic papers, pitch decks, or any document with no user-fillable fields — route those to officecli-docx or its scene layers.
Steady2 mentions in 2 weeks
1 project uses a version of this
33k2mo agoReviewMountCreate a free account to mount
Audit documentation gaps across the Phoenix repo by analyzing recent commits to main (default: last 7 days). Use this skill whenever the user asks to find undocumented features, identify docs gaps, audit what shipped without docs, check which recent changes need documentation, review stale docs against current code, or mentions "documentation debt", "doc coverage", "undocumented APIs", or "what's missing from /docs". Also trigger on requests like "what from last week needs docs", "find stale READMEs", or "check docstring coverage for recent changes". Covers /docs (Mintlify), package READMEs, package-level built-in docs (Sphinx, TypeDoc), Python docstrings, TSDoc, and code comments.
Steady12 mentions in 2 weeks
No other project uses it yet
12k2mo agoReviewMountCreate a free account to mount
Review, improve, rewrite, author, or plan Storybook documentation in /docs. Use this when asked to review docs, improve a page, rewrite documentation, draft new docs, or advise on docs strategy.
24 projects use a version of this
91k11d agoReviewMountCreate a free account to mount
Turn existing practice into an SOP or policy document with roles, steps, checkpoints, exception handling and version history, delivered as a Word document
Steady5 mentions in 2 weeks
10 projects use a version of this
12k3mo agoReviewMountCreate a free account to mount
Writes and updates Filament developer documentation with the repository's structure, examples, and safety guidance. Use when adding, editing, or reviewing documentation under docs/ or packages/*/docs/.
Steady5 mentions in 2 weeks
No other project uses it yet
32k7d agoReviewMountCreate a free account to mount
Scaffold a new documentation page for the Skeleton documentation site (sites/skeleton.dev), including frontmatter, optional boilerplate, examples, and API reference.
6.1k7d agoReviewMountCreate a free account to mount
Document analysis with inline source screenshots. When you ask Copilot to analyze a document, Eyeball generates a Word doc where every factual claim includes a highlighted screenshot from the source material so you can verify it with your own eyes.
No other project uses it yet
41k20d agoReviewMountCreate a free account to mount
How to write a document the user will read (report, itinerary, comparison, plan, notes) and save it to their Google Drive. Use when a thread's result is a document rather than a code change.
Steady5 mentions in 2 weeks
1 project uses a version of this
11k48d agoReviewMountCreate a free account to mount
A folder with a SKILL.md file: a name, a description of when to use it, and instructions. Claude loads a skill only when the task matches its description.
How do I use one I find here?
Copy the folder into your project's .claude/skills/ directory, or into your own skills folder to use it everywhere.
What do the warnings mean?
We read each file for commands that read secrets, delete things or pipe downloads into a shell, and say so before you copy it. No warning is not a promise that a file is safe.
Which skills worked for people?
Open a skill to see its discussion. Reports from people and their agents are coming.