CtrlK
BlogDocsLog inGet started
Tessl Logo

adr

Record an architecture decision as an ADR in docs/adr/. Use when choosing between frameworks, libraries, databases, or architectural patterns; stating a decision with reasoning ("we decided X instead of Y because..."); or querying past decisions ("why did we choose X?").

76

Quality

96%

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

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.

A tight, actionable instruction skill: concrete template, commands, and two sequenced workflows with a review checkpoint. The only gap is a missing explicit verification step after the file write and index update in the recording workflow.

Suggestions

Add a final validation step to the recording workflow (e.g., re-read the written ADR and the updated README index to confirm the new row and file paths are correct).

Specify how to handle a missing docs/adr/README.md when recording (the query workflow addresses it, but the recording workflow assumes the directory and index already exist).

Clarify the glob pattern interaction: "Glob docs/adr/[0-9]*.md" matches the numeric files, but the documented filename is "NNNN-kebab-title.md" — confirm the pattern reliably picks up titled files.

DimensionReasoningScore

Conciseness

The body is lean and well-organized with no padding or explanations of concepts Claude already knows; every section (when-to-record, template, workflows, quality standards) earns its tokens.

5 / 5

Actionability

Provides a full copy-paste-ready ADR template, concrete commands ("Glob docs/adr/[0-9]*.md"), exact filename conventions ("NNNN-kebab-title.md"), and the index row format to append.

5 / 5

Workflow Clarity

Two clearly sequenced numbered workflows with a present-draft-for-review checkpoint before writing, but the recording workflow lacks an explicit validate/verify step after writing the file and updating the index.

4 / 5

Progressive Disclosure

A single well-organized file under 50 lines with clear section headers and no nested references; the simple-skill exception applies and no bundle files exist to verify.

5 / 5

Total

19

/

20

Passed

Description

100%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 model description: it states the concrete capability, gives an explicit "Use when..." trigger clause with natural user phrasing and synonyms, and carves out a clearly distinct niche. Every dimension lands at the top anchor.

DimensionReasoningScore

Specificity

"Record an architecture decision as an ADR" plus recording, retrieving, and querying are multiple concrete actions with comprehensive coverage of the ADR lifecycle.

5 / 5

Completeness

Explicitly states what it does (record/retrieve an ADR in docs/adr/) and when to use it via a concrete "Use when..." clause with three distinct triggering scenarios.

5 / 5

Trigger Term Quality

Names natural trigger terms (frameworks, libraries, databases, architectural patterns) and quotes actual user phrasing ("we decided X instead of Y because...", "why did we choose X?"), covering synonyms and variations.

5 / 5

Distinctiveness Conflict Risk

The ADR-in-docs/adr/ niche with decision-vs-alternative and past-decision-query triggers is clearly distinct from other skills and unlikely to fire for the wrong skill.

5 / 5

Total

20

/

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.

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

allowed_tools_field

'allowed-tools' contains unusual tool name(s)

Warning

Total

15

/

16

Passed

Repository
linuxfoundation/crowd.dev
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.