CtrlK
BlogDocsLog inGet started
Tessl Logo

documentation-standards

Scaffolds issue docs, ADRs, README outlines, changelog entries, roadmap updates, Mermaid architecture diagrams using project templates. Use when drafting ADR, writing changelog, updating roadmap after a feature ships, creating README for a new library, or diagramming a system flow.

72

Quality

89%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

Quality

Content

90%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A tight, highly actionable skill body that gives concrete templates and an executable validation command without padding. Structure and progressive disclosure are good, with minor gaps in explicit error-recovery loops and reference navigation.

Suggestions

Add an explicit feedback loop under Validate: 'If checks fail, fix the flagged links/formatting and re-run until both pass.'

Promote the two external file references into a short '## References' section so navigation is signaled as clearly as the other sections.

DimensionReasoningScore

Conciseness

Lean and efficient with no padding or explanation of concepts Claude already knows; every line is concrete template or directive guidance that earns its place.

5 / 5

Actionability

Provides copy-paste-ready templates with exact headings, field lists, enumerated options, Mermaid directives, and an executable validate command, covering the common documentation cases concretely.

5 / 5

Workflow Clarity

The roadmap completion gives a clear two-step sequence and a Validate section supplies a checkpoint command, but there is no explicit validate→fix→retry feedback loop for failures.

4 / 5

Progressive Disclosure

Well-organized into Templates, Mermaid Diagrams, and Validate sections with clearly labeled one-level-deep references (docs-structure.md, WRITING-GUIDE.md), though the references sit in an intro sentence rather than a dedicated navigation section.

4 / 5

Total

18

/

20

Passed

Description

88%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A strong, concrete description that explicitly covers both capabilities and trigger conditions with natural phrasing. It is comprehensive and mostly distinct, with only minor gaps in trigger synonyms and slight overlap risk on the more generic doc types.

DimensionReasoningScore

Specificity

Lists multiple concrete scaffolding actions — issue docs, ADRs, README outlines, changelog entries, roadmap updates, and Mermaid architecture diagrams — giving comprehensive coverage rather than vague abstractions.

5 / 5

Completeness

Explicitly answers both 'what' (scaffolds the listed doc types using project templates) and 'when' (a 'Use when...' clause with concrete trigger phrases), matching the top anchor.

5 / 5

Trigger Term Quality

Natural trigger phrases like 'drafting ADR', 'writing changelog', 'updating roadmap', 'creating README', and 'diagramming a system flow' match what users would say, though a few synonyms (e.g. 'architecture decision record', 'release notes') are missing.

4 / 5

Distinctiveness Conflict Risk

The specific doc types (ADR, changelog, roadmap) form a clear niche with distinct triggers, but general README/diagramming wording carries minor overlap risk with adjacent writing skills.

4 / 5

Total

18

/

20

Passed

Validation

93%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

relative_links

Relative link issues: 1 missing, 1 suspicious

Warning

Total

15

/

16

Passed

Repository
monkilabs/opencastle
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.