CtrlK
BlogDocsLog inGet started
Tessl Logo

documentation-criteria

Determines which of PRD, ADR, UI Spec, Design Doc, and Work Plan a change requires, and where each is stored. Use when deciding documentation scope, or when creating or reviewing a technical document.

68

Quality

83%

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

78%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 well-structured routing skill that assumes Claude's competence, provides concrete decision criteria and storage paths, and cleanly separates the routing overview from per-document templates via verified one-level references. Adding a worked example and tightening the rationale prose would lift it further.

Suggestions

Add a short worked example (a sample change → chosen Structural Scale → resulting document path) to move actionability from concrete criteria to fully illustrated guidance.

Tighten the 'What Each Document Fixes' bullets by trimming the explanatory rationale clauses, keeping only the decision class each document fixes and what belongs elsewhere.

Optional: add an explicit verification checkpoint in the build sequence (e.g., 'confirm the chosen path matches the Creation Decision Matrix before creating documents') to strengthen workflow clarity.

DimensionReasoningScore

Conciseness

The body is dense and information-rich without padding basic concepts Claude already knows, but the 'What Each Document Fixes' section is somewhat philosophical ('An unfilled section becomes a guess made later by the consumer...') and could be trimmed, fitting 'efficient; minor instances of over-explanation'.

4 / 5

Actionability

Provides concrete actionable guidance via the Creation Decision Matrix, Structural Scale conditions, numbered ADR Decision Filters, and a Storage Locations table with explicit paths, naming conventions, and template links; the only gap is the absence of a worked routing example showing the criteria applied end-to-end.

4 / 5

Workflow Clarity

A clear ordered build sequence (select base path → insert UI Spec → insert ADR batch) backed by a decision matrix and explicit filters; this is a routing decision rather than a destructive/batch operation so the validation-cap does not apply, but no explicit verification checkpoints keep it just below 5.

4 / 5

Progressive Disclosure

SKILL.md is a focused routing overview that points to six one-level-deep template references via clear links in both the Storage Locations table and a References section, all verified to exist, with content appropriately split between routing logic here and per-document structure in the templates.

5 / 5

Total

17

/

20

Passed

Description

87%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, third-person description that answers both what and when with concrete triggers and a distinctive niche. Minor room to widen the action vocabulary and add synonyms for maximum keyword coverage.

DimensionReasoningScore

Specificity

Names the five concrete document types (PRD, ADR, UI Spec, Design Doc, Work Plan) and two specific actions ('Determines which... a change requires' and 'where each is stored'), but the action set is narrow rather than a breadth of distinct operations, so it sits at 'lists several specific actions; minor gaps' rather than the comprehensive 5.

4 / 5

Completeness

Explicitly states what it does ('Determines which of PRD, ADR, UI Spec, Design Doc, and Work Plan a change requires, and where each is stored') and when to use it via an explicit 'Use when...' clause with concrete triggers, matching the anchor for clear what-and-when with concrete trigger phrases.

5 / 5

Trigger Term Quality

Includes natural trigger phrases ('deciding documentation scope', 'creating or reviewing a technical document') plus the five document-type keywords users would mention, but lacks synonyms and file-extension variants, leaving a few natural terms missing.

4 / 5

Distinctiveness Conflict Risk

Occupies a clear niche (deciding which technical document type a change requires) with distinct, specific triggers and minimal overlap risk with other skills.

5 / 5

Total

18

/

20

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.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
shinpr/claude-code-workflows
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.