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.

66

Quality

Does it follow best practices?

Impact

No eval scenarios have been run

SecuritybySnyk

Passed

No known issues

SKILL.md
Quality
Evals
Security

Quality

Content

57%

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 overview with good progressive disclosure to a real reference file, but it largely restates concepts Claude already knows and lacks concrete, executable guidance or a sequenced workflow. It functions better as a table of contents than as actionable instruction.

Suggestions

Trim or condense the Core Concepts glosses for well-known patterns (Circuit Breaker, Saga, Bulkhead) to avoid restating knowledge Claude already has; keep only non-obvious guidance.

Add at least one concrete, executable artifact in the body — e.g., a minimal code/config snippet or a concrete decision rule — so the skill instructs rather than merely describes.

Introduce a short sequenced workflow with checkpoints for the most common task (e.g., decomposing a monolith: identify bounded contexts → extract one service → validate contract → repeat) to raise workflow clarity.

DimensionReasoningScore

Conciseness

The bullet form is lean, but the Core Concepts section re-catalogues well-known patterns (Circuit Breaker, Saga, Bulkhead, Database Per Service) with one-line glosses Claude already knows, so not every token earns its place.

2 / 3

Actionability

It names concrete patterns and decomposition strategies, but provides no executable code, commands, or concrete application guidance — the "how" is deferred to references, leaving guidance incomplete.

2 / 3

Workflow Clarity

Content is organized into sections, but this is a pattern catalog with no sequenced multi-step workflow or validation checkpoints, so it is not a clear process with feedback loops.

2 / 3

Progressive Disclosure

A clear overview points one level deep to the real references/details.md, signaled with explicit guidance ("Read that file when the navigation tier above is insufficient"), matching the well-signaled one-level-deep anchor.

3 / 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.

A concise, third-person description that clearly states capabilities and provides explicit trigger guidance with natural user terms. It is distinctive and complete, scoring well across all dimensions.

DimensionReasoningScore

Specificity

Names concrete architectural concerns — "service boundaries, event-driven communication, and resilience patterns" — rather than vague fluff, matching the multiple-specific-concrete-actions anchor.

3 / 3

Completeness

Explicitly answers both what ("Design microservices architectures with...") and when ("Use when..."), with an explicit trigger clause.

3 / 3

Trigger Term Quality

The "Use when building distributed systems, decomposing monoliths, or implementing microservices" clause covers natural terms a user would actually say.

3 / 3

Distinctiveness Conflict Risk

Targets a clear microservices-architecture niche with distinct triggers, making conflict with other skills unlikely.

3 / 3

Total

12

/

12

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.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
wshobson/agents
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.