MCP Server Builder
anthropics/skills
Guides the design and implementation of Model Context Protocol servers in TypeScript or Python, from tool naming and error messages to evaluation.
Audit documentation and developer experience against the live product — drift, onboarding, error messages — and write or fix docs when asked.
Install Docs
$ npx skills add automagik-dev/genie --skill docs -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install automagik-dev/genie docs --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/automagik-dev/genie.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/docs .claude/skills/docs && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "docs" agent skill from https://github.com/automagik-dev/genie/tree/main/skills/docs into .claude/skills/docs/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "docs", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/automagik-dev/genie/tree/main/skills/docsType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add automagik-dev/genie --skill docs -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install automagik-dev/genie docs --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/automagik-dev/genie.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/docs .agents/skills/docs && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "docs" agent skill from https://github.com/automagik-dev/genie/tree/main/skills/docs into .agents/skills/docs/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "docs", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add automagik-dev/genie --skill docs -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install automagik-dev/genie docs --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/automagik-dev/genie.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/docs .cursor/skills/docs && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "docs" agent skill from https://github.com/automagik-dev/genie/tree/main/skills/docs into .cursor/skills/docs/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "docs", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/automagik-dev/genie.git --path skills/docs--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add automagik-dev/genie --skill docs -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install automagik-dev/genie docs --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/automagik-dev/genie.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/docs .gemini/skills/docs && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "docs" agent skill from https://github.com/automagik-dev/genie/tree/main/skills/docs into .gemini/skills/docs/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "docs", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install automagik-dev/genie docsInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add automagik-dev/genie --skill docs -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/automagik-dev/genie.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/docs .github/skills/docs && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "docs" agent skill from https://github.com/automagik-dev/genie/tree/main/skills/docs into .github/skills/docs/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "docs", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add automagik-dev/genie --skill docs -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install automagik-dev/genie docs --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/automagik-dev/genie.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/docs .opencode/skills/docs && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "docs" agent skill from https://github.com/automagik-dev/genie/tree/main/skills/docs into .opencode/skills/docs/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "docs", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
docs- GitHub stars
- 345
- Token cost
- ~1.3k tokens
- SKILL.md length
- 759 words
- Files
- 2
- Skills in repo
- 19
- Repo updated
- First seen
- Licence
- MIT
At a glance
Audit documentation and developer experience against the live product — drift, onboarding, error messages — and write or fix docs when asked.
- Agent Workflows work in your project
- SKILL.md covers When to use, Surfaces, The contributor test and Write, plus 2 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Docs is an agent skill from automagik-dev/genie. Audit documentation and developer experience against the live product — drift, onboarding, error messages — and write or fix docs when asked.
Its SKILL.md is about 1.3k tokens, which your agent loads only when the skill is triggered. The skill folder holds 2 other files (for example `agents/openai.yaml`).
It sits in Agent Workflows. The repository describes itself as: Wishes in, PRs out. CLI agent that interviews you, plans the work, dispatches parallel agents in isolated worktrees, and reviews code before you see it. The licence is MIT.
When your agent uses it
- Agent Workflows work in your project
Example prompts
- “/docs”
What it can do on your machine
Read from SKILL.md and the folder at commit c4f8788. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md.
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Docs loads about 1.3k tokens when it runs. Until then it costs about 37 tokens; SKILL.md has 759 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from automagik-dev/genie at commit c4f8788, republished under its MIT licence (© automagik-dev). 759 words, ~1,326 tokens.
Download SKILL.mdSave it as
.claude/skills/docs/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.- name
- docs
- description
- Audit documentation and developer experience against the live product — drift, onboarding, error messages — and write or fix docs when asked.
- category
- authoring
- mutates
- repo
Docs
Assess by default; write only when the request asks. Documentation is judged by use: a page that cannot be followed is worse than none. The live interface (the real --help output, routes, exports) is the truth; every README table, guide, and agent-context file is a claim to check against it.
The assessment half is a saved workflow, not a procedure this skill performs inline. Its single source of truth is .claude/workflows/docs-audit.js in the genie repository's canonical workflow catalog (see .claude/workflows/README.md there); this skill is its front door. On a runtime that runs saved workflows, run the script at <repository root>/.claude/workflows/docs-audit.js when that file exists, otherwise ~/.claude/workflows/docs-audit.js (delivered by genie install / genie update); give the runtime that explicit script path, never a bare name — both scopes now carry these names and the order a name resolves in is undocumented. Pass {focus?, surfaces?, quorum?, model?, timestamp?} — every key optional, and with no surfaces list the audit runs the full four-surface roster of the table below. The workflow probes read-only: it asks nothing, writes nothing, and moves no file. Relay the returned report unchanged, and list notConvened (agents that returned nothing) beside the unread (paths no auditor could read) and unprobed (documented claims no auditor could probe read-only) lists rather than filling any of the three gaps yourself.
When to use
- Modules, APIs, or workflows are undocumented, or docs describe removed behavior.
- Code changed in ways the docs describe, or a wish deliverable includes documentation.
- Someone wants the contributor experience audited: onboarding, drift, error messages.
Surfaces
The four keys are the audit's shard roster: surfaces narrows it, never grows it, and a key it drops is named as a gap.
| Surface | Key | Where |
|---|---|---|
| README | readme | README.md, */README.md |
| Agent instructions | agent-instructions | AGENTS.md (governing), CLAUDE.md + .claude/rules/*.md (Claude overlays; keep current) |
| Reference and architecture | docs-architecture | docs/, ARCHITECTURE.md, inline JSDoc/TSDoc |
| Runtime DX | runtime-dx | --help text, error messages, onboarding path in README/CONTRIBUTING |
The workflow resolves where docs live before judging them — in-repo, a submodule behind a symlink, or a separate site — and stamps that route into every auditor, so a fix never says "edit here" when the docs live elsewhere. Internal pages deliberately excluded from a public site are design, not gaps.
The contributor test
This stays here, with you, and never reaches the workflow. When onboarding is in scope, follow the written path verbatim as a fresh reader: from clone to the first passing check, one serial walk, logging every divergence. It installs and builds, so it is never parallelised and never delegated to a shard. Hold the repo to its own stated bar, and freeze what you learned into focus before the call rather than asking the workflow to re-derive it.
Show full SKILL.md (313 more words)Show less
Write
When asked, fill gaps in the project's existing style through its documented docs workflow, whatever that repository states it to be — in the genie repository, for instance, the vendored docs submodule flow its agent-instructions file records: edit under docs/, commit and push inside the submodule, open the pull request against the docs remote, then bump the superproject pointer once it merges. Never document features that do not exist; every referenced path, API, and behavior must be verified real. Write to the reader's decision boundary: what they need to decide, do, observe, and verify. Keep internal mechanism out of operator pages unless it changes a decision, a safety boundary, or a troubleshooting step.
Without a workflow surface
On a runtime with no workflow surface, dispatch the same four stages by hand and carry no roster the script does not. Locate: one read-only agent resolves the docs home, its other true names, the public/internal split and the fix workflow, each claim carrying the read-only command that proved it. Audit: one auditor per row of the Surfaces table, each carrying several checks over its whole surface and quoting both the documented claim and the live behaviour. Consolidate: one judge sees every responding auditor at once, collapses one root drift restated on three surfaces into a single row, settles severity conflicts, and ranks by which blocker a reader hits first. Render: draw the table, the docs-home routing line, the duplicate list and the unread/unprobed lists yourself. An auditor that returns nothing is reported, never inferred.
Report
Lead with the verdict: did the contributor test pass, what is the worst drift. Then the ranked table with evidence (both sides of each drift, the exact stumble step, the quoted error message) and concrete fixes routed through the real workflow. Say what was verified current and what was skipped. Report only what was checked or written in this session.
© automagik-dev, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
SKILL.md and 1 other file in skills/docs of automagik-dev/genie.
- SKILL.md
- agents/openai.yaml
Open the folder on GitHubat commit c4f8788
Compare with similar skills
Docs next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Docs this skillautomagik-dev/genie | 345 | — | ~1.3k | Automated safety check: Pass | MIT | |
| MCP Server Builderanthropics/skills | 180k | 62 repos | ~2.3k | Automated safety check: Pass | Apache-2.0 | |
| Hook Development for Claude Code Pluginsanthropics/claude-plugins-official | 37k | 11 repos | ~4.1k | Automated safety check: Notes | Apache-2.0 | |
| Using Superpowersfarm-fe/farm | 5.6k | 34 repos | ~1.4k | Automated safety check: Pass | MIT | |
| Executing Plans Inlineobra/superpowers | 296k | 2 repos | ~5.1k | Automated safety check: Pass | MIT | |
| Claude Code Agent Developmentanthropics/claude-plugins-official | 37k | 8 repos | ~2.8k | Automated safety check: Pass | Apache-2.0 |
Similar skills
- Official
- Official
Hook Development for Claude Code Plugins
anthropics/claude-plugins-official
Explains how to write Claude Code plugin hooks, both prompt-based checks and bash commands, for events such as PreToolUse, Stop and SessionStart.
Using Superpowers
farm-fe/farm
A skill your agent uses when starting any conversation - establishes how to find and use skills, requiring Skill tool invocation before ANY response including clarifying questions
Executing Plans Inline
obra/superpowers
Has the agent carry out an implementation plan itself, task by task in the current session, keeping a ledger, proving each step with a test and ending with one whole-branch review.
- Official
Claude Code Agent Development
anthropics/claude-plugins-official
Explains how to write agents for Claude Code plugins: the markdown file with YAML frontmatter, trigger descriptions, model and color settings, and system prompt design.
- Official
Skill Creator
Azure/azqr
Create new skills, modify and improve existing skills, and measure skill performance.
More from automagik-dev/genie
All 19 skills in this repoLearn
automagik-dev/genie
Diagnose and fix agent behavioral surfaces when the user corrects a mistake — connects to Claude native memory.
Brainstorm
automagik-dev/genie
Explore an ambiguous idea with the user, settle scope and success criteria, and produce an independently reviewed design for wish.
Report
automagik-dev/genie
Investigate a failure to its root cause with grounded evidence, hand the diagnosis to fix, and create a GitHub issue only when asked.
Wish
automagik-dev/genie
Deliver one decided task end to end — admit it, work it in one worktree, gate, independent review, bounded repair, a merge-ready PR — or plan a multi-group wish when it is bigger than one task.
Work
automagik-dev/genie
Execute an approved wish in dependency order with scoped workers, independent review, bounded repairs, and verified completion.
Authoring
automagik-dev/genie
Write or revise a Genie skill so it survives the shipped contract — frontmatter, house size, starter card, and runtime-neutral voice.
Related
Categories
Questions about Docs
What does Docs do?
Audit documentation and developer experience against the live product — drift, onboarding, error messages — and write or fix docs when asked. Docs is an agent skill from automagik-dev/genie. Audit documentation and developer experience against the live product — drift, onboarding, error messages — and write or fix docs when asked.
When should I use Docs?
Docs fits situations like: agent Workflows work in your project.
How do I install Docs in Claude Code?
Run `npx skills add automagik-dev/genie --skill docs -a claude-code`. Or copy the skill folder (skills/docs in automagik-dev/genie) into .claude/skills/docs in your project. Claude Code loads it when a task matches its description.
How do I install Docs in Codex?
Run `npx skills add automagik-dev/genie --skill docs -a codex`. Or copy the skill folder (skills/docs in automagik-dev/genie) into .agents/skills/docs in your project. Codex loads it when a task matches its description.
Can I use Docs in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add automagik-dev/genie --skill docs -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/docs, .gemini/skills/docs, .github/skills/docs and .opencode/skills/docs in your project.
What does Docs need to run?
SKILL.md names no scripts, command-line tools or credentials: Docs is instructions for the agent only.
Does Docs access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Docs safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Docs use?
Docs is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Docs use?
About 1.3k tokens (SKILL.md is roughly 5.3k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Docs?
Skills that share tags, products or a category with Docs: MCP Server Builder (anthropics/skills, 180k stars), Hook Development for Claude Code Plugins (anthropics/claude-plugins-official, 37k stars), Using Superpowers (farm-fe/farm, 5.6k stars) and Executing Plans Inline (obra/superpowers, 296k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Docs?
automagik-dev (a GitHub organization) maintains it in automagik-dev/genie, which has 345 GitHub stars. The repository holds 19 skills in this directory. The repository was last updated on October 7, 2026.
Source: automagik-dev/genie on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.