architecture-decision-records

Write and maintain Architecture Decision Records (ADRs) following best practices for technical decision documentation. Use when documenting significant technical decisions, reviewing past architectural choices, or establishing decision processes.

Quality

88%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Quality

Content

77%

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 with concrete templates and commands and clear review/migration checklists, but it is a monolithic ~440-line document whose fully worked hypothetical examples and basic concept explanations could be tightened and offloaded into reference files.

Suggestions

Move the five full templates into separate files under references/ (e.g., templates/standard-madr.md) and signal them from a concise overview in SKILL.md to improve progressive disclosure and cut inline tokens.

Trim the filled-in hypothetical details in examples (user counts, team names, migration week ranges) to skeletal template skeletons, and drop or shorten the "What is an ADR?" Core Concepts section that re-explains knowledge Claude already has.

Tighten the high-level Instructions into a concrete sequenced workflow with explicit validation checkpoints (e.g., verify status field, confirm related-ADR links resolve) rather than four abstract verbs.

Dimension	Reasoning	Score
Conciseness	The body runs ~440 lines with five fully fleshed-out hypothetical templates (e.g., an e-commerce PostgreSQL example with 10,000 users, migration phases, team names) and a "Core Concepts" section re-explaining Context/Decision/Consequences that Claude already knows; useful but padded, not lean.	2 / 3
Actionability	Five copy-paste-ready markdown templates plus executable adr-tools commands ("brew install adr-tools", "adr init docs/adr", "adr new -s 3 ...") and a concrete directory structure give fully executable, specific guidance.	3 / 3
Workflow Clarity	The Review Process provides an explicit sequenced checklist (Before Submission / During Review / After Acceptance) and the deprecation template gives a phased migration plan, supplying clear checkpoints and feedback structure; the high-level 4-step Instructions are vaguer but the checklists carry the workflow.	3 / 3
Progressive Disclosure	No bundle files exist and everything is inline in one ~440-line SKILL.md; sections are well-organized, but the five templates and management guidance are content that could be split into separate reference files and no one-level-deep references are signaled, matching the "content that should be separate is inline" anchor.	2 / 3
	Total	10 / 12 Passed

Description

100%

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 well-crafted: third-person voice, concrete actions, explicit "Use when" triggers, and a clearly distinguishable ADR niche. It hits all four anchors at the top level with no fluff or over-claims.

Dimension	Reasoning	Score
Specificity	"Write and maintain Architecture Decision Records (ADRs)" names multiple concrete actions on a specific artifact, matching the anchor that lists specific concrete actions; the trailing "following best practices" clause is light fluff but does not undermine the concrete verbs.	3 / 3
Completeness	Clearly states what ("Write and maintain ADRs...") and an explicit "Use when..." clause with three trigger scenarios, satisfying both halves of the anchor.	3 / 3
Trigger Term Quality	Covers natural terms a user would say — "Architecture Decision Records (ADRs)", "documenting significant technical decisions", "reviewing past architectural choices" — giving good coverage rather than just technical jargon.	3 / 3
Distinctiveness Conflict Risk	ADRs are a distinct, well-scoped niche with trigger terms unlikely to fire for unrelated skills, matching the clear-niche anchor.	3 / 3
	Total	12 / 12 Passed

Validation

93%

Warnings & errors only

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

Criteria	Description	Result
relative_links	Relative link issues: 4 missing	Warning

	Total	15 / 16 Passed

Repository: rmyndharis/antigravity-skills
Path: skills/architecture-decision-records/SKILL.md
Commit: e63f7dd

Reviewed: about 5 hours ago

Table of Contents

Discovery Implementation Validation

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.