architecture
Architectural decision-making framework. Requirements analysis, trade-off evaluation, ADR documentation. Use when making architecture decisions or analyzing system design.
79
Quality
70%
Does it follow best practices?
Impact
98%
1.18xAverage score across 3 eval scenarios
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./skills/architecture/SKILL.mdQuality
Discovery
67%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 has good structure with an explicit 'Use when' clause that clearly communicates both purpose and trigger conditions. However, the capabilities listed are somewhat abstract (e.g., 'trade-off evaluation') rather than concrete actions, and the trigger terms could be expanded to capture more natural user language around architecture decisions.
Suggestions
Add more specific concrete actions like 'create ADR documents', 'compare technology options', 'document architectural rationale'
Expand trigger terms to include natural variations like 'tech stack choice', 'scalability decisions', 'microservices', 'design trade-offs', or 'technology comparison'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (architectural decision-making) and lists some actions (requirements analysis, trade-off evaluation, ADR documentation), but these are somewhat abstract rather than concrete specific actions like 'create ADR files' or 'compare technology options'. | 2 / 3 |
Completeness | Clearly answers both what (architectural decision-making framework with requirements analysis, trade-off evaluation, ADR documentation) and when (making architecture decisions or analyzing system design) with an explicit 'Use when' clause. | 3 / 3 |
Trigger Term Quality | Includes relevant terms like 'architecture decisions' and 'system design', but misses common variations users might say such as 'tech stack', 'design patterns', 'scalability', 'microservices vs monolith', or 'technology choice'. | 2 / 3 |
Distinctiveness Conflict Risk | 'System design' is fairly broad and could overlap with skills for database design, API design, or general software engineering. The ADR focus helps distinguish it, but 'architecture decisions' could conflict with infrastructure or deployment skills. | 2 / 3 |
Total | 9 / 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 being a concise navigation hub with excellent progressive disclosure through its content map table. However, it functions more as an index than an actionable skill - the actual guidance for making architecture decisions is entirely delegated to referenced files without demonstrating any concrete workflow or examples in the main file itself.
Suggestions
Add a brief concrete example workflow showing how to apply the framework (e.g., 'For a new feature: 1. Read context-discovery.md → 2. Classify project → 3. Document in ADR using trade-off-analysis.md')
Include at least one inline example of a quick decision or ADR snippet to make the skill immediately actionable without requiring file reads
| 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 without padding or explaining concepts Claude already knows. | 3 / 3 |
Actionability | Provides a clear checklist and file navigation structure, but lacks concrete executable examples or specific commands. The actual actionable content is deferred to referenced files rather than demonstrated inline. | 2 / 3 |
Workflow Clarity | The validation checklist provides a sequence of considerations, but lacks explicit step-by-step workflow with validation checkpoints. The process of 'how' to do architecture decisions is delegated to external files without a clear orchestrating workflow. | 2 / 3 |
Progressive Disclosure | Excellent use of a content map table with clear 'When to Read' guidance. References are one level deep, well-signaled, and organized for easy navigation 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 | |
- Repository
- sickn33/antigravity-awesome-skills
- Commit
9c177eb
- 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.