microservices-patterns
Design microservices architectures with service boundaries, event-driven communication, and resilience patterns. Use when building distributed systems, decomposing monoliths, or implementing microservices.
85
78%
Does it follow best practices?
Impact
96%
1.14xAverage score across 3 eval scenarios
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./plugins/microservices-patterns/skills/microservices-patterns/SKILL.mdQuality
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 a well-crafted skill description that follows best practices. It uses third person voice, lists specific architectural concepts and patterns, includes a clear 'Use when...' clause with natural trigger terms, and carves out a distinct niche in the microservices/distributed systems domain.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'Design microservices architectures', 'service boundaries', 'event-driven communication', and 'resilience patterns'. These are concrete architectural concepts and activities. | 3 / 3 |
Completeness | Clearly answers both what ('Design microservices architectures with service boundaries, event-driven communication, and resilience patterns') and when ('Use when building distributed systems, decomposing monoliths, or implementing microservices') with explicit trigger guidance. | 3 / 3 |
Trigger Term Quality | Includes natural keywords users would say: 'microservices', 'distributed systems', 'decomposing monoliths', 'service boundaries', 'event-driven'. These cover common variations of how users discuss microservices architecture. | 3 / 3 |
Distinctiveness Conflict Risk | Clear niche focused specifically on microservices architecture with distinct triggers like 'decomposing monoliths', 'service boundaries', and 'resilience patterns'. Unlikely to conflict with general coding or other architecture skills. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
57%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill provides excellent, executable code examples for microservices patterns with good coverage of key concepts. However, it's overly verbose with explanatory content Claude doesn't need, lacks clear decision-making workflows, and presents everything in one large file rather than using progressive disclosure to organize the substantial content.
Suggestions
Split into multiple files: SKILL.md as overview with links to COMMUNICATION.md, RESILIENCE.md, SAGA.md for detailed implementations
Remove explanatory definitions (e.g., 'REST APIs', 'gRPC', 'GraphQL' bullets) and 'When to Use' section that duplicates the skill description
Add a decision workflow: 'When decomposing, first identify bounded contexts → validate with team → implement one service → verify communication before proceeding'
Add validation checkpoints for saga implementations (e.g., 'Test compensation logic by simulating failures at each step before production')
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill contains useful patterns but includes explanatory content Claude already knows (e.g., explaining what REST, gRPC, GraphQL are; defining basic concepts like 'Each service owns its data'). The 'When to Use This Skill' section is largely redundant with the description. | 2 / 3 |
Actionability | Provides fully executable Python code examples for each major pattern including service decomposition, API gateway, event-driven communication, saga pattern, and circuit breaker. Code is copy-paste ready with realistic implementations. | 3 / 3 |
Workflow Clarity | While individual patterns are well-explained, there's no clear workflow for how to approach microservices design decisions. The saga pattern shows compensation logic, but there's no validation checkpoint guidance for when to use which pattern or how to verify implementations work correctly. | 2 / 3 |
Progressive Disclosure | This is a monolithic 300+ line document with no references to external files for detailed content. API gateway, saga patterns, and resilience patterns could each be separate files. No navigation structure or links to deeper documentation. | 1 / 3 |
Total | 8 / 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
- secondsky/claude-skills
- Commit
90d6bd7
- 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.