microservices-patterns
Design microservices architectures with service boundaries, event-driven communication, and resilience patterns. Use when building distributed systems, decomposing monoliths, or implementing microservices.
Install with Tessl CLI
npx tessl i github:secondsky/claude-skills --skill microservices-patterns83
Does it follow best practices?
If you maintain this skill, you can automatically optimize it using the tessl CLI to improve its score:
npx tessl skill review --optimize ./path/to/skillValidation for skill structure
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 capabilities, includes a clear 'Use when...' clause with natural trigger terms, and carves out a distinct niche in microservices architecture that won't easily conflict with other skills.
| 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', 'distributed systems', and 'microservices'. 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.
The skill provides excellent, executable code examples for microservices patterns with strong actionability. However, it suffers from being a monolithic document that mixes high-level concepts Claude already knows with detailed implementations that should be in separate files. The lack of a clear decision workflow for when to apply each pattern limits its practical utility.
Suggestions
Remove the 'Core Concepts' section entirely - it restates information Claude knows and is redundant with the detailed patterns that follow
Split into multiple files: keep a concise overview in SKILL.md with links to COMMUNICATION_PATTERNS.md, RESILIENCE_PATTERNS.md, SAGA_PATTERN.md, etc.
Add a decision workflow: 'When decomposing a monolith: 1. Identify bounded contexts 2. Validate service boundaries with [criteria] 3. Choose communication pattern based on [decision tree]'
Add validation checkpoints for the decomposition process (e.g., 'Before extracting a service, verify: independent deployability, clear API contract, no shared database dependencies')
| 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 'Core Concepts' section is largely redundant given the detailed patterns that follow. | 2 / 3 |
Actionability | Provides fully executable Python code examples for all major patterns 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 when to apply which pattern or how to sequence a microservices migration. The saga pattern shows compensation logic, but there's no validation checkpoint guidance for the overall decomposition process. | 2 / 3 |
Progressive Disclosure | This is a monolithic 300+ line document with no references to external files. Content like the full saga implementation, circuit breaker code, and communication patterns could be split into separate reference files with a concise overview in the main skill. | 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.
- 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.