Microservices
Service boundaries, communication patterns, event sourcing, CQRS, and distributed tracing
Install
npx skills add cosmicstack-labs/mercury-agent-skills --skill microservicesgit clone --depth 1 https://github.com/cosmicstack-labs/mercury-agent-skills.git /tmp/mercury-agent-skills
mkdir -p ~/.claude/skills
cp -r /tmp/mercury-agent-skills/categories/backend/microservices ~/.claude/skills/microservicesPersonal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.
From the SKILL.md
# Microservices
Design and operate microservice architectures.
## Service Boundaries
### Bounded Context (DDD)
- Each service owns a domain concept
- Service has its own database (no DB sharing)
- Communication via API or events
- Avoid "shared" services (leads to tight coupling)
### Service Sizing
- **Too small**: Nano-services — high overhead, hard to debug
- **Too large**: Distributed monolith — worst of both worlds
- **Right size**: Team can build, test, deploy independently
## Communication Patterns
| Pattern | Type | When |
|---------|------|------|
| REST | Sync | Request-response, CRUD |
| gRPC | Sync (fast) | Internal, high throughput |
| Event | Async | Decoupled workflows |
| Message Queue | Async | Buffered, reliable delivery |
### Event-Driven Communication
```
Service A → Event Bus → Service B
→ Service C
→ Service D
```
Benefits: eventual consistency, loose coupling, replayability.
## CQRS (Command Query Responsibility Segregation)
- Separate read and write models
- Queries go to optimized read stores (materialized views)
- Commands go to write stores (normalized)
- Eventually consistent between them
## Distributed Tracing
- Correlation ID passed across all services
- Use OpenTelemetry for instrumentation
- Trace each request: Service → Queue → DB → External API
- Visualize in Jaeger or Zipkin
- Alert on traces that exceed latency SLOs
## Anti-Patterns to Avoid
❌ Shared database between servicesDetails
- Skill name
microservices- Repository
- cosmicstack-labs/mercury-agent-skills
- Path
categories/backend/microservices/SKILL.md- License
- MIT
- Repo updated
- 25 August 2026
FAQ
What does the Microservices skill do?
Service boundaries, communication patterns, event sourcing, CQRS, and distributed tracing
How do I install the Microservices skill?
skills CLI (Claude Code, Cursor, Codex and more): npx skills add cosmicstack-labs/mercury-agent-skills --skill microservices. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.
Is Microservices popular?
It lives in cosmicstack-labs/mercury-agent-skills, which has 492 GitHub stars and 68 forks.
Related skills
Accessibility
492cosmicstack-labs/mercury-agent-skills
Achieve and maintain WCAG compliance through inclusive design practices, proper ARIA usage, and comprehensive testing methodologies.
Accessibility Testing
492cosmicstack-labs/mercury-agent-skills
WCAG 2.1/2.2 audit, axe, Lighthouse, manual testing, screen reader testing, and remediation
Agent Audit Logging
492cosmicstack-labs/mercury-agent-skills
Implement comprehensive audit logging and reporting for multi-agent systems. Covers event capture, structured logging, traceability, compliance reporting, forensic analysis, and real-time monitoring dashboards for agent actions and decisions.
Nodejs Patterns
492cosmicstack-labs/mercury-agent-skills
Async control flow, error handling, module design, streams, and production hardening
Message Queues
492cosmicstack-labs/mercury-agent-skills
RabbitMQ, Kafka, SQS, pub/sub, competing consumers, dead letter queues, and event streaming
Now Reading Page
329readwiseio/readwise-skills
Generate a personal "Now Reading" webpage from your Reader library
Browse the most popular Claude skills, all software development skills, or write your own with the skills generator.