architecture-designer
Use when designing new high-level system architecture, reviewing existing designs, or making architectural decisions. Invoke to create architecture diagrams, write Architecture Decision Records (ADRs), evaluate technology trade-offs, design component interactions, and plan for scalability. Use for system design, architecture review, microservices structuring, ADR authoring, scalability planning, and infrastructure pattern selection — distinct from code-level design patterns or database-only design tasks.
94
92%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Passed
No known issues
Quality
Discovery
100%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 is an excellent skill description that hits all the key criteria. It provides specific concrete actions, includes abundant natural trigger terms users would actually say, explicitly states both what the skill does and when to use it, and proactively distinguishes itself from potentially overlapping skills. The description uses proper third-person voice throughout.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'create architecture diagrams', 'write Architecture Decision Records (ADRs)', 'evaluate technology trade-offs', 'design component interactions', and 'plan for scalability'. | 3 / 3 |
Completeness | Clearly answers both what (create diagrams, write ADRs, evaluate trade-offs, design interactions, plan scalability) AND when ('Use when designing new high-level system architecture, reviewing existing designs, or making architectural decisions'), with explicit scope boundaries. | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural terms users would say: 'system architecture', 'architectural decisions', 'architecture diagrams', 'ADRs', 'system design', 'architecture review', 'microservices', 'scalability planning', 'infrastructure pattern'. | 3 / 3 |
Distinctiveness Conflict Risk | Explicitly distinguishes itself from related skills with the clause 'distinct from code-level design patterns or database-only design tasks', creating clear boundaries and reducing conflict risk with other design-related skills. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
85%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 architecture skill with strong actionability through concrete examples (Mermaid diagram, full ADR) and excellent progressive disclosure via the reference table. The workflow includes proper validation checkpoints. Minor inefficiency in the role definition section which adds persona backstory that doesn't enhance Claude's execution.
Suggestions
Remove or condense the 'Role Definition' section - Claude doesn't need persona backstory ('15+ years of experience') to execute the skill effectively
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Generally efficient but includes some unnecessary framing ('Senior software architect with 15+ years of experience') and the role definition section adds little value since Claude doesn't need persona backstory to execute the skill. | 2 / 3 |
Actionability | Provides concrete, executable guidance with a complete Mermaid diagram example, a full ADR template with realistic content, clear output templates, and specific constraints. The examples are copy-paste ready. | 3 / 3 |
Workflow Clarity | Clear 5-step workflow with explicit validation checkpoints ('Verify full requirements coverage before proceeding', 'If review fails, return to step 3 with recorded feedback'). The feedback loop for stakeholder review is well-defined. | 3 / 3 |
Progressive Disclosure | Excellent structure with a reference table clearly signaling when to load each detailed guide. Content is appropriately split between the overview skill and referenced materials, with one-level-deep navigation. | 3 / 3 |
Total | 11 / 12 Passed |
Validation
100%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 11 / 11 Passed
Validation for skill structure
No warnings or errors.
- Repository
- jeffallan/claude-skills
- Commit
5b76101
- 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.