architecture
Architectural decision-making framework.
48
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, consisting of only four words that provide no actionable information. It fails to specify concrete capabilities, lacks natural trigger terms users would say, omits any 'when to use' guidance, and is too generic to distinguish from other architecture-related skills.
Suggestions
Add specific concrete actions the skill performs, e.g., 'Creates Architecture Decision Records (ADRs), documents technical tradeoffs, evaluates design alternatives'
Include a 'Use when...' clause with natural trigger terms like 'ADR', 'architecture decision', 'design decision', 'technical tradeoff', 'document why we chose'
Specify the distinct scope to avoid conflicts, e.g., 'for software architecture decisions' or 'for documenting system design choices in ADR format'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description uses abstract language ('framework') without listing any concrete actions. It does not specify what the skill actually does - no verbs describing capabilities like 'documents decisions', 'evaluates tradeoffs', or 'generates ADRs'. | 1 / 3 |
Completeness | Missing both 'what' and 'when'. The description doesn't explain what actions the skill performs, nor does it include any 'Use when...' clause or trigger guidance for when Claude should select this skill. | 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', 'architecture decision record', 'design decision', 'technical decision', or 'tradeoff analysis'. | 1 / 3 |
Distinctiveness Conflict Risk | Very generic phrasing could overlap with any architecture-related skill, design pattern skill, or general decision-making tool. 'Framework' is too vague to distinguish this from other architectural or planning skills. | 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 skill excels at organization and token efficiency, serving as a clean entry point to a larger architecture decision framework. However, it functions primarily as an index/overview rather than providing directly actionable guidance—the actual decision-making content lives in referenced files. The validation checklist is helpful but would benefit from explicit sequencing.
Suggestions
Add a brief numbered workflow showing the typical architecture decision process (e.g., 1. Discover context → 2. Analyze trade-offs → 3. Select patterns → 4. Document in ADR)
Include one concrete, minimal example of an ADR or trade-off analysis directly in this file to make it immediately actionable
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Lean and efficient with a clear content map, minimal prose, and no unnecessary explanations. Every section serves a purpose and assumes Claude's competence with architectural concepts. | 3 / 3 |
Actionability | Provides a validation checklist and clear file references, but lacks concrete executable examples or specific commands. The guidance is structural rather than directly actionable—actual implementation details are deferred to referenced files. | 2 / 3 |
Workflow Clarity | The validation checklist implies a sequence, but there's no explicit workflow with numbered steps or feedback loops. The 'When to Read' column helps with navigation but doesn't constitute a clear multi-step process with validation checkpoints. | 2 / 3 |
Progressive Disclosure | Excellent structure with a clear content map, one-level-deep references to supporting files, and well-signaled navigation. The table format makes it easy to find relevant content without reading everything. | 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 | |
- Repository
- Dokhacgiakhoa/antigravity-ide
- Commit
332e58b
- 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.