CtrlK
BlogDocsLog inGet started
Tessl Logo

architecture-decision-records

Capture architectural decisions made during Claude Code sessions as structured ADRs. Auto-detects decision moments, records context, alternatives considered, and rationale. Maintains an ADR log so future developers understand why the codebase is shaped the way it is.

64

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

The canonical home for this skill is tdg-personal/architecture-decision-records

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 body is a well-structured, actionable instruction skill with a concrete template, clear multi-step workflow, and explicit validation checkpoints; only progressive disclosure and minor conciseness tweaks remain.

DimensionReasoningScore

Conciseness

Efficient and focused on what Claude doesn't already know (the adapted ADR template, workflow, lifecycle); only minor sections such as the categories table and Do/Don't lists could be trimmed.

4 / 5

Actionability

Provides a copy-paste-ready ADR template, concrete directory structure, index format, specific file paths (docs/adr/NNNN-decision-title.md), and exact fallback responses — fully actionable guidance.

5 / 5

Workflow Clarity

The capture workflow is a clearly sequenced eight-step process with explicit consent validation before writing ('Only write... after explicit approval. If the user declines, discard the draft') and a feedback loop, satisfying the validation requirement for file-writing operations.

5 / 5

Progressive Disclosure

Well-organized with clear section headers and a single self-contained file (no nested references), though at ~180 lines some material (full ADR template, categories table) could optionally be split into a reference file.

4 / 5

Total

18

/

20

Passed

Description

67%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 is specific and occupies a distinct niche, but it omits any explicit 'Use when...' trigger guidance, which caps completeness and weakens trigger-term quality.

Suggestions

Append an explicit 'Use when...' clause with natural user phrases such as 'Use when the user says let's record this decision, ADR this, or asks why we chose X over Y.'

Add common synonyms and file/term variations users would actually say (e.g. 'decision log', 'architecture decision record', 'ADR').

Surface a couple of natural trigger phrases directly in the description so the skill is discoverable from user speech rather than only from domain terms.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — 'Capture architectural decisions', 'Auto-detects decision moments', 'records context, alternatives considered, and rationale', 'Maintains an ADR log' — giving comprehensive coverage of what the skill does.

5 / 5

Completeness

Has a clear 'what' but no explicit 'Use when...' clause or equivalent trigger guidance, so per the judging guidelines completeness is capped at 3 even though the capability description is strong.

3 / 5

Trigger Term Quality

Contains relevant domain keywords ('architectural decisions', 'ADR', 'alternatives', 'rationale') but lacks the natural user-spoken trigger phrases (e.g. 'let's record this decision', 'ADR this') and common synonyms that appear in the body.

3 / 5

Distinctiveness Conflict Risk

Occupies a clear niche (structured ADRs) with distinct triggers and minimal overlap risk against other skills.

5 / 5

Total

16

/

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.

Validation14 / 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
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.