Skillzwave Logo
Skillzwave

documentation-specialist

1 stars 3 forks
94
A

This skill should be used when creating professional software documentation (SRS, PRD, OpenAPI,user manuals, tutorials, runbooks) from templates (greenfield) or reverse-engineering documentationfrom existing code like Spring Boot or FastAPI (brownfield). Also handles documentation audits/reviews,format conversion (Markdown, DOCX, PDF), and diagram generation (C4, Mermaid, PlantUML, ER, sequence).Use when asked to "create documentation", "document my code", "write SRS", "generate PRD", or ...

#references#claude-code-skill#software documentation#Start Software#skill#templates#Markdown#agentic-skill

Third-Party Agent Skill: Review the code before installing. Agent skills execute in your AI assistant's environment and can access your files. Learn more about security

Installation for Agentic Skill

View all platforms →
skilz install SpillwaveSolutions/document-specialist-skill/documentation-specialist
skilz install SpillwaveSolutions/document-specialist-skill/documentation-specialist --agent opencode
skilz install SpillwaveSolutions/document-specialist-skill/documentation-specialist --agent codex
skilz install SpillwaveSolutions/document-specialist-skill/documentation-specialist --agent gemini

First time? Install Skilz: pip install skilz

Works with 22+ AI coding assistants

Cursor, Aider, Copilot, Windsurf, Qwen, Kimi, and more...

View All Agents
Download Agent Skill ZIP

Extract and copy to ~/.claude/skills/ then restart Claude Desktop

1. Clone the repository:
git clone https://github.com/SpillwaveSolutions/document-specialist-skill
2. Copy the agent skill directory:
cp -r document-specialist-skill ~/.claude/skills/
View on GitHub

Need detailed installation help? Check our platform-specific guides:

Claude Desktop Guide Claude Code Guide Troubleshooting

Related Agentic Skills

automating-mail

by SpillwaveSolutions

Automates Apple Mail via JXA with AppleScript dictionary discovery. Use when asked to "automate email", "send mail via script", "JXA Mail automatio...

100
Marketplace

automating-reminders

by SpillwaveSolutions

Automates Apple Reminders using JavaScript for Automation (JXA). Use when asked to "create reminders programmatically", "automate reminder lists", ...

100
Marketplace

mastering-postgresql

by SpillwaveSolutions

PostgreSQL development for Python with full-text search (tsvector, tsquery, BM25 via pg_search), vector similarity (pgvector with HNSW/IVFFlat), JS...

100
Marketplace

automating-contacts

by SpillwaveSolutions

Automates macOS Contacts via JXA with AppleScript dictionary discovery. Use when asked to "automate contacts", "JXA contacts automation", "macOS ad...

99
Marketplace

Agentic Skill Details

Owner
SpillwaveSolutions (GitHub)
Repository
document-specialist-skill
Stars
1
Forks
3
Type
Other
Meta-Domain
Primary Domain
Market Score
94
Agentic Skill Grades →

Agent Skill Grade

A
Score: 94/100 Click to see breakdown

Score Breakdown

Spec Compliance
14/15
PDA Architecture
28/30
Ease of Use
23/25
Writing Style
9/10
Utility
18/20
Modifiers: +2

Areas to Improve

  • TOC missing in SKILL.md
  • Examples TOC references non-existent files
  • Redundant TOC information

Recommendations

  • Add trigger phrases to description for discoverability
  • Add table of contents for files over 100 lines

Graded: 2026-01-19

Developer Feedback

I took a look at your documentation-specialist skill and wanted to share some thoughts.

Links:

The TL;DR

You're at 94/100, solid A territory. This is based on Anthropic's PDA framework and best practices for agentic skills. Your strongest area is Spec Compliance (14/15) – you nailed the frontmatter and conventions. Weakest is Utility (18/20) – a few edge cases and some broken example references holding you back from a perfect score.

What's Working Well

  • Progressive Disclosure Architecture is chef's kiss – Your 3-tier structure (SKILL.md → workflows → templates/references) is textbook PDA. The routing hub at 139 lines keeps token load lean, and everything loads on-demand exactly as intended.

  • Trigger phrases are comprehensive – You've got 5+ distinct intents covered ("create documentation", "document my code", "write SRS", "generate PRD", "documentation specialist"). Users will find this skill easily.

  • Examples and templates are real – 380+ lines in billing-srs.md with actual Gherkin acceptance criteria, runbooks with step-by-step instructions, getting-started guides. This isn't template-ware – it's production-ready documentation people can actually use.

The Big One: Broken Example References

Your examples/TOC.md references files that don't exist in the actual structure – specifically greenfield/ecommerce-sdd.md and brownfield subdirectories that aren't there. When users try to navigate to these, they'll hit dead ends.

Why it matters: Breaks discoverability and makes the skill feel incomplete. Users exploring examples won't find what they're looking for.

The fix: Audit references/examples/TOC.md and either create the missing files (if in...

AI-Detected Topics

Extracted using NLP analysis

references claude-code-skill software documentation Start Software skill templates Markdown agentic-skill documentation documentation specialist

Report Security Issue

Found a security vulnerability in this agent skill?