documentation-standards
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.
77
96%
Does it follow best practices?
Impact
—
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 an excellent skill description that clearly enumerates specific document types it handles, uses natural trigger terms that users would actually say, and includes an explicit 'Use when...' clause with diverse 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 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'. These cover a broad range of natural user language for documentation tasks. | 3 / 3 |
Distinctiveness Conflict Risk | Targets a clear niche of project documentation scaffolding with distinct artifact types (ADRs, changelogs, roadmaps, Mermaid diagrams). The specificity of these document types and the mention of 'project templates' makes it unlikely to conflict with general coding or writing skills. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
92%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a strong, well-structured skill that provides concrete, copy-paste-ready templates for six documentation types. The workflow section includes proper validation with feedback loops, and the content is concise without over-explaining concepts Claude already knows. The main weakness is that all templates are inline rather than referenced from separate files, making the skill longer than ideal for an overview, and the two external references cannot be verified against bundle files.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is lean and template-driven. It avoids explaining what ADRs, changelogs, or Mermaid diagrams are—it assumes Claude knows and just provides the exact templates and conventions to follow. Every section earns its place. | 3 / 3 |
Actionability | Each document type has a concrete, copy-paste-ready markdown template with placeholder fields. The Mermaid section includes an executable diagram example, the changelog shows exact formatting, and the roadmap update gives a specific structured example. Guidance is specific and directly usable. | 3 / 3 |
Workflow Clarity | The 'Documentation workflow' section provides a clear 5-step sequence with an explicit validation checkpoint (step 2) that includes a concrete command, a feedback loop (fail → fix → re-run), and a pre-merge checklist. This covers the key destructive/batch concern of publishing bad docs. | 3 / 3 |
Progressive Disclosure | The skill references two external files (docs-structure.md and WRITING-GUIDE.md) which is good progressive disclosure, but no bundle files were provided to verify these exist. The main content is well-organized with clear sections, but the templates are all inline rather than split into separate reference files, making the skill somewhat long for an overview document. | 2 / 3 |
Total | 11 / 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.
- Repository
- monkilabs/opencastle
- Commit
cc13aaf
- Reviewed
Table of Contents
Is this your skill?
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.