adr-generator
Install with Tessl CLI
npx tessl i github:jeremylongshore/claude-code-plugins-plus-skills --skill adr-generatorAdr Generator - Auto-activating skill for Technical Documentation. Triggers on: adr generator, adr generator Part of the Technical Documentation skill category.
Overall
score
19%
Does it follow best practices?
Validation for skill structure
Activation
7%This description is severely underdeveloped, essentially serving as a placeholder rather than a functional skill description. It relies entirely on the skill name without explaining what ADR generation entails or providing meaningful trigger guidance. The repeated trigger term and generic category label provide almost no value for skill selection.
Suggestions
Add specific actions the skill performs, e.g., 'Creates Architecture Decision Records (ADRs) documenting technical choices, generates ADR templates with status/context/decision/consequences sections, maintains ADR numbering and indexing.'
Include a 'Use when...' clause with natural trigger terms: 'Use when the user asks about documenting architecture decisions, creating ADRs, recording technical choices, or needs templates for design decision documentation.'
Add common variations and file references users might mention: 'architecture decision record', 'design decision', 'technical decision log', 'ADR template', 'docs/adr/', '.md decision files'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description only mentions 'Technical Documentation' as a category and 'adr generator' as a trigger, but provides no concrete actions. It doesn't explain what ADR generation actually involves (e.g., creating architecture decision records, documenting design choices, generating templates). | 1 / 3 |
Completeness | The description fails to answer 'what does this do' beyond the name itself, and the 'when' guidance is just a repeated trigger phrase with no explicit use-case scenarios or context for when Claude should select this skill. | 1 / 3 |
Trigger Term Quality | The only trigger terms listed are 'adr generator' repeated twice. Missing natural variations users would say like 'architecture decision record', 'design decision', 'ADR template', 'document architecture choice', or 'technical decision'. | 1 / 3 |
Distinctiveness Conflict Risk | While 'ADR' is a specific technical concept that provides some distinctiveness, the vague 'Technical Documentation' category could overlap with other documentation skills. The lack of specific actions makes it harder to distinguish from general documentation tools. | 2 / 3 |
Total | 5 / 12 Passed |
Implementation
0%This skill is essentially a placeholder with no actionable content. It describes what an ADR generator skill should do but provides zero actual guidance on ADR structure, format, templates, or generation process. The content would be completely useless for Claude attempting to help a user create Architecture Decision Records.
Suggestions
Add a concrete ADR template with sections (Title, Status, Context, Decision, Consequences) and example content for each
Include executable code or commands for generating ADR files with proper naming conventions (e.g., 'NNNN-title-with-dashes.md')
Provide at least one complete example ADR showing the expected output format
Add a clear workflow: 1) Determine next ADR number, 2) Create file with template, 3) Fill sections based on user input, 4) Validate required sections are complete
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is padded with generic boilerplate that explains nothing specific about ADR generation. Phrases like 'provides automated assistance' and 'follows industry best practices' are filler that Claude doesn't need. | 1 / 3 |
Actionability | No concrete guidance whatsoever - no code, no commands, no ADR format examples, no actual instructions on how to generate an ADR. The content only describes what the skill claims to do without showing how. | 1 / 3 |
Workflow Clarity | No workflow is defined. There are no steps for creating an ADR, no template structure, no validation criteria. The skill claims to provide 'step-by-step guidance' but contains none. | 1 / 3 |
Progressive Disclosure | The content is a monolithic block of vague marketing-style text with no structure for actual use. No references to templates, examples, or detailed documentation are provided. | 1 / 3 |
Total | 4 / 12 Passed |
Validation
69%Validation — 11 / 16 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
description_trigger_hint | Description may be missing an explicit 'when to use' trigger hint (e.g., 'Use when...') | Warning |
allowed_tools_field | 'allowed-tools' contains unusual tool name(s) | Warning |
metadata_version | 'metadata' field is not a dictionary | Warning |
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
body_steps | No step-by-step structure detected (no ordered list); consider adding a simple workflow | Warning |
Total | 11 / 16 Passed | |
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.