CtrlK
BlogDocsLog inGet started
Tessl Logo

architecture-decision-records

Comprehensive patterns for creating, maintaining, and managing Architecture Decision Records (ADRs) that capture the context and rationale behind significant technical decisions.

34

Quality

30%

Does it follow best practices?

Impact

No eval scenarios have been run

SecuritybySnyk

Passed

No known issues

Optimize this skill with Tessl

npx tessl skill review --optimize ./plugins/antigravity-awesome-skills-claude/skills/architecture-decision-records/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

27%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

This skill reads more like a comprehensive ADR handbook than a focused skill for Claude. It is extremely verbose, explaining concepts Claude already understands and providing five full-length template examples inline rather than referencing external files. While the templates themselves are well-crafted and the adr-tools commands are actionable, the sheer volume of content undermines usability, and the workflow for Claude to actually follow when creating an ADR is buried under reference material.

Suggestions

Reduce to one primary template inline (e.g., Standard MADR) and move the other four templates to separate referenced files (e.g., templates/lightweight.md, templates/y-statement.md).

Remove the 'Core Concepts' section entirely—Claude already knows what ADRs are, their lifecycle, and when to write them.

Restructure the Instructions section into a clear, numbered workflow with explicit decision points (e.g., 'Determine template based on decision complexity', 'Verify all required sections are populated before submitting').

Move the Review Checklist, Best Practices, and ADR Management sections into a separate MANAGEMENT.md reference file, keeping only a brief summary with links in the main skill.

DimensionReasoningScore

Conciseness

Extremely verbose at ~350+ lines. Explains basic concepts Claude already knows (what an ADR is, when to write one, lifecycle states). Five full template examples with extensive prose content that could be replaced by a single template with brief annotations. The 'Core Concepts' section is entirely unnecessary for Claude.

1 / 3

Actionability

Provides concrete templates and examples that are copy-paste ready, plus real CLI commands for adr-tools. However, the skill is more of a reference document than actionable instructions—it doesn't clearly tell Claude what to DO when asked to create an ADR (e.g., which template to pick, how to determine the next number, where to place the file).

2 / 3

Workflow Clarity

The Instructions section lists 4 high-level steps but lacks specificity on sequencing and validation. The review checklist provides checkpoints but isn't integrated into the workflow. There's no feedback loop for validating the ADR content (e.g., check that all sections are filled, verify linked ADRs exist). The 'Creating a New ADR' steps in the index section are clearer but buried deep in the document.

2 / 3

Progressive Disclosure

Monolithic wall of content with no references to external files despite having five full templates that should be separate files. Everything is inline—templates, examples, management guidelines, review checklists, best practices—making it extremely long. No bundle files exist to offload content to, and the skill doesn't attempt any structural separation.

1 / 3

Total

6

/

12

Passed

Description

32%

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 identifies a clear domain (ADRs) but relies on generic verbs and lacks explicit trigger guidance ('Use when...'). It would benefit from listing specific concrete actions and including natural trigger terms that users would say when they need help with architecture decision records.

Suggestions

Add an explicit 'Use when...' clause, e.g., 'Use when the user asks to create, update, or review an ADR, document an architecture decision, or manage a decision log.'

List more specific concrete actions such as 'generate ADR templates from a standard format, update ADR statuses (proposed/accepted/deprecated), link related decisions, and ensure consistent markdown structure.'

Include additional natural trigger terms users might say: 'decision log', 'ADR template', 'document architecture decision', 'adr-tools', 'record technical decision'.

DimensionReasoningScore

Specificity

Names the domain (Architecture Decision Records/ADRs) and some actions ('creating, maintaining, and managing'), but these are fairly generic verbs. It doesn't list specific concrete actions like 'generate ADR templates, update status fields, link related decisions, format markdown files.'

2 / 3

Completeness

It describes what the skill does (patterns for creating/maintaining ADRs) but completely lacks a 'Use when...' clause or any explicit trigger guidance for when Claude should select this skill. Per the rubric, a missing 'Use when...' clause caps completeness at 2, and the 'what' portion is also somewhat vague, placing this at 1.

1 / 3

Trigger Term Quality

Includes 'Architecture Decision Records', 'ADRs', and 'technical decisions' which are relevant keywords. However, it misses common variations users might say like 'ADR template', 'document architecture decision', 'decision log', 'tech decision record', or 'adr-tools'.

2 / 3

Distinctiveness Conflict Risk

ADRs are a fairly specific niche which helps distinctiveness, but the phrase 'significant technical decisions' is broad enough to potentially overlap with general documentation or software architecture skills. The lack of explicit triggers increases conflict risk.

2 / 3

Total

7

/

12

Passed

Validation

90%

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

Validation10 / 11 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

10

/

11

Passed

Repository
sickn33/antigravity-awesome-skills
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.