adr-generator
Adr Generator - Auto-activating skill for Technical Documentation. Triggers on: adr generator, adr generator Part of the Technical Documentation skill category.
34
0%
Does it follow best practices?
Impact
100%
1.02xAverage score across 3 eval scenarios
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./planned-skills/generated/17-technical-docs/adr-generator/SKILL.mdQuality
Discovery
0%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This description is essentially a placeholder with no substantive content. It fails to explain what an ADR is, what the skill generates, or when it should be triggered. It would be nearly impossible for Claude to correctly select this skill from a pool of other documentation-related skills.
Suggestions
Add concrete actions such as 'Generates Architecture Decision Records (ADRs) documenting technical decisions, including context, decision rationale, status, and consequences in a standardized markdown format.'
Add an explicit 'Use when...' clause with natural trigger terms like 'Use when the user asks to create an ADR, document an architecture decision, record a technical decision, or mentions architecture decision records.'
Include common keyword variations users might say: 'ADR', 'architecture decision record', 'technical decision', 'decision log', 'design decision documentation'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description provides no concrete actions. It only states 'Auto-activating skill for Technical Documentation' without describing what it actually does—no mention of creating, formatting, reviewing, or managing ADRs. | 1 / 3 |
Completeness | Neither 'what does this do' nor 'when should Claude use it' is meaningfully answered. There is no explicit 'Use when...' clause and no description of capabilities beyond the category label 'Technical Documentation'. | 1 / 3 |
Trigger Term Quality | The only trigger terms listed are 'adr generator' repeated twice. It misses natural user phrases like 'architecture decision record', 'ADR', 'document architecture decisions', 'decision log', or 'technical decision'. | 1 / 3 |
Distinctiveness Conflict Risk | The phrase 'Technical Documentation' is extremely broad and would overlap with any documentation-related skill. The term 'adr generator' is somewhat specific but the description provides no context to distinguish it from other documentation skills. | 1 / 3 |
Total | 4 / 12 Passed |
Implementation
0%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill is an empty placeholder that provides no actual value. It contains no ADR template, no concrete instructions for generating Architecture Decision Records, no examples of ADR format, and no executable guidance whatsoever. The entire content is generic boilerplate that could apply to any skill topic by swapping the name.
Suggestions
Add a concrete ADR template with sections (Title, Status, Context, Decision, Consequences) and an example of a completed ADR
Provide executable commands or a step-by-step workflow for creating an ADR, such as file naming conventions (e.g., `NNNN-title.md`), directory structure, and how to number/sequence ADRs
Include at least one complete, copy-paste-ready ADR example showing proper format and content
Remove all generic boilerplate sections (When to Use, Capabilities, Example Triggers) and replace with actionable content about ADR generation patterns and best practices
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is entirely filler with no substantive information. It explains what the skill does in abstract terms without providing any actual guidance, commands, or examples for ADR generation. Every section restates the same vague concept. | 1 / 3 |
Actionability | There is zero concrete, executable guidance. No ADR template, no commands, no code, no specific format or structure is provided. The content only describes what the skill theoretically does without instructing how to do anything. | 1 / 3 |
Workflow Clarity | No workflow is defined at all. There are no steps, no sequence, no validation checkpoints. The bullet point 'Provides step-by-step guidance' is ironic given that no actual steps are present. | 1 / 3 |
Progressive Disclosure | The content is a flat, repetitive structure with no references to external files, no layered organization, and no meaningful sections. The headings exist but contain only boilerplate text with no real content to organize. | 1 / 3 |
Total | 4 / 12 Passed |
Validation
81%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 9 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
allowed_tools_field | 'allowed-tools' contains unusual tool name(s) | Warning |
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 9 / 11 Passed | |
- Commit
4dee593
- 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.