CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

adr

Keep track of architectural decisions in a structured format using Architecture Decision Records (ADRs).

Quality

78%

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

Fix and improve this skill with Tessl

tessl review fix ./.agents/skills/adr/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

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

The body is an exemplary lean instruction skill: concrete workflows, a copy-paste-ready template, and precise conventions with no padding. The only gap is the absence of an explicit validation step after writing/updating ADRs and the index.

DimensionReasoningScore

Conciseness

The ~80-line body is lean with zero concept explanations — every section (directory layout, workflows, naming, template, TOC format) adds information Claude would not infer on its own. It assumes competence and every token earns its place.

5 / 5

Actionability

Guidance is fully executable for an instruction-only skill: a copy-paste-ready ADR template, a concrete file-naming pattern ("ADR-{NNN}-{kebab-case-slug}.md" with zero-padding rules), and an exact TOC table row example. The create/update/supersede workflows each give specific, direct steps including the FDR sweep.

5 / 5

Workflow Clarity

Three multi-step workflows (create, update, supersede) are clearly sequenced with an index-reading checkpoint up front, but there is no explicit post-write verification step (e.g. confirming the new ADR appears in the TOC or that numbering is unique). Not 5 for missing validation checkpoints; not 3 since sequences are complete and unambiguous, and no destructive/batch operation triggers the cap.

4 / 5

Progressive Disclosure

The skill has no bundle files and no content that belongs in a separate reference — the template, naming, and TOC format are exactly the inline material needed. Sections are well-organized and self-contained, and it correctly points to workspace artifacts (docs/adr/INDEX.md) rather than burying detail.

5 / 5

Total

19

/

20

Passed

Description

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

The description clearly states what the skill does and occupies a distinct niche, but it omits any 'when to use' trigger guidance and lacks keyword variations and specific capability verbs. It reads as a competent one-sentence summary rather than a complete trigger-optimized description.

Suggestions

Add an explicit trigger clause, e.g. "Use when the user mentions architectural decisions, ADRs, decision records, or asks to document/supersede a design decision."

Enumerate the concrete capabilities (create ADRs from a template, maintain the index, supersede old decisions) instead of the generic "keep track of".

Include natural synonyms such as "design decisions", "decision log", and "decision records" to broaden trigger-term coverage.

DimensionReasoningScore

Specificity

"Keep track of architectural decisions in a structured format using Architecture Decision Records (ADRs)" names the domain and one concrete action (tracking decisions as structured records), but stops short of the several specific actions (create, supersede, index) that anchor 4 requires.

3 / 5

Completeness

The 'what' is clear (structured tracking of architectural decisions as ADRs), but there is no 'when' clause at all — no "Use when..." or equivalent trigger guidance — which caps completeness at 3 per the judging guidelines.

3 / 5

Trigger Term Quality

"architectural decisions" and "Architecture Decision Records (ADRs)" are natural keywords users would say, but common variations like "design decisions", "decision log", or "decision record" are missing, matching the 'some relevant keywords but missing variations' anchor.

3 / 5

Distinctiveness Conflict Risk

ADRs are a distinct, well-known practice niche with specific triggers, so conflict risk is low; only minor overlap with general documentation/note-taking skills keeps it below 5.

4 / 5

Total

13

/

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.

Validation — 15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

relative_links

Relative link issues: 1 missing

Warning

Total

15

/

16

Passed

Repository

chattocorp/chatto

Path

.agents/skills/adr/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.