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.

86

1.81x
Quality

Does it follow best practices?

Impact

98%

1.81x

Average score across 3 eval scenarios

SecuritybySnyk

Passed

No known issues

SKILL.md
Quality
Evals
Security

Quality

Content

65%

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

The body is a well-structured, actionable patterns catalog with real code, but it is padded with known concepts, lacks validation workflows, and its bundle references point to non-existent files while the promised content stays inline. It earns mid-range scores on the structure and efficiency dimensions.

Suggestions

Trim or remove the 'Core Concepts' bullet explanations of patterns Claude already knows (Circuit Breaker, Bulkhead, Retry, Saga) and keep only the non-obvious guidance, to improve conciseness.

Move the full inline implementations (saga, circuit breaker, event bus, API gateway) into the referenced assets/ and references/ files so SKILL.md stays a lean overview with one-level-deep pointers, and ensure those bundle files actually exist.

Add an explicit workflow with validation checkpoints for at least one risky multi-step process (e.g., decomposing a monolith or running a saga) — validate contracts/data after each step before proceeding — to raise workflow clarity.

DimensionReasoningScore

Conciseness

The ~590-line body explains concepts Claude already knows (e.g., Circuit Breaker = "Fail fast on repeated errors", Bulkhead = "Isolate resources") and inlines full class implementations that could be trimmed; it is mostly valuable but significantly padded.

2 / 3

Actionability

Substantial concrete, executable Python is provided throughout (Saga orchestration, CircuitBreaker state machine, Kafka EventBus, API Gateway) with specific examples rather than vague direction.

3 / 3

Workflow Clarity

The content is a patterns catalog with organized sections but no multi-step process sequenced with validation checkpoints or feedback loops, so the sequence is present but checkpoints are missing.

2 / 3

Progressive Disclosure

A Resources section signals one-level-deep references, but the referenced files (references/*.md, assets/*.py) do not exist and the full implementations those assets promise are instead inlined in SKILL.md, so content that should be separate is inline with dangling references.

2 / 3

Total

9

/

12

Passed

Description

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.

The description is concise, third-person, and explicitly covers both what the skill does and when to use it with natural trigger terms. It is a strong, low-conflict description with no meaningful weaknesses.

DimensionReasoningScore

Specificity

"Design microservices architectures with service boundaries, event-driven communication, and resilience patterns" lists multiple specific concrete capabilities rather than vague language, matching the score-3 anchor.

3 / 3

Completeness

It 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 an explicit trigger clause.

3 / 3

Trigger Term Quality

"building distributed systems, decomposing monoliths, or implementing microservices" are natural phrases a user would actually say, giving good coverage of common variations.

3 / 3

Distinctiveness Conflict Risk

The microservices-architecture niche with triggers like "decomposing monoliths" is clearly distinguishable and unlikely to fire for unrelated skills.

3 / 3

Total

12

/

12

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.