mjmorales/agentic-doc-writer
skills/agentic-doc-writer/SKILL.md
Generate machine-parseable, LLM-optimized documentation for Claude Code agents. Use when documenting agents, subagents, APIs, modules, or any code that other agents will consume. Triggers include "document this agent", "write agent docs", "create API docs for agents", or when documentation needs to be actionable by LLMs.
$ install --global
skillsauthnpx skillsauth add mjmorales/claude-prove agentic-doc-writerInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: Apr 15, 2026, 11:35 AM30.1s1 file scanned
SKILL.md
- name:
- agentic-doc-writer
- description:
- Generate machine-parseable, LLM-optimized documentation for Claude Code agents. Use when documenting agents, subagents, APIs, modules, or any code that other agents will consume. Triggers include "document this agent", "write agent docs", "create API docs for agents", or when documentation needs to be actionable by LLMs.
Agentic Doc Writer
Generate documentation optimized for LLM consumption. Follow references/interaction-patterns.md for all AskUserQuestion usage.
Workflow
- Identify subject type (agent, API, module, code)
- Gather context -- targeted reads, single pass
- Delegate to
technical-writerwith structured prompt - Review output for contract completeness
Subject Identification
AskUserQuestion header "Subject" if ambiguous. For <=3 choices, include "Research & proceed".
| Subject | Indicators | Key Contracts |
|---------|------------|---------------|
| Agent | .md in agents dir, tools: frontmatter | Triggers, inputs, outputs, workflow |
| API | HTTP handlers, REST/GraphQL endpoints | Request/response schemas, errors |
| Module | Package exports, public interfaces | Parameters, return types, side effects |
| Code | Functions, classes, complex logic | Types, behavior, edge cases |
Context Gathering
- Grep to locate targets, then read specific lines
- Document public interface only -- never follow imports recursively
- Complete all reads before delegating
Delegation to technical-writer
Invoke with:
Document [SUBJECT_TYPE]: [SUBJECT_NAME]
Source: [FILE_PATH]:[LINE_RANGE]
Context:
[MINIMAL RELEVANT CODE/CONFIG]
Requirements:
- Output: [agent-doc | api-doc | module-doc]
- Include: [specific contracts needed]
- Format: YAML frontmatter + structured markdown
Required Contracts by Subject
Agent: Invocation triggers, input contract, output contract (format), workflow steps (numbered), tool permissions
API: Request schema (params, body, headers), response schema (success + error), validation rules, error codes
Module: Public interface (exports only), parameter types/constraints, return types, side effects (I/O, state)
Prove Plugin Documentation
| Component | Document | |-----------|----------| | Skills | Workflow phases, interaction points, references | | Agents | Triggers, tool permissions, model, output format | | Commands | Frontmatter fields, arguments, delegated skill | | Scripts | Usage, flags, output format |
Reference .claude/.prove.json scopes for canonical component list.
Output Validation
Verify before accepting:
- [ ] YAML frontmatter has
name,type - [ ] All contracts from Subject Identification table addressed
- [ ] Examples use concrete values (no
.../foo/bar) - [ ] Error/failure conditions documented
AskUserQuestion header "Quality": "Approve" / "Revise".
Anti-Patterns
| Anti-Pattern | Instead | |--------------|---------| | Verbose examples with inline commentary | Minimal working examples | | Line-by-line code explanation | Document behavior and contracts |
Committing
Delegate to commit skill. Example: docs(agentic-doc-writer): document validation-agent interface
Related Skills
mjmorales/smart-compaction
testing
VerifiedTrustedCommunity
Anchor session context into prove primitives before compaction and rehydrate from them after. Built-in compaction summarizes by recency and drops the claude-prove state an agent needs to reorient; this skill externalizes volatile context into durable anchors (scrum tasks, decisions, run-state, a compact-anchors pointer file) pre-compact, then runs a deterministic reorientation sequence post-compact. Use before a manual /compact, when context is about to auto-compact, or immediately after a compaction. Triggers on "smart compact", "prepare for compaction", "anchor before compact", "context is getting long", "rehydrate", "reorient after compact".
2SKILL.mdUpdated Jun 5, 2026
mjmorales/run-migrate
tools
VerifiedTrustedCommunity
Apply model-driven CONTENT reshaping to stored run artifacts that sit behind the current schema, on explicit operator invocation only. Triggers on "migrate runs", "migrate run artifacts", "run content migration", "reshape run artifacts", "bring runs to current schema". You are the driver: the `run-state migrate-runs` CLI mechanically detects which artifacts are behind and emits a plan naming each one plus its migration-instruction file; you read the instructions and reshape the prose/findings, gated by the operator. The deterministic `schema migrate` handles structural column moves; this skill covers only the content reshaping beyond them. Never run as a background or resident loop — only when the operator asks.
2SKILL.mdUpdated Jun 5, 2026
mjmorales/reasoning-brief
tools
VerifiedTrustedCommunity
Synthesize the 7-section risk-forward Review Brief from a run's reasoning log. Triggers on "reasoning brief", "review brief", "synthesize the brief", "generate the brief", "brief the run", "brief for review", "story brief". You are the driver: the `acb brief` CLI renders a mechanical preservation-safe backbone and proves preservation; you synthesize the narrative prose (summary + changes), single-pass or multipass over episode chunks, then gate it through Stage-1 (mechanical, blocking) and Stage-2 (prose judge, advisory).
2SKILL.mdUpdated Jun 5, 2026
mjmorales/plugin-cache-cleanup
tools
VerifiedTrustedCommunity
Prune stale cached versions of the prove plugin from Claude Code's plugin cache. Use when superseded versions pile up under plugins/cache and agents read stale skills/references from them, or when reclaiming plugin-cache disk space. Triggers on "clean up cached plugin versions", "prune the plugin cache", "remove old prove versions", "stale plugin cache".
2SKILL.mdUpdated Jun 5, 2026