agentleFS
Sign inStart free
drafthqdrafthq/draft/skills/docs/SKILL.md

docs

Skill40 starsChanged 4 months agoMITView on GitHub

Primary router for authoring and documentation workflows. Analyzes intent and dispatches primarily to documentation (technical docs, readme, runbook, api, onboarding). Use when the user needs to generate or update project documentation.

165 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use import-memory, perf and 8 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • amirbironSkill

    import-memory

    Import a memory export from another AI assistant into Claude's memory — conversationally, additively, and with the content treated as data.

    Also in 3 projects that use this

  • MicrosoftSkill

    perf

    Speed and memory performance rules for Rust crates, the Node addon, webui-framework, and webui-delivery.

    Also in 4 projects that use this

  • diego-tobalinaSkill

    build-fix

    Fix build and compilation errors systematically. Run when build fails.

    Also in 3 projects that use this

  • JkudjoSkill

    incident

    Production incident response — structured triage, hypothesis tree, safe remediation, incident record

    Also in 4 projects that use this

  • vbrevikSkill

    work

    Use when the user says 'plan', 'todo', 'copy plan', 'append plan', 'resume plan', 'priorities', or 'what's next'.

    Also in 7 projects that use this

  • Google CloudSkill

    fix

    Plan a remediation strategy after a test failure.

    Also in 7 projects that use this

The file

We split this skill into the rules it gives an agent

1 rule. 0 are common, 0 are distinctive, and 1 is very specific to this project.

  • 0

    Common

    Most of the 129 edited versions we read keep these.

  • 0

    Distinctive

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Prefer /draft:docs going forward for all authoring requests.

    line 42

“Common” is measured: kept by at least 6 in 10 of the 129 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Docs - Authoring & Documentation Router

/draft:docs provides a single namespace for all documentation generation and maintenance tasks.

When to Use

  • Generating or refreshing README, API docs, runbooks, or onboarding guides
  • Producing technical documentation from existing architecture and code context
  • Keeping documentation in sync after implementation or review phases

Routing Logic

Currently focused on the documentation specialist. Future expansion may include additional authoring helpers under the same router.

User Intent KeywordsDispatches ToPurpose
write docs, documentation, readme, runbook, api docs, onboarding guide, generate docs/draft:documentationTechnical documentation authoring (readme, runbook, api, onboarding)

Dispatch Examples

User: "write a README for the new service"

→ dispatches to /draft:documentation readme

User: "generate an API reference and runbook for the billing module"

→ dispatches to /draft:documentation api runbook

User: "create onboarding guide for new engineers"

→ dispatches to /draft:documentation onboarding

Notes

The documentation command reads heavily from draft/architecture.md, draft/.ai-context.md, draft/product.md, and draft/tech-stack.md (plus graph artifacts when present).

Prefer /draft:docs going forward for all authoring requests. The legacy direct form remains for compatibility (see migration guidance).

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free