How do I install the Docs skill?

Run npx skillmds@latest add willyu1007/docs in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

What does the Docs skill do?

Docs (workflow router) It is listed under Docs & Writing on SkillMD.

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Docs?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

willyu1007 (@willyu1007) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Docs by willyu1007 — Agent Skill

Name: Docs
Author: willyu1007

File contents

Docs (workflow router)

Purpose

Select the correct documentation workflow (authoring vs planning vs handoff) and enforce portability and verifiability.

When to use

Use this skill when you need to:

Write or update developer-facing documentation
Create a repeatable dev-docs bundle for a task
Update dev-docs for handoff, context recovery, or archival

Operating mode (governor)

Select exactly one workflow below.
After selecting, invoke the chosen workflow skill and follow it end-to-end.

Routing (pick one)

If you need...	Use this workflow skill
Author or update developer documentation (guides, APIs, runbooks)	`author-developer-documentation`
Create a new dev-docs task bundle (overview/plan/architecture/notes/verification)	`create-dev-docs-plan`
Update an existing dev-docs bundle for handoff or archive	`update-dev-docs-for-handoff`

Shared non-negotiables

Progressive disclosure
- Keep top-level docs short; move deep detail into supporting files under dev-docs/ or the selected workflow skill’s supporting folders (reference, examples, templates) when present.
No secrets
- Do not include credentials, tokens, or internal-only URLs.
Actionable verification
- Every doc set must include concrete verification steps (commands/checks + expected results).

Steps

Identify whether the intent is: (a) write docs, (b) start a dev task bundle, or (c) handoff/update.
Select exactly one workflow from the routing table.
State the selection explicitly.
Invoke the selected workflow skill and execute it end-to-end.

Verification

Exactly one workflow was selected and executed
Outputs use progressive disclosure (examples/templates for long content)
Verification steps are concrete and reproducible
No secrets or sensitive URLs were included

Boundaries

MUST NOT mix multiple documentation workflows in the same execution pass
MUST NOT include secrets/credentials/tokens in documentation
MUST NOT publish unverifiable instructions

Included assets

None (router only).

---name: docsdescription: Docs (workflow router)---# Docs (workflow router)## PurposeSelect the correct documentation workflow (authoring vs planning vs handoff) and enforce portability and verifiability.## When to useUse this skill when you need to:- Write or update developer-facing documentation- Create a repeatable dev-docs bundle for a task- Update dev-docs for handoff, context recovery, or archival## Operating mode (governor)- Select **exactly one** workflow below.- After selecting, invoke the chosen workflow skill and follow it end-to-end.## Routing (pick one)| If you need... | Use this workflow skill ||---|---|| Author or update developer documentation (guides, APIs, runbooks) | `author-developer-documentation` || Create a new dev-docs task bundle (overview/plan/architecture/notes/verification) | `create-dev-docs-plan` || Update an existing dev-docs bundle for handoff or archive | `update-dev-docs-for-handoff` |## Shared non-negotiables1) **Progressive disclosure** - Keep top-level docs short; move deep detail into supporting files under `dev-docs/` or the selected workflow skill’s supporting folders (reference, examples, templates) when present.2) **No secrets** - Do not include credentials, tokens, or internal-only URLs.3) **Actionable verification** - Every doc set must include concrete verification steps (commands/checks + expected results).## Steps1. Identify whether the intent is: (a) write docs, (b) start a dev task bundle, or (c) handoff/update.2. Select exactly one workflow from the routing table.3. State the selection explicitly.4. Invoke the selected workflow skill and execute it end-to-end.## Verification- [ ] Exactly one workflow was selected and executed- [ ] Outputs use progressive disclosure (examples/templates for long content)- [ ] Verification steps are concrete and reproducible- [ ] No secrets or sensitive URLs were included## Boundaries- MUST NOT mix multiple documentation workflows in the same execution pass- MUST NOT include secrets/credentials/tokens in documentation- MUST NOT publish unverifiable instructions## Included assets- None (router only).

Frequently asked questions

Docs