microservices-patterns

Master microservices architecture patterns including service boundaries, inter-service communication, data management, and resilience patterns for building distributed systems.

Quality

33%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./plugins/AI-Agents-Safe-Coding-Skills/skills/microservices-patterns/SKILL.md

The canonical home for this skill is microservices-patterns in rmyndharis/antigravity-skills

Quality

Content

25%Scale 1-5

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

This skill is essentially a placeholder — it provides a high-level outline of microservices architecture concerns but offers no concrete, actionable guidance. The four instruction steps are abstract descriptions that Claude already knows, and the sole referenced resource file does not exist in the bundle. The skill fails to teach Claude anything it doesn't already know about microservices patterns.

Suggestions

Add concrete, executable examples for at least the core patterns (e.g., a service decomposition example with specific code for API contracts, circuit breaker implementation, or saga pattern).

Replace the vague 4-step instructions with specific, detailed workflows including validation checkpoints — e.g., how to validate service boundaries, how to test inter-service communication, how to verify resilience patterns.

Either include the referenced `resources/implementation-playbook.md` in the bundle or inline the essential patterns and examples directly in the SKILL.md.

Remove generic explanations ('Identify domain boundaries') and instead provide decision frameworks, concrete heuristics, or code templates that add value beyond Claude's existing knowledge.

Dimension	Reasoning	Score
Conciseness	The skill is relatively short but includes some unnecessary content like the description repeating the title, and the 'Use this skill when' / 'Do not use this skill when' sections are somewhat generic. The instructions section is lean but borders on too thin.	3 / 5
Actionability	The instructions are entirely vague and abstract — 'Identify domain boundaries,' 'Define contracts,' 'Plan resilience' — with no concrete code, commands, specific patterns, examples, or executable guidance whatsoever. It only describes rather than instructs.	1 / 5
Workflow Clarity	There is a rough 4-step sequence but the steps are poorly defined and extremely high-level. There are no validation checkpoints, no feedback loops, and no concrete details about what each step entails. For a skill involving complex distributed systems architecture, this is insufficient.	2 / 5
Progressive Disclosure	The skill references `resources/implementation-playbook.md` for detailed patterns, but no bundle files are provided, meaning the reference is unverifiable and potentially broken. The SKILL.md itself contains almost no substantive content, making it an empty shell pointing to a missing file.	2 / 5
	Total	8 / 20 Passed

Description

41%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 reads like a course syllabus topic rather than a functional skill description. It lists broad architectural categories without specifying concrete actions Claude would perform, and completely lacks a 'Use when...' clause to guide skill selection. The microservices domain focus provides some distinctiveness, but the description needs actionable verbs and explicit trigger guidance.

Suggestions

Add a 'Use when...' clause with trigger phrases like 'Use when the user asks about designing microservices, splitting a monolith, choosing communication patterns (REST, gRPC, message queues), or implementing resilience patterns like circuit breakers and retries.'

Replace the abstract 'Master microservices architecture patterns' with concrete actions such as 'Designs service boundaries, recommends inter-service communication strategies (REST, gRPC, event-driven), implements data management patterns (saga, CQRS), and applies resilience patterns (circuit breaker, bulkhead, retry).'

Include natural trigger terms and synonyms users would say, such as 'monolith to microservices', 'API gateway', 'service discovery', 'event sourcing', 'Docker', 'Kubernetes', or 'distributed architecture'.

Dimension	Reasoning	Score
Specificity	Names the domain (microservices architecture) and lists several sub-areas (service boundaries, inter-service communication, data management, resilience patterns), but these are categories rather than concrete actions. No specific verbs like 'design', 'implement', 'debug' are tied to actionable outputs.	3 / 5
Completeness	Provides a 'what' (master microservices architecture patterns) but has no 'when' clause or trigger guidance. The description reads more like a course title than a skill selection guide. Missing 'Use when...' caps this at 3 per rubric, and the 'what' itself is more of a topic listing than a clear capability statement, bringing it to 2.	2 / 5
Trigger Term Quality	Includes relevant terms like 'microservices', 'distributed systems', 'service boundaries', 'inter-service communication', and 'resilience patterns', but misses common natural user phrases like 'API gateway', 'circuit breaker', 'event-driven', 'service mesh', 'saga pattern', or 'containerized'.	3 / 5
Distinctiveness Conflict Risk	The term 'microservices' provides some distinctiveness, but the broad scope covering architecture patterns, communication, data management, and resilience could overlap with general software architecture skills, API design skills, or distributed systems skills.	3 / 5
	Total	11 / 20 Passed

Validation

90%

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 — 10 / 11 Passed

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	10 / 11 Passed

Repository: administrakt0r/AI-Agents-Safe-Coding-Skills
Path: plugins/AI-Agents-Safe-Coding-Skills/skills/microservices-patterns/SKILL.md
Commit: 57c135b

Reviewed: 3 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.