CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

architecture-decision-records

Capture architectural decisions as numbered ADR markdown files in docs/adr/ with context, alternatives considered, consequences, and an index README. Use when the user says 'record this decision' or 'ADR this', chooses between frameworks or databases, discusses trade-offs, or asks why the codebase is shaped this way.

Quality

92%

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

88%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 content is highly actionable and the workflows are exemplary in their consent and approval checkpoints, with a complete template and index format making execution unambiguous. The main costs are duplicated trigger content across two sections and the absence of any reference-file offloading in a >150-line skill.

Suggestions

Merge "When to Activate" and "Decision Detection Signals" into a single section — both enumerate the same conversation triggers, so the second is largely redundant tokens.

Move the full ADR template and index format example into references/ files (e.g., references/template.md) to slim the main SKILL.md, since the skill already demonstrates this pattern by seeding a template.md in the target repo.

Drop or generalize "Integration with Other Skills", which references planner and code-reviewer agents that may not exist in the user's environment.

DimensionReasoningScore

Conciseness

The body is mostly operational with no explanation of concepts Claude already knows, but "When to Activate" and "Decision Detection Signals" substantially duplicate each other's trigger lists, and "ADR Lifecycle" restates the status enum already embedded in the template — minor trimming opportunities characteristic of anchor 4.

4 / 5

Actionability

Everything needed to execute is concrete: a complete ADR markdown template, the directory structure, a filled-in index table example, exact file paths ("docs/adr/NNNN-decision-title.md"), and verbatim fallback responses — copy-paste-ready guidance appropriate for an instruction-only skill.

5 / 5

Workflow Clarity

Both workflows are clearly sequenced with explicit checkpoints: consent before creating the directory, draft review with "Only write... after explicit approval", a decline path, numbering by scanning existing ADRs, and scripted fallbacks when no ADRs or no match is found. Writes are consent-gated and non-batch, so the destructive/batch validation cap does not apply.

5 / 5

Progressive Disclosure

The single file is well-sectioned and easy to navigate, but at ~170 lines with the full ADR template, index format, and categories table all inline and no references/ offloading, it sits between anchor 4 (good structure, minor placement gaps) and the split-file ideal of anchor 5.

4 / 5

Total

18

/

20

Passed

Description

95%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 that clearly and concisely states both what the skill produces (numbered ADR files in docs/adr/ with a defined structure) and when to invoke it, using natural user phrasings in third person. The only minor gap is that reading existing ADRs is implied rather than stated as a capability.

DimensionReasoningScore

Specificity

"Capture architectural decisions as numbered ADR markdown files in docs/adr/ with context, alternatives considered, consequences, and an index README" names the domain, artifact, location, and complete structure, but the reading/retrieval capability (a major function per the skill body) is only implied by "asks why the codebase is shaped this way", leaving a minor coverage gap between anchors 4 and 5.

4 / 5

Completeness

Both questions are answered explicitly: sentence one states what is produced and where, and sentence two gives a concrete "Use when..." clause with multiple specific trigger phrases, in third-person voice, matching the anchor-5 example structure exactly.

5 / 5

Trigger Term Quality

Natural user phrasings are covered comprehensively — "record this decision", "ADR this", "chooses between frameworks or databases", "discusses trade-offs", "why the codebase is shaped this way" — matching the anchor-5 example's breadth including the domain-specific term.

5 / 5

Distinctiveness Conflict Risk

The ADR niche has dedicated, unlikely-to-collide triggers ("ADR this", "record this decision", "why did we choose X") that don't overlap meaningfully with generic documentation or note-taking skills.

5 / 5

Total

19

/

20

Passed

Validation

87%

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

Validation — 14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

metadata_version

'metadata.version' is missing

Warning

relative_links

Relative link issues: 3 missing

Warning

Total

14

/

16

Passed

Repository

affaan-m/ECC

Path

skills/architecture-decision-records/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.