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

71%

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/backend-development/skills/microservices-patterns/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

43%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 skill is well-structured for progressive disclosure with a genuine, clearly signaled one-level-deep reference, but the body itself is a glossary-style catalog: it restates widely known patterns instead of adding decision-oriented guidance, and it offers no sequenced design workflow. The description is strong; the body's value is concentrated in the reference file rather than in the navigation tier.

Suggestions

Replace glossary bullets that restate well-known patterns (e.g., "Circuit Breaker — Fail fast on repeated errors") with decision-oriented guidance Claude does not already know: criteria for choosing saga vs. orchestrated workflow, heuristics for drawing service boundaries (data ownership, change cadence, team scope), and when to prefer sync vs. async communication.

Add a sequenced design workflow with checkpoints — e.g., 1. map bounded contexts, 2. define service contracts, 3. choose communication style per interaction, 4. assign data ownership and transaction strategy, 5. layer in resilience — instead of an unordered pattern catalog.

Link each Core Concepts entry to its corresponding section in references/details.md so the overview works as a per-pattern table of contents rather than a condensed re-explanation.

DimensionReasoningScore

Conciseness

The body is lean in form (terse bullets, no prose padding), but a large share of the Core Concepts tier restates patterns Claude already knows (e.g., "Circuit Breaker — Fail fast on repeated errors, Prevent cascade failures"), so the tokens are efficient in style yet much of the content does not earn its place. Not 2 because nothing is verbose or padded; not 4/5 because the glossary of well-known definitions adds little beyond Claude's existing knowledge.

3 / 5

Actionability

Guidance is limited to high-level hints ("Organize services around business functions", "Gradually extract from monolith") with no code, commands, decision criteria, or concrete steps inline; the only executable instruction is the pointer to references/details.md. This matches "minimal concrete guidance; high-level hints but missing the specific steps" — it is above the purely vague anchor 1 only because the pattern index and the explicit read-details instruction give a little concrete direction.

2 / 5

Workflow Clarity

No sequenced design process or checkpoints are given; the section ordering (decomposition → communication → data → resilience) and the single escalation step ("Read that file when the navigation tier above is insufficient") provide only a rough, poorly defined progression, matching "rough sequence present but many gaps; steps poorly defined; validation absent". Not 1 because the material is coherent and does include an explicit two-tier progression for depth; not 3 because there are no actual enumerated steps.

2 / 5

Progressive Disclosure

A clean two-tier structure: the body acts as a navigation-tier overview, and the single reference (references/details.md, verified to exist with 482 lines of worked examples and no further nested references) is clearly signaled with explicit guidance on when to read it. The split is appropriate — the bulk of worked examples lives in the reference, one level deep, with no duplication of the escalation path.

5 / 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 well-formed description with an explicit what/when structure, third-person voice, and natural trigger phrases. Minor gains are available from broader synonym coverage and tighter scoping of the broad "distributed systems" trigger.

DimensionReasoningScore

Specificity

"Design microservices architectures with service boundaries, event-driven communication, and resilience patterns" lists several concrete capability areas, but they are facets of a single design verb and omit data management, matching "several specific actions; minor gaps in coverage" rather than the comprehensive multi-action anchor 5.

4 / 5

Completeness

It explicitly answers both questions: a clear "what" ("Design microservices architectures with service boundaries, event-driven communication, and resilience patterns") followed by an explicit "when" with three concrete trigger conditions ("Use when building distributed systems, decomposing monoliths, or implementing microservices"), mirroring the anchor-5 example structure. Not 4 because the when-clause is already explicit and trigger-phrase-based, not merely implied.

5 / 5

Trigger Term Quality

"building distributed systems, decomposing monoliths, or implementing microservices" contains natural phrases users would say, but common variations such as "service-oriented architecture", "strangler fig", or "event-driven architecture" as a trigger are missing, so it sits at good-but-not-comprehensive keyword coverage.

4 / 5

Distinctiveness Conflict Risk

A clear microservices niche with distinct triggers ("decomposing monoliths"), but "building distributed systems" is broad enough to overlap with general system-design or messaging/event-streaming skills, matching "mostly distinct; minor overlap risk with closely related skills" rather than the minimal-conflict anchor 5.

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

wshobson/agents

Path

plugins/backend-development/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.