CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

microservices-patterns

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

Quality

76%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./plugins/microservices-patterns/skills/microservices-patterns/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

57%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 a well-organized, code-rich pattern reference with genuinely useful saga and circuit-breaker implementations, but it front-loads a redundant conceptual section that duplicates later content and explains knowledge Claude already has. It lacks any sequenced workflow with validation checkpoints, and all implementation detail lives inline in SKILL.md instead of being split into reference files.

Suggestions

Delete the 'Core Concepts' section: its bullets duplicate the pattern sections that follow and explain distributed-systems basics (circuit breaker, retry, database-per-service) that Claude already knows.

Add a sequenced workflow with checkpoints, e.g., identify bounded contexts → define service contracts → extract one service via the strangler fig → validate boundaries with integration tests before extracting the next.

Keep SKILL.md as an overview with one-code-example-per-pattern and move the full saga, circuit breaker, and event bus implementations into reference files (e.g., references/sagas.md, references/resilience.md) with clearly signaled links.

DimensionReasoningScore

Conciseness

The "Core Concepts" section (service decomposition bullets, circuit breaker "fail fast on repeated errors", retry "transient fault handling") re-explains standard distributed-systems knowledge Claude already has and duplicates the later pattern sections with code. This is noticeably unnecessary padding that keeps it below anchor 4, though the bullet style and otherwise code-forward body prevent a 2.

3 / 5

Actionability

The body provides substantial concrete Python (OrderService publishing events, APIGateway aggregation, OrderFulfillmentSaga with compensation, a full CircuitBreaker state machine) covering the common cases. It falls short of anchor 5 because the code is not copy-paste executable — undefined types (SagaStep, Order, DomainEvent), the unexplained `circuit` decorator, and missing imports (List, asyncio, asdict).

4 / 5

Workflow Clarity

The skill is organized as a pattern catalog, not a process: there is no sequenced workflow for actually applying the patterns (e.g., steps for decomposing a monolith or migrating incrementally via the strangler fig) and no validation checkpoints for verifying boundaries or contracts. Sequence material exists only inside the saga code, fitting anchor 3 ('sequence present but checkpoints missing') rather than 4.

3 / 5

Progressive Disclosure

Section headers make the ~320-line body navigable, but all detailed pattern implementations (sagas, circuit breaker, event bus) are inlined in SKILL.md with no reference files at all — content that belongs in one-level-deep references is inline. This matches anchor 3 ('some structure but could be better organized; content that should be separate is inline') rather than 4.

3 / 5

Total

13

/

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 description that explicitly answers both what the skill does and when to use it with concrete, natural trigger phrases in third-person voice. Keyword coverage and capability listing are good but not exhaustive, leaving minor room for synonyms and broader coverage.

DimensionReasoningScore

Specificity

"Design microservices architectures with service boundaries, event-driven communication, and resilience patterns" names three concrete capability areas, matching the anchor for several specific actions with minor gaps; it is not comprehensive enough (no data management, deployment, or observability) for a 5.

4 / 5

Completeness

It clearly states what the skill does ("Design microservices architectures with service boundaries, event-driven communication, and resilience patterns") and explicitly when to use it with concrete trigger phrases ("Use when building distributed systems, decomposing monoliths, or implementing microservices"), matching the top anchor exactly.

5 / 5

Trigger Term Quality

"building distributed systems, decomposing monoliths, or implementing microservices" are natural phrases users would say, but common variations like "splitting a monolith", "service boundaries", or "event-driven" are missing, so it fits 'good keyword coverage; a few natural terms missing' rather than the comprehensive anchor.

4 / 5

Distinctiveness Conflict Risk

The microservices architecture niche has distinct triggers ("decomposing monoliths", "implementing microservices") with only minor overlap risk against general system-design or distributed-systems skills, fitting 'mostly distinct; minor overlap risk' rather than a fully clear niche.

4 / 5

Total

17

/

20

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 — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository

secondsky/claude-skills

Path

plugins/microservices-patterns/skills/microservices-patterns/SKILL.md

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.