Architectural decision-making framework.
54
Quality
36%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./.agent/skills/architecture/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 critically underdeveloped and would be nearly useless for skill selection. It provides no concrete actions, no trigger terms users would naturally use, and no guidance on when to apply the skill. Claude would struggle to distinguish this from any other planning or documentation skill.
Suggestions
Add specific actions the skill performs, e.g., 'Creates Architecture Decision Records (ADRs), documents technical trade-offs, tracks design rationale'
Include a 'Use when...' clause with natural trigger terms like 'ADR', 'architecture decision', 'design rationale', 'technical trade-off', 'why did we choose'
Specify the scope to reduce conflicts, e.g., 'for software architecture decisions' or 'for documenting system design choices'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description uses vague, abstract language ('framework') without listing any concrete actions. It doesn't specify what decisions, what architecture, or what the skill actually does. | 1 / 3 |
Completeness | Missing both 'what' (no specific actions described) and 'when' (no trigger guidance or use cases). The description provides almost no actionable information for skill selection. | 1 / 3 |
Trigger Term Quality | Contains only technical jargon ('architectural decision-making framework') that users are unlikely to naturally say. Missing common terms like 'ADR', 'design decisions', 'architecture docs', 'technical decisions'. | 1 / 3 |
Distinctiveness Conflict Risk | Extremely generic - 'architectural' and 'decision-making' could overlap with many skills involving design, planning, code structure, or documentation. No distinct triggers to differentiate it. | 1 / 3 |
Total | 4 / 12 Passed |
Implementation
72%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a well-structured overview skill that excels at progressive disclosure and conciseness. The content map and related skills sections provide excellent navigation. However, the main file could benefit from at least one concrete example or executable guidance rather than deferring all actionable content to referenced files.
Suggestions
Add a brief concrete example of an ADR format or decision tree directly in the main file to improve actionability
Include explicit workflow steps with validation checkpoints (e.g., 'After context discovery, validate requirements with stakeholders before proceeding to pattern selection')
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is lean and efficient, using tables for quick reference and avoiding unnecessary explanations. Every section serves a clear purpose with no padding or concepts Claude would already know. | 3 / 3 |
Actionability | Provides a clear file map and checklist, but lacks concrete executable examples in the main file. The actionable content is deferred to referenced files rather than demonstrated here. | 2 / 3 |
Workflow Clarity | The validation checklist provides a clear sequence, but lacks explicit validation checkpoints or feedback loops for error recovery. The workflow is implied through file references rather than explicitly sequenced. | 2 / 3 |
Progressive Disclosure | Excellent structure with a clear content map table, one-level-deep references to supporting files, and well-signaled navigation. The skill appropriately serves as an overview pointing to detailed materials. | 3 / 3 |
Total | 10 / 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.
Validation — 10 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 10 / 11 Passed | |
3395991
Table of Contents
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.