architect-review
Master software architect specializing in modern architecture
33
0%
Does it follow best practices?
Impact
92%
1.09xAverage score across 3 eval scenarios
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./skills/antigravity-architect-review/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 essentially a title or role label rather than a functional skill description. It lacks any concrete actions, trigger terms, or usage guidance. It also uses an implied first-person persona ('Master software architect') rather than third-person action-oriented language, further reducing its utility for skill selection.
Suggestions
Replace the role label with specific actions the skill performs, e.g., 'Designs system architectures, evaluates trade-offs between microservices and monoliths, creates architecture diagrams, and reviews code structure for scalability.'
Add an explicit 'Use when...' clause with natural trigger terms, e.g., 'Use when the user asks about system design, microservices, design patterns, scalability, API architecture, or architectural decision records.'
Use third-person voice describing capabilities rather than a persona title, e.g., 'Provides architectural guidance for...' instead of 'Master software architect specializing in...'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description uses vague, abstract language ('Master software architect') with no concrete actions listed. It doesn't describe what the skill actually does—no verbs like 'designs', 'reviews', or 'creates'. | 1 / 3 |
Completeness | Neither 'what does this do' nor 'when should Claude use it' is answered. There is no 'Use when...' clause and no description of capabilities. | 1 / 3 |
Trigger Term Quality | 'Modern architecture' is overly generic and not a natural phrase users would say when seeking help. There are no specific keywords like 'microservices', 'system design', 'API design', 'design patterns', etc. | 1 / 3 |
Distinctiveness Conflict Risk | 'Software architect' and 'modern architecture' are extremely broad and could overlap with virtually any coding, design, or engineering skill. There is nothing to distinguish this from other development-related skills. | 1 / 3 |
Total | 4 / 12 Passed |
Implementation
0%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill is essentially a persona description and technology catalog rather than actionable guidance. It lists hundreds of architecture concepts, patterns, and technologies that Claude already knows, without providing any concrete templates, decision frameworks, code examples, or executable workflows. The content would be more effective as a concise 20-30 line skill with specific review checklists, ADR templates, and concrete evaluation criteria.
Suggestions
Replace the extensive 'Capabilities' bullet lists with a concise architecture review checklist or decision framework that provides concrete evaluation criteria (e.g., a scoring rubric for scalability, security, maintainability).
Add concrete, executable examples such as an ADR template, a C4 diagram template in code, or a specific architecture review output format with sections and expected content.
Define a clear multi-step review workflow with explicit validation checkpoints, e.g., 'Step 1: Identify bounded contexts → Step 2: Check for these specific anti-patterns → Step 3: Validate against these criteria → Step 4: Document findings in this format'.
Remove 'Behavioral Traits', 'Knowledge Base', and 'Expert Purpose' sections entirely — these describe what Claude already knows and add no actionable value.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Extremely verbose with extensive lists of technologies, patterns, and concepts that Claude already knows. The 'Capabilities' section is essentially a catalog of architecture buzzwords that adds no actionable value. 'Behavioral Traits' and 'Knowledge Base' sections describe personality attributes Claude doesn't need spelled out. The entire skill could be reduced to ~20% of its current size. | 1 / 3 |
Actionability | No concrete code, commands, templates, or executable examples anywhere. The 'Instructions' section has four vague steps like 'Gather system context' and 'Evaluate architecture decisions' with no specifics on how. The 'Example Interactions' are just prompt suggestions, not input/output examples. There's nothing copy-paste ready or directly usable. | 1 / 3 |
Workflow Clarity | The 4-step 'Instructions' workflow is extremely vague ('Gather system context, goals, and constraints' — how?). The 'Response Approach' lists 8 steps but they're abstract descriptions without validation checkpoints, decision criteria, or feedback loops. For a skill involving architectural review of complex systems, there's no guidance on what constitutes a valid review or how to verify recommendations. | 1 / 3 |
Progressive Disclosure | Monolithic wall of text with no references to external files. All content is inline in one massive document with 10+ sections of bullet-point lists. The extensive 'Capabilities' catalog could be split into reference files, but instead everything is dumped into a single file with no navigation structure or hierarchy. | 1 / 3 |
Total | 4 / 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
- boisenoise/skills-collections
- Commit
f1697b6
- 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.