CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

adr-creator

Creates, scores, reviews, supersedes Architecture Decision Records with the pantheon-adr CLI. Use when recording an architectural decision, writing an ADR, documenting a technical choice, checking whether an ADR is finished, superseding a prior decision, bootstrapping an ADR log under docs/adr.

76

Quality

95%

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

92%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.

Excellent tool-driving skill: fully executable commands with expected outputs, a validated multi-step workflow with explicit checkpoints and feedback loops, and clean progressive disclosure to real bundle files. The only notable weakness is redundancy across the Mindset, Principles, Procedure, and Anti-Patterns sections, which repeats several rules and could be consolidated.

Suggestions

Consolidate the duplicated rules: heading immutability, placeholder replacement, and Options Considered requirements each appear in both the Procedure/Principles and the Anti-Patterns sections — state each once and cross-reference.

The 'Mindset' section's prose (e.g., 'Write for a reader six months out') could be tightened to its actionable rules, since the surrounding sections already encode the same guidance as commands and constraints.

DimensionReasoningScore

Conciseness

The body is dense with tool-specific facts Claude cannot know (score thresholds, rubric word counts, slug derivation, heading-cap rules) and avoids explaining general concepts. However, the Principles, Procedure, and Anti-Patterns sections repeat several rules — heading immutability, placeholder handling, and Options Considered each appear twice or more — so it is efficient with minor over-explanation that could be trimmed, matching anchor 4 rather than the lean anchor 5.

4 / 5

Actionability

Every step is a copy-paste-ready command with its expected output (e.g., 'pantheon-adr check adopt-opentelemetry' → 'Score: 100/100 [complete]'), plus exact thresholds (80, 95 with --strict), word counts, file paths, and exit codes. Nothing is pseudocode or hand-wavy.

5 / 5

Workflow Clarity

The 9-step procedure is clearly sequenced with explicit '**Verify:**' checkpoints after risky steps, a '**Stop if:**' guard when Options Considered cannot be filled, and a score-iterate feedback loop (run check, fix, re-run until at least 80). Anti-pattern entries spell out consequences for error recovery.

5 / 5

Progressive Disclosure

The body is a clear overview with well-signaled, one-level-deep references that all exist in the bundle (references/adr-lifecycle.md, references/cli-usage.md, references/context-extraction.md, scripts/check-undocumented-decisions.sh). Bulk CLI detail is correctly split into references, and each link is annotated with what it contains.

5 / 5

Total

19

/

20

Passed

Description

96%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 description: third-person voice, concrete verb-first capability list, and an explicit 'Use when' clause with natural trigger phrases and synonyms. The only weakness is a slightly broad trigger ("documenting a technical choice") that risks minor overlap with general documentation skills.

Suggestions

Tighten the trigger "documenting a technical choice" to something narrower like "documenting an architectural or technical decision" to reduce overlap with general technical-writing requests.

Consider mentioning the listing/status inspection capability (e.g., "lists record status") to round out coverage of what the CLI does.

DimensionReasoningScore

Specificity

The description lists multiple concrete actions covering the full record lifecycle — "Creates, scores, reviews, supersedes Architecture Decision Records" plus bootstrapping under docs/adr. Coverage of the tool's capabilities is comprehensive, matching the anchor-5 pattern rather than leaving minor gaps.

5 / 5

Completeness

It explicitly answers both questions: the first sentence states what the skill does (create/score/review/supersede with the pantheon-adr CLI), and "Use when recording an architectural decision, writing an ADR, ... bootstrapping an ADR log under docs/adr" gives concrete trigger phrases. This matches the anchor-5 example structure.

5 / 5

Trigger Term Quality

It includes comprehensive natural terms with synonyms: "architectural decision", "ADR", "writing an ADR", "documenting a technical choice", "superseding a prior decision", "bootstrapping an ADR log". These are exactly the phrases a user needing this skill would naturally say.

5 / 5

Distinctiveness Conflict Risk

The ADR/pantheon-adr niche is clear and mostly distinct, but the trigger "documenting a technical choice" could plausibly fire on general technical-writing or documentation requests that don't warrant an ADR — a minor overlap risk with related writing/documentation skills, which places it just below anchor 5 and clearly above anchor 3.

4 / 5

Total

19

/

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.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository

pantheon-org/tekhne

Path

skills/documentation/adr-creator/SKILL.md

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.