Scaffolds issue docs, ADRs, README outlines, changelog entries, roadmap updates, and Mermaid architecture diagrams using project templates. Use when drafting an ADR, writing a changelog, updating the roadmap after a feature ships, creating a README for a new library, or diagramming a system flow.
100
100%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Passed
No known issues
Quality
Discovery
100%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This is a strong skill description that clearly enumerates specific documentation artifacts it can produce, uses natural trigger terms that users would actually say, and includes an explicit 'Use when...' clause with diverse trigger scenarios. It is well-scoped to a distinct niche of project documentation scaffolding, minimizing conflict risk with other skills.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: scaffolding issue docs, ADRs, README outlines, changelog entries, roadmap updates, and Mermaid architecture diagrams. Also specifies the mechanism ('using project templates'). | 3 / 3 |
Completeness | Clearly answers both 'what' (scaffolds issue docs, ADRs, README outlines, changelog entries, roadmap updates, Mermaid diagrams using project templates) and 'when' with an explicit 'Use when...' clause listing five concrete trigger scenarios. | 3 / 3 |
Trigger Term Quality | Includes highly natural trigger terms users would say: 'ADR', 'changelog', 'roadmap', 'README', 'Mermaid', 'architecture diagrams', 'issue docs', 'system flow', 'feature ships'. These cover a broad range of natural user phrasings for documentation tasks. | 3 / 3 |
Distinctiveness Conflict Risk | Targets a clear niche of project documentation artifacts (ADRs, changelogs, roadmaps, Mermaid diagrams) using templates. The specificity of document types like ADRs and Mermaid architecture diagrams makes it unlikely to conflict with general documentation or coding skills. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
100%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a well-crafted skill that provides concrete, copy-paste-ready templates for multiple documentation types while remaining concise and well-organized. The workflow section includes proper validation with feedback loops, and content is appropriately split between inline templates and external references. Minor improvement opportunities exist but the skill is strong across all dimensions.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is lean and template-focused. It doesn't explain what ADRs, changelogs, or Mermaid diagrams are — it assumes Claude knows and just provides the templates and conventions. Every section earns its place. | 3 / 3 |
Actionability | Templates are concrete and copy-paste ready with clear placeholder patterns. The Mermaid example is executable, the changelog format is specific with Conventional Commits grouping, and the validation commands are real runnable commands. | 3 / 3 |
Workflow Clarity | The documentation workflow section provides a clear 5-step sequence with an explicit validation checkpoint (step 2), a feedback loop (fail → fix → re-run), and a pre-merge checklist. This covers the necessary verification for document operations. | 3 / 3 |
Progressive Disclosure | The skill provides a clear overview with well-signaled one-level-deep references to docs-structure.md and WRITING-GUIDE.md. Templates are inline (appropriate since they're the core content), while detailed writing guidelines and project-specific structure are properly externalized. | 3 / 3 |
Total | 12 / 12 Passed |
Validation
100%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 11 / 11 Passed
Validation for skill structure
No warnings or errors.
f5c8508
Table of Contents
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.