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:Dicklesworthstone/pi_agent_rust --skill microservices-patterns90
Quality
86%
Does it follow best practices?
Impact
98%
1.81xAverage score across 3 eval scenarios
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 an explicit '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 with service boundaries, event-driven communication, and resilience patterns' covers distinct architectural concerns. | 3 / 3 |
Completeness | Clearly answers both what (design microservices architectures with specific patterns) AND when (explicit 'Use when' clause covering building distributed systems, decomposing monoliths, or implementing microservices). | 3 / 3 |
Trigger Term Quality | Includes natural keywords users would say: 'microservices', 'distributed systems', 'decomposing monoliths', 'service boundaries', 'event-driven' - these are terms developers naturally use when discussing this domain. | 3 / 3 |
Distinctiveness Conflict Risk | Clear niche focused specifically on microservices architecture with distinct triggers like 'decomposing monoliths', 'service boundaries', and 'resilience patterns' that wouldn't overlap with general coding or other architecture skills. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
72%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a comprehensive microservices skill with excellent actionable code examples covering key patterns like Saga, Circuit Breaker, and Event-Driven communication. The main weaknesses are verbosity in the conceptual sections (explaining things Claude already knows) and missing validation/verification workflows for implementing these patterns in practice. The structure and progressive disclosure are well-executed.
Suggestions
Remove or significantly condense the 'Core Concepts' section - Claude already understands these fundamentals; jump directly to the actionable patterns
Add a validation workflow section: how to verify service boundaries are correct, test circuit breaker behavior, validate saga compensation logic works
Include a decision tree or checklist for choosing between synchronous vs asynchronous communication patterns based on specific criteria
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill contains substantial content that Claude likely already knows (basic microservices concepts, what circuit breakers are, etc.). The 'Core Concepts' section is largely redundant given the detailed patterns that follow. However, the code examples are reasonably focused without excessive commentary. | 2 / 3 |
Actionability | The skill provides fully executable Python code examples for each pattern including API Gateway, Event Bus with Kafka, Saga orchestration, and Circuit Breaker implementations. Code is complete with imports, class definitions, and usage examples that are copy-paste ready. | 3 / 3 |
Workflow Clarity | While the Saga pattern includes clear step sequencing with compensation logic, the overall skill lacks explicit validation checkpoints. There's no guidance on how to verify service boundaries are correct, test inter-service communication, or validate that resilience patterns are working. The 'When to Use' section lists scenarios but doesn't provide a decision workflow. | 2 / 3 |
Progressive Disclosure | The skill has a clear structure with a quick overview (Core Concepts), detailed patterns with code, and references to external files (references/service-decomposition-guide.md, assets/circuit-breaker.py, etc.). Navigation is well-signaled with clear section headers and the Resources section provides one-level-deep references. | 3 / 3 |
Total | 10 / 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 |
|---|---|---|
skill_md_line_count | SKILL.md is long (596 lines); consider splitting into references/ and linking | Warning |
Total | 10 / 11 Passed | |
- 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.