Service Mesh Patterns

Implement service mesh patterns for observability, resilience, and traffic management. Use when managing complex microservices communication at scale.

48 stars 10 forksDevOps & Cloud Plugin marketplace

Install

Claude Code plugin
/plugin marketplace add sethdford/claude-skills

The repo is a Claude Code plugin marketplace. Run /plugin afterwards to pick the plugin that includes this skill.

skills CLI (Claude Code, Cursor, Codex and more)
npx skills add sethdford/claude-skills --skill service-mesh-patterns
Manual install
git clone --depth 1 https://github.com/sethdford/claude-skills.git /tmp/claude-skills
mkdir -p ~/.claude/skills
cp -r /tmp/claude-skills/architect/system-design/skills/service-mesh-patterns ~/.claude/skills/service-mesh-patterns

Personal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.

From the SKILL.md

# Service Mesh Patterns

Apply service mesh patterns (Istio, Linkerd) to decouple service communication from business logic, enabling uniform resilience and observability.

## Context

You are designing service mesh infrastructure for microservices. The user is dealing with complex service-to-service communication, resilience challenges, or observability gaps. Read their current infrastructure.

## Domain Context

Based on Istio/Linkerd reference implementations and distributed systems research:

- **Sidecar Proxy**: Per-service proxy handling network concerns (retries, circuit breaking, auth)
- **Control Plane**: Centralized configuration of routing, security, observability
- **Mutual TLS**: Encrypted, authenticated service-to-service communication by default
- **Traffic Management**: Canary deployments, retries, timeouts, load balancing
- **Observability**: Distributed tracing, metrics collection, access logs

## Instructions

1. **Assess Mesh Necessity**: Service mesh adds complexity. Evaluate: are you managing >10 services? Do you need fine-grained traffic control? Do you have mTLS requirements? If yes to 2+, mesh may help.

2. **Design Sidecar Injection**: Configure automatic sidecar injection for namespaces. Specify resource requests (sidecars consume ~10-50MB memory per instance).

3. **Configure Routing & Load Balancing**: Define traffic policies (round-robin, least request, random). For canary deployments, specify traffic split (90% stable, 10% canary).
Read the full skill on GitHub

Details

Skill name
service-mesh-patterns
Path
architect/system-design/skills/service-mesh-patterns/SKILL.md
License
MIT
Repo updated
11 March 2026

FAQ

What does the Service Mesh Patterns skill do?

Implement service mesh patterns for observability, resilience, and traffic management. Use when managing complex microservices communication at scale.

How do I install the Service Mesh Patterns skill?

Claude Code plugin: /plugin marketplace add sethdford/claude-skills. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.

Is Service Mesh Patterns popular?

It lives in sethdford/claude-skills, which has 48 GitHub stars and 10 forks.

Related skills

Browse the most popular Claude skills, all devops & cloud skills, or write your own with the skills generator.