microservices-patterns

3 stars

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

Marketplace

Third-Party Agent Skill: Review the code before installing. Agent skills execute in your AI assistant's environment and can access your files. Learn more about security

Installation for Agentic Skill

View all platforms →

Claude Code (CLI) Fast

skilz install secondsky/claude-skills/microservices-patterns

OpenCode (CLI) Fast

skilz install secondsky/claude-skills/microservices-patterns --agent opencode

OpenAI Codex (CLI) Native

skilz install secondsky/claude-skills/microservices-patterns --agent codex

Gemini CLI (Project) Project

skilz install secondsky/claude-skills/microservices-patterns --agent gemini

First time? Install Skilz: pip install skilz

Works with 14 AI coding assistants

Cursor, Aider, Copilot, Windsurf, Qwen, Kimi, and more...

View All Agents

For Claude Desktop Easy

Download Agent Skill ZIP

Extract and copy to ~/.claude/skills/ then restart Claude Desktop

Manual Installation

1. Clone the repository:

git clone https://github.com/secondsky/claude-skills

2. Copy the agent skill directory:

cp -r claude-skills/plugins/microservices-patterns/skills/microservices-patterns ~/.claude/skills/

Owner: secondsky (GitHub)
Repository: claude-skills
Stars: 3
Type: Technical
Meta-Domain: cloud infrastructure
Primary Domain: kubernetes
Market Score: 84

Agentic Skill Grades →

Agent Skill Grade

Score: 84/100 Click to see breakdown

Score Breakdown

Spec Compliance

12/15

PDA Architecture

15/30

Ease of Use

23/25

Writing Style

9/10

Utility

18/20

Modifiers: +7

Areas to Improve

No Layered References
Missing Table of Contents
Limited Feedback Loops

Recommendations

Focus on improving Pda (currently 15/30)
Address 1 high-severity issues first
Add trigger phrases to description for discoverability

Graded: 2026-01-19

Developer Feedback

I took a look at your microservices-patterns skill and wanted to share some thoughts.

Links:

The TL;DR

You're at 84/100, solidly in B territory. This is based on Anthropic's Claude Skills best practices. Your strongest area is Ease of Use (23/25)—your trigger terms are clear and the "When to Use" section is well-written. The main drag is Progressive Disclosure Architecture (15/30)—you've got 326 lines in a single file with no layered structure or reference materials to break things up.

What's Working Well

Clear discoverability. Your description nails the trigger phrases ("microservices patterns," "API gateway," "service mesh"), making it easy for Claude to know when to invoke this.
Solid examples. The code samples for Circuit Breaker, Service Discovery, and API Gateway patterns are practical and match what people actually need to implement.
Consistent terminology. You stick with the same language throughout—"services," "patterns," "failures"—which makes it easy to follow.
Good foundational content. The explanations are focused and don't have fluff; you're getting real value per line.

The Big One

No layered references or deeper documentation. Everything's dumped into one 326-line file. This kills your Progressive Disclosure score (15/30) because Claude can't efficiently navigate or reference deeper material when needed.

Here's the fix: Extract your code examples and detailed pattern implementations into separate reference files:

microservices-patterns/
├── SKILL.md (keep to ~150 lines with pattern overviews)
├── references/
│   ├── circuit-breaker-example.md
│   ├── service-discovery-example.md
│   ├── api-gateway-example.md
│  ...

Browse Category

More cloud infrastructure Agentic Skills

Report Security Issue

Found a security vulnerability in this agent skill?