microservices-architect

Designs distributed system architectures, decomposes monoliths into bounded-context services, recommends communication patterns, and produces service boundary diagrams and resilience strategies. Use when designing distributed systems, decomposing monoliths, or implementing microservices patterns — including service boundaries, DDD, saga patterns, event sourcing, CQRS, service mesh, or distributed tracing.

Quality

94%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Failed to scan

The risk profile of this skill

Quality

Content

88%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 strong: a checkpointed six-step workflow, multiple executable code examples, and a clean reference table pointing to real bundled files. The only weak spots are minor redundancy between the workflow, constraints lists, and the knowledge-reference glossary.

Suggestions

Remove or merge the 'Knowledge Reference' glossary paragraph — its terms duplicate the description's triggers and the reference table; move any retained detail into references/.

Trim the MUST DO / MUST NOT DO lists, since every rule is already expressed as a workflow validation checkpoint; keep only items not already covered to avoid restating the same guidance twice.

Convert the reference table rows into actual markdown links (e.g. [references/decomposition.md](references/decomposition.md)) so navigation is clickable rather than just a path string.

Dimension	Reasoning	Score
Conciseness	Mostly efficient with executable examples and a tight workflow, but the 'Knowledge Reference' paragraph and the MUST DO/MUST NOT DO lists re-state rules already encoded in the workflow checkpoints, adding minor padding; not quite the lean score-5 anchor.	4 / 5
Actionability	Four copy-paste-ready, executable code examples (correlation-ID middleware, pybreaker circuit breaker, TypeScript saga orchestrator, Kubernetes probes) cover the common cases fully, matching the score-5 anchor.	5 / 5
Workflow Clarity	Six clearly sequenced steps each carry an explicit 'Validation checkpoint:' with concrete pass criteria, providing the feedback/checklist structure the score-5 anchor calls for; not a destructive/batch skill so no cap applies.	5 / 5
Progressive Disclosure	Good structure: an overview body with a Reference Guide table signals one-level-deep references to real files in references/, all of which exist; the inlined 'Knowledge Reference' glossary paragraph is content that could live in a reference file, keeping it just below the score-5 anchor.	4 / 5
	Total	18 / 20 Passed

Description

100%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.

The description is exemplary: it pairs a precise, multi-action capability statement with an explicit, keyword-rich 'Use when...' trigger clause. It avoids fluff, uses third person, and is clearly distinguishable from adjacent skills.

Dimension	Reasoning	Score
Specificity	Lists multiple distinct concrete actions — 'Designs distributed system architectures, decomposes monoliths into bounded-context services, recommends communication patterns, and produces service boundary diagrams and resilience strategies' — with comprehensive coverage matching the score-5 anchor.	5 / 5
Completeness	Explicitly answers both 'what' (four concrete capabilities) and 'when' via a clear 'Use when...' clause with concrete trigger phrases, matching the score-5 anchor exactly.	5 / 5
Trigger Term Quality	Comprehensive natural trigger terms users would actually say — 'distributed systems, decomposing monoliths, service boundaries, DDD, saga patterns, event sourcing, CQRS, service mesh, distributed tracing' — including synonyms and pattern names.	5 / 5
Distinctiveness Conflict Risk	Occupies a clear niche (microservices/distributed-systems architecture) with distinct, specialized triggers and minimal overlap risk with other skills.	5 / 5
	Total	20 / 20 Passed

Validation

100%

Warnings & errors only

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: Jeffallan/claude-skills
Path: skills/microservices-architect/SKILL.md
Commit: 882ef55

Reviewed: 4 days ago

Table of Contents

Discovery Implementation Validation

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.