CtrlK
BlogDocsLog inGet started
Tessl Logo

architecture-decision

Document an architectural decision — record the decision and rationale, retain into Hindsight, and update CLAUDE.md if needed.

60

Quality

70%

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

Fix and improve this skill with Tessl

tessl review fix ./devflow-plugin/skills/architecture-decision/SKILL.md

The canonical home for this skill is architecture-decision in AndreJorgeLopes/devflow

SKILL.md
Quality
Evals
Security

Quality

Content

75%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.

The content is well-structured, actionable, and concise, with a complete ADR template and clear approval checkpoints. The main gap is the absence of an explicit error-recovery/validation feedback loop around the CLAUDE.md write.

Suggestions

Add a short validation/feedback step after the CLAUDE.md update (e.g. re-read the edited section to confirm the rule landed correctly) to strengthen the workflow's feedback loop.

Move the diagram-complexity rating guidance into a brief referenced note so the main flow stays leaner for purely textual decisions.

Show one minimal filled-in ADR example so the template's placeholders are unambiguous.

DimensionReasoningScore

Conciseness

The body is efficient: a compact diagram-complexity callout, a fill-in ADR template, and terse numbered steps with no padding or explanation of concepts Claude already knows.

4 / 5

Actionability

Provides a copy-paste-ready ADR template plus concrete tool usage (Hindsight retain with named fields, a relative-path markdown embed, Read-the-PNG step); minor gaps are placeholder fields the user must elaborate.

4 / 5

Workflow Clarity

Six well-sequenced steps with explicit approval checkpoints ('Present the ADR for review and approval', 'Only update CLAUDE.md if the user approves') and a confirmation step, though there is no error-recovery feedback loop.

4 / 5

Progressive Disclosure

Self-contained single SKILL.md with clear sections (Steps, Important, diagram callout) and one-level references to the render-diagram skill and Hindsight tool; no nested or buried references, though it slightly exceeds the simple-skill line count.

4 / 5

Total

16

/

20

Passed

Description

66%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.

The description conveys concrete actions and a clear niche, but omits any explicit 'Use when...' trigger guidance, which caps its completeness. Adding a trigger clause and common synonyms (ADR, design decision) would raise it.

Suggestions

Add an explicit trigger clause, e.g. 'Use when the user asks to record or document an architectural/design decision (ADR).'

Include synonyms like 'ADR', 'design decision', and 'decision record' to improve trigger term coverage.

Tighten the em-dash list into a single concrete action statement to reduce reliance on implied 'when'.

DimensionReasoningScore

Specificity

Lists several concrete actions — 'Document an architectural decision', 'record the decision and rationale', 'retain into Hindsight', 'update CLAUDE.md' — giving good coverage of the skill's capabilities.

4 / 5

Completeness

The 'what' is clear, but there is no explicit 'Use when...' trigger clause; per the rubric a missing explicit trigger caps completeness at 3 even though the when is weakly implied.

3 / 5

Trigger Term Quality

'architectural decision', 'rationale', 'Hindsight', and 'CLAUDE.md' are natural terms a user would say, but common synonyms like 'ADR', 'design decision', or 'decision record' are missing.

4 / 5

Distinctiveness Conflict Risk

'Architectural decision' recording tied to Hindsight retention and CLAUDE.md is a fairly distinct niche, with only minor overlap risk against general documentation skills.

4 / 5

Total

15

/

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

relative_links

Relative link issues: 1 missing

Warning

Total

15

/

16

Passed

Repository
AndreJorgeLopes/devflow
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.