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.
A skill your agent uses when documentation coverage is low, after composer docs:coverage shows gaps, or when asked to batch-write PHPDoc blocks across multiple files
Install Write Docblocks
$ npx skills add aaddrick/claude-pipeline --skill write-docblocks -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install aaddrick/claude-pipeline write-docblocks --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/aaddrick/claude-pipeline.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.claude/skills/write-docblocks .claude/skills/write-docblocks && 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 "write-docblocks" agent skill from https://github.com/aaddrick/claude-pipeline/tree/main/.claude/skills/write-docblocks into .claude/skills/write-docblocks/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "write-docblocks", 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/aaddrick/claude-pipeline/tree/main/.claude/skills/write-docblocksType 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 aaddrick/claude-pipeline --skill write-docblocks -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install aaddrick/claude-pipeline write-docblocks --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/aaddrick/claude-pipeline.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.claude/skills/write-docblocks .agents/skills/write-docblocks && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "write-docblocks" agent skill from https://github.com/aaddrick/claude-pipeline/tree/main/.claude/skills/write-docblocks into .agents/skills/write-docblocks/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "write-docblocks", 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 aaddrick/claude-pipeline --skill write-docblocks -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install aaddrick/claude-pipeline write-docblocks --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/aaddrick/claude-pipeline.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.claude/skills/write-docblocks .cursor/skills/write-docblocks && 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 "write-docblocks" agent skill from https://github.com/aaddrick/claude-pipeline/tree/main/.claude/skills/write-docblocks into .cursor/skills/write-docblocks/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "write-docblocks", 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/aaddrick/claude-pipeline.git --path .claude/skills/write-docblocks--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 aaddrick/claude-pipeline --skill write-docblocks -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install aaddrick/claude-pipeline write-docblocks --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/aaddrick/claude-pipeline.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.claude/skills/write-docblocks .gemini/skills/write-docblocks && 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 "write-docblocks" agent skill from https://github.com/aaddrick/claude-pipeline/tree/main/.claude/skills/write-docblocks into .gemini/skills/write-docblocks/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "write-docblocks", 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 aaddrick/claude-pipeline write-docblocksInstalls 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 aaddrick/claude-pipeline --skill write-docblocks -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/aaddrick/claude-pipeline.git skills-src && mkdir -p .github/skills && cp -r skills-src/.claude/skills/write-docblocks .github/skills/write-docblocks && 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 "write-docblocks" agent skill from https://github.com/aaddrick/claude-pipeline/tree/main/.claude/skills/write-docblocks into .github/skills/write-docblocks/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "write-docblocks", 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 aaddrick/claude-pipeline --skill write-docblocks -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install aaddrick/claude-pipeline write-docblocks --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/aaddrick/claude-pipeline.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.claude/skills/write-docblocks .opencode/skills/write-docblocks && 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 "write-docblocks" agent skill from https://github.com/aaddrick/claude-pipeline/tree/main/.claude/skills/write-docblocks into .opencode/skills/write-docblocks/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "write-docblocks", 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
write-docblocks- GitHub stars
- 130
- Token cost
- ~956 tokens
- SKILL.md length
- 234 words
- Files
- 1
- Skills in repo
- 12
- Repo updated
- First seen
- Licence
- MIT
At a glance
A skill your agent uses when documentation coverage is low, after composer docs:coverage shows gaps, or when asked to batch-write PHPDoc blocks across multiple files
- Works in 5 steps: Get Missing Files → Process in Batches of 5 → Wait for Batch Completion → …
- Documentation coverage is low
- SKILL.md covers Overview, When to Use, Workflow and Execution Steps, plus 2 more sections
- Calls composer
What it does
Write Docblocks is an agent skill from aaddrick/claude-pipeline. Use when documentation coverage is low, after composer docs:coverage shows gaps, or when asked to batch-write PHPDoc blocks across multiple files
Its SKILL.md is about 960 tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in Agent Workflows. The repository describes itself as: Portable Claude Code multi-agent pipeline - skills, agents, hooks, orchestration scripts, and quality gates. The licence is MIT.
When your agent uses it
- Documentation coverage is low
- After composer docs:coverage shows gaps
- Asked to batch-write PHPDoc blocks across multiple files
Example prompts
- “/write-docblocks”
Workflow steps
5 steps, taken from the step headings in SKILL.md.
What it can do on your machine
Read from SKILL.md and the folder at commit 402eac7. 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
Shell commands in SKILL.md call:
composer
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
Write Docblocks loads about 956 tokens when it runs. Until then it costs about 40 tokens; SKILL.md has 234 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 aaddrick/claude-pipeline at commit 402eac7, republished under its MIT licence (© aaddrick). 234 words, ~956 tokens.
Download SKILL.mdSave it as
.claude/skills/write-docblocks/SKILL.md (or your agent's skills folder).- name
- write-docblocks
- description
- Use when documentation coverage is low, after composer docs:coverage shows gaps, or when asked to batch-write PHPDoc blocks across multiple files
Write Docblocks
Overview
Batch-process PHPDoc documentation gaps by running composer docs:coverage:missing and dispatching parallel phpdoc-writer subagents.
Core principle: Process files in batches of 5 subagents for efficient parallel documentation without overwhelming the system.
When to Use
- Documentation coverage below target (80% classes, 75% methods)
- After creating multiple new services, controllers, or models
- When
composer docs:coverage:missingshows many files needing docs - User requests batch PHPDoc writing
Workflow
digraph write_docblocks {
rankdir=TB;
start [label="Run composer docs:coverage:missing" shape=box];
parse [label="Parse output for file paths" shape=box];
check [label="Files remaining?" shape=diamond];
batch [label="Take next 5 files" shape=box];
dispatch [label="Dispatch 5 phpdoc-writer\nsubagents in parallel" shape=box];
wait [label="Wait for batch to complete" shape=box];
done [label="Run composer docs:coverage\nto verify improvement" shape=box];
start -> parse -> check;
check -> batch [label="yes"];
check -> done [label="no"];
batch -> dispatch -> wait -> check;
}Execution Steps
1. Get Missing Files
composer docs:coverage:missing 2>&1 | sed 's/\x1b\[[0-9;]*m//g' | grep '\.php$'This strips ANSI codes and extracts just file paths like:
Console/Commands/ProcessDataCommand.php
Http/Controllers/AuthController.php
Services/AuthService.php2. Process in Batches of 5
For each batch of 5 files, dispatch phpdoc-writer subagents in parallel using a single message with multiple Task tool calls:
Task(subagent_type="phpdoc-writer", prompt="Write PHPDoc blocks for app/Console/Commands/ProcessDataCommand.php - read the file, understand its purpose, and add comprehensive docblocks for the class and all undocumented methods.")
Task(subagent_type="phpdoc-writer", prompt="Write PHPDoc blocks for app/Http/Controllers/OAuthController.php - read the file, understand its purpose, and add comprehensive docblocks for the class and all undocumented methods.")
// ... 3 more in same messageCRITICAL: All 5 Task calls MUST be in a single assistant message to run in parallel.
3. Wait for Batch Completion
Wait for all 5 subagents to complete before starting the next batch. This prevents resource exhaustion while maintaining parallelism.
4. Repeat Until Done
Continue processing batches until all files are documented.
5. Verify Coverage
composer docs:coverageConfirm improvement toward targets (80% classes, 75% methods).
Subagent Prompt Template
Write PHPDoc blocks for app/{PATH}
1. Read the file thoroughly to understand its purpose
2. Check what's already documented vs missing
3. Add comprehensive docblocks for:
- Class-level documentation explaining purpose and context
- All undocumented public methods with @param, @return, @throws
- Protected/private methods with brief explanations
4. Follow project-specific conventions and domain terminology
5. Run pint after editing: ./vendor/bin/pint {file}
Target audience: New developer on their first day.Common Mistakes
Dispatching sequentially: Each file one at a time wastes time. Use batches of 5 in parallel.
Not using single message: Multiple Task calls in separate messages run sequentially. Put all 5 in ONE message.
Skipping verification: Always run composer docs:coverage at the end to confirm improvement.
Forgetting pint: Subagents should run ./vendor/bin/pint after editing to maintain code style.
© aaddrick, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
Just SKILL.md in .claude/skills/write-docblocks of aaddrick/claude-pipeline.
Open the folder on GitHubat commit 402eac7
Compare with similar skills
Write Docblocks 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 |
|---|---|---|---|---|---|---|
| Write Docblocks this skillaaddrick/claude-pipeline | 130 | — | ~956 | 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 aaddrick/claude-pipeline
All 12 skills in this repoWriting Agents
aaddrick/claude-pipeline
A skill your agent uses when creating new agents, editing existing agents, or defining specialized subagent roles for the Task tool
Adapting Claude Pipeline
aaddrick/claude-pipeline
A skill your agent uses when adapting the generic .claude pipeline folder to a specific codebase - adjusting skills, agents, hooks, scripts, prompts, and settings for the target project's tech stack…
Investigating Codebase For User Stories
aaddrick/claude-pipeline
A skill your agent uses when asked to create user stories from a codebase, document existing features as stories, or reverse-engineer requirements from code
Review UI
aaddrick/claude-pipeline
Comprehensive UI/CSS review using parallel agents. An agent skill from aaddrick/claude-pipeline.
Using Git Worktrees
aaddrick/claude-pipeline
A skill your agent uses when starting feature work that needs isolation from current workspace or before executing implementation plans - creates isolated git worktrees in .worktrees/
Implement Issue
aaddrick/claude-pipeline
A skill your agent uses when given a GitHub issue number and base branch to implement end-to-end
Related
Categories
Questions about Write Docblocks
What does Write Docblocks do?
A skill your agent uses when documentation coverage is low, after composer docs:coverage shows gaps, or when asked to batch-write PHPDoc blocks across multiple files. Write Docblocks is an agent skill from aaddrick/claude-pipeline.
When should I use Write Docblocks?
Write Docblocks fits situations like: documentation coverage is low; after composer docs:coverage shows gaps; asked to batch-write PHPDoc blocks across multiple files.
How do I install Write Docblocks in Claude Code?
Run `npx skills add aaddrick/claude-pipeline --skill write-docblocks -a claude-code`. Or copy the skill folder (.claude/skills/write-docblocks in aaddrick/claude-pipeline) into .claude/skills/write-docblocks in your project. Claude Code loads it when a task matches its description.
How do I install Write Docblocks in Codex?
Run `npx skills add aaddrick/claude-pipeline --skill write-docblocks -a codex`. Or copy the skill folder (.claude/skills/write-docblocks in aaddrick/claude-pipeline) into .agents/skills/write-docblocks in your project. Codex loads it when a task matches its description.
Can I use Write Docblocks 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 aaddrick/claude-pipeline --skill write-docblocks -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/write-docblocks, .gemini/skills/write-docblocks, .github/skills/write-docblocks and .opencode/skills/write-docblocks in your project.
What does Write Docblocks need to run?
Going by SKILL.md and its folder, Write Docblocks needs the command-line tools its instructions call (composer).
Does Write Docblocks 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 Write Docblocks 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 Write Docblocks use?
Write Docblocks 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 Write Docblocks use?
About 956 tokens (SKILL.md is roughly 3.8k 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 Write Docblocks?
Skills that share tags, products or a category with Write Docblocks: 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 Write Docblocks?
aaddrick (a GitHub user) maintains it in aaddrick/claude-pipeline, which has 130 GitHub stars. The repository holds 12 skills in this directory. The repository was last updated on February 25, 2026.
Source: aaddrick/claude-pipeline on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.