CtrlK
BlogDocsLog inGet started
Tessl Logo

microservices-patterns

Design microservices architectures with service boundaries, event-driven communication, and resilience patterns. Use when building distributed systems, decomposing monoliths, or implementing microservices.

78

1.81x
Quality

68%

Does it follow best practices?

Impact

98%

1.81x

Average score across 3 eval scenarios

SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./tests/ext_conformance/artifacts/agents-wshobson/backend-development/skills/microservices-patterns/SKILL.md

The canonical home for this skill is microservices-patterns in wshobson/agents

SKILL.md
Quality
Evals
Security

Quality

Content

53%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The body is actionable and code-rich but suffers from structural problems: a duplicated conceptual overview and, most seriously, a Resources section pointing to nonexistent bundle files while the inlined code those files would hold bloats the SKILL.md. Progressive disclosure is the weakest dimension.

Suggestions

Create the referenced bundle files (references/service-decomposition-guide.md, references/communication-patterns.md, references/saga-implementation.md, assets/circuit-breaker.py, assets/event-bus-template.py, assets/api-gateway-template.py) and move the large code blocks into them, leaving SKILL.md as a concise overview — this fixes the dangling references and the monolithic inlining.

Remove the redundancy between "Core Concepts" (conceptual bullets) and the later detailed pattern sections, or collapse Core Concepts into a brief pointer to the expanded sections, to tighten token efficiency.

Add missing imports and define (or stub) the helper types referenced by the code (asyncio, uuid, List, Order, PaymentRequest, SagaResult, StepResult, ReservationResult, and the *Event classes) so the examples are fully executable rather than partially schematic.

DimensionReasoningScore

Conciseness

The intro and "When to Use" list duplicate the description, and the "Core Concepts" section re-states the same four areas later expanded with full code, so while mostly efficient there is clear redundancy that could be trimmed.

3 / 5

Actionability

Large executable code blocks (service classes, API gateway, event bus, saga, circuit breaker) provide concrete, mostly copy-paste-ready guidance, with minor gaps such as missing imports (asyncio, uuid) and undefined helper types (SagaResult, StepResult, event classes).

4 / 5

Workflow Clarity

This is a pattern catalog rather than a sequenced workflow; there are no explicit checkpoints or validation feedback loops, though Best Practices and Common Pitfalls give some structure to selection and application.

3 / 5

Progressive Disclosure

The "Resources" section references six bundle files (references/*.md, assets/*.py) but none of those directories or files exist, and the full implementations are inlined in a ~590-line body — content that clearly belongs in separate files is inlined with dangling references.

2 / 5

Total

12

/

20

Passed

Description

83%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A strong, well-formed description: third-person voice, explicit what-and-when, and concrete trigger phrases. It is comprehensive on completeness with only minor specificity and distinctiveness gaps.

DimensionReasoningScore

Specificity

"Design microservices architectures with service boundaries, event-driven communication, and resilience patterns" names the domain plus several concrete capabilities (boundaries, event-driven comms, resilience), with only minor coverage gaps.

4 / 5

Completeness

It explicitly states 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 concrete trigger phrases.

5 / 5

Trigger Term Quality

"Use when building distributed systems, decomposing monoliths, or implementing microservices" surfaces natural phrases users would say, though it misses some synonyms/variants like 'service-oriented' or file/format triggers.

4 / 5

Distinctiveness Conflict Risk

"decomposing monoliths" and "implementing microservices" carve a clear microservices niche, but the broader "building distributed systems" trigger creates minor overlap risk with general architecture skills.

4 / 5

Total

17

/

20

Passed

Validation

87%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

skill_md_line_count

SKILL.md is long (596 lines); consider splitting into references/ and linking

Warning

referenced_paths_exist

Referenced path issues: 6 missing

Warning

Total

14

/

16

Passed

Repository
Dicklesworthstone/pi_agent_rust
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.