microservices-architect
Designs distributed system architectures, decomposes monoliths into bounded-context services, recommends communication patterns, and produces service boundary diagrams and resilience strategies. Use when designing distributed systems, decomposing monoliths, or implementing microservices patterns — including service boundaries, DDD, saga patterns, event sourcing, CQRS, service mesh, or distributed tracing.
91
92%
Does it follow best practices?
Impact
89%
1.08xAverage score across 6 eval scenarios
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 clearly articulates specific capabilities, provides comprehensive trigger terms covering the distributed systems domain, and includes an explicit 'Use when...' clause. It uses proper third-person voice throughout and would be easily distinguishable from other skills in a large skill library.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'designs distributed system architectures', 'decomposes monoliths into bounded-context services', 'recommends communication patterns', 'produces service boundary diagrams and resilience strategies'. These are all concrete, well-defined capabilities. | 3 / 3 |
Completeness | Clearly answers both 'what' (designs architectures, decomposes monoliths, recommends patterns, produces diagrams) and 'when' with an explicit 'Use when...' clause listing specific trigger scenarios and patterns. | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural terms users would say: 'distributed systems', 'monoliths', 'microservices', 'service boundaries', 'DDD', 'saga patterns', 'event sourcing', 'CQRS', 'service mesh', 'distributed tracing'. These are all terms a developer would naturally use when seeking help in this domain. | 3 / 3 |
Distinctiveness Conflict Risk | Occupies a clear niche around distributed systems and microservices architecture. The specific domain terms like 'saga patterns', 'CQRS', 'event sourcing', 'service mesh' make it highly distinguishable from general software architecture or coding 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 microservices architecture skill with excellent workflow clarity, strong executable examples across multiple languages, and good progressive disclosure via the reference table. Its main weakness is moderate verbosity — the Knowledge Reference keyword dump and some redundancy between the workflow validation checkpoints and the MUST DO/MUST NOT DO constraints could be trimmed to save tokens.
Suggestions
Remove the 'Knowledge Reference' keyword list at the bottom — it provides no actionable guidance and Claude already knows these concepts.
Consolidate the MUST DO/MUST NOT DO constraints with the workflow validation checkpoints to eliminate redundancy and save tokens.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is mostly efficient but includes some unnecessary content. The 'Knowledge Reference' section at the bottom is just a keyword list that adds no actionable value. The MUST DO/MUST NOT DO lists partially restate what's already in the workflow. The constraints section could be tighter. | 2 / 3 |
Actionability | The skill provides fully executable code examples across multiple languages (Node.js, Python, TypeScript) and Kubernetes YAML. The circuit breaker, saga orchestration, correlation ID middleware, and health probe examples are all copy-paste ready with concrete libraries and configurations. | 3 / 3 |
Workflow Clarity | The 6-step core workflow is clearly sequenced with explicit validation checkpoints at each stage. Each checkpoint defines specific, measurable criteria (e.g., 'no shared database schema exists between services'). The saga example includes a built-in compensation/rollback pattern for error recovery. | 3 / 3 |
Progressive Disclosure | The reference guide table clearly signals when to load each detailed reference file, with specific trigger conditions ('Load When' column). References are one level deep and well-organized by topic. The main skill provides a concise overview with actionable examples while deferring deep dives to reference files. | 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.