microservices-patterns

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

Install with Tessl CLI

npx tessl i github:secondsky/claude-skills --skill microservices-patterns

What are skills?

Review — 78%

Does it follow best practices?

If you maintain this skill, you can automatically optimize it using the tessl CLI to improve its score:

npx tessl skill review --optimize ./path/to/skill

Learn more

Validation — 11 / 11 Passed

Validation for skill structure

SKILL.md

Review

Evals

Evaluation results

96%

22%

Building a Resilient Microservice Client Library

Resilient HTTP service client

Criteria

Without context

With context

Uses httpx

50%

Connection timeout

100%

Read timeout

25%

100%

Uses tenacity

100%

Retry attempts

100%

Exponential backoff multiplier

100%

Backoff min/max

50%

100%

Circuit breaker failure threshold

100%

Circuit breaker recovery timeout

100%

Three CB states

100%

Fail fast when OPEN

100%

HALF_OPEN transition

100%

Reset on success

100%

Without context: $0.3077 · 1m 8s · 15 turns · 15 in / 4,296 out tokens

With context: $0.5122 · 1m 38s · 22 turns · 82 in / 5,714 out tokens

100%

Order Fulfillment Workflow for an E-Commerce Platform

Event-driven saga with compensation

Criteria

Without context

With context

Uses aiokafka

100%

Kafka producer publish

100%

Domain events published

100%

Async throughout

100%

Saga step structure

100%

Compensation on failure

100%

Reverse compensation order

100%

Failure result returned

100%

Async preferred over sync

100%

Compensation explanation

50%

100%

Kafka library named

100%

Without context: $0.3013 · 1m 21s · 11 turns · 12 in / 5,233 out tokens

With context: $0.5008 · 1m 41s · 21 turns · 20 in / 6,115 out tokens

92%

Migrating a Monolithic Checkout System to Microservices

Strangler fig decomposition and API gateway

Criteria

Without context

With context

Strangler Fig named

100%

Proxy routing described

100%

Proxy routes old and new

100%

Business capability decomposition

100%

Database per service

100%

No shared DB in code

100%

asyncio.gather in gateway

100%

Partial failure handling

100%

Uses FastAPI

Uses httpx in gateway

100%

Async gateway methods

100%

Incremental migration

100%

Without context: $0.3700 · 1m 54s · 11 turns · 12 in / 7,374 out tokens

With context: $0.6962 · 2m 28s · 27 turns · 273 in / 8,810 out tokens

Evaluated: 3 days ago
Agent: Claude Code

Table of Contents

Building a Resilient Microservice Client Library Order Fulfillment Workflow for an E-Commerce Platform Migrating a Monolithic Checkout System to Microservices

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.