istio-traffic-management Skill for Claude: What It Does and How to Install It

Makes Claude write Istio traffic rules: routing, canary releases, circuit breakers, retries, mirroring, fault injection and gateways.

Installs: 10.5K; on skills.sh
Stars: 42.1K; on GitHub
Updated: Oct 2026; last repo commit

This is an Istio guide from wshobson's agents collection. SKILL.md explains the four core resources (VirtualService, DestinationRule, Gateway, ServiceEntry) and the path a request takes, then gives seven YAML templates.

The templates cover basic routing, canary deployment, circuit breaker, retry and timeout, traffic mirroring, fault injection and an ingress gateway. A load balancing section and four istioctl debugging commands follow. The skill bundles no other files, so everything is in SKILL.md.

Good for

Platform engineers running Istio on Kubernetes
Teams rolling out canary or blue-green releases
Developers adding timeouts, retries and circuit breakers
Engineers testing failure handling with fault injection

Install istio-traffic-management

Claude Code

Copy this prompt.

Install the istio-traffic-management skill in Claude Code. Run this command:

/plugin marketplace add wshobson/agents
/plugin install cloud-infrastructure@claude-code-workflows

Then check that it loaded and tell me how to use it.

2
Paste it into Claude Code. It shows the change and asks before running it.

Pick one route. The plugin routes install the whole cloud-infrastructure plugin: 7 agents, 0 commands and 8 skills (counted from the plugin folder in the repo tree, which has no hooks or MCP config files). The skills-only routes install just this skill, with no agents or commands.

Built from the package data we hold. Not yet tested by us. Source.

What's in the skill

When it loads

Configure Istio traffic management including routing, load balancing, circuit breakers, and canary deployments. Use when implementing service mesh traffic policies, progressive delivery, or resilience patterns.

Sections in SKILL.md

When to Use This Skill
Core Concepts
1. Traffic Management Resources
2. Traffic Flow
Templates
Template 1: Basic Routing
Template 2: Canary Deployment
Template 3: Circuit Breaker
Template 4: Retry and Timeout
Template 5: Traffic Mirroring
Template 6: Fault Injection
Template 7: Ingress Gateway
Load Balancing Strategies
Best Practices
Do's
Don'ts

Key facts

Author: wshobson (repo owner)
License: MIT
Installs on skills.sh: 10,473 (Nov 2, 2026)
GitHub stars: 42,081 for the whole wshobson/agents repo (Nov 2, 2026)
Last repo commit: Oct 30, 2026
What it includes: 1 file: SKILL.md (7 templates, load balancing section and debugging commands). No scripts
skills.sh audits: Gen Agent Trust Hub: pass; Socket: pass; Snyk: pass (Nov 2, 2026)
Part of: The cloud-infrastructure plugin (version 1.3.3) in wshobson/agents. Counted from the plugin folder: 7 agents, 0 commands and 8 skills
Works in: Claude Code, Codex CLI, Cursor, OpenCode, Antigravity CLI, GitHub Copilot and Pi, per the README. Skills-only installers ask which tool you use

What it includes

VirtualService, DestinationRule, Gateway and ServiceEntry, with what each is for
Includes a diagram: client, gateway, virtual service, destination rule, service, pods.
Traffic resources
Route traffic to a service with a VirtualService
Write · Template 1: Basic routing
Send part of the traffic to a new version
Write · Template 2: Canary deployment
Limit connections and eject failing endpoints
Write · Template 3: Circuit breaker
Set retries and timeouts on a route
Write · Template 4: Retry and timeout
Copy live traffic to another version for testing
Write · Template 5: Traffic mirroring
Add delays or errors to test resilience
Write · Template 6: Fault injection
Expose a service through a Gateway with TLS
Write · Template 7: Ingress gateway
ROUND_ROBIN, LEAST_CONN, RANDOM, PASSTHROUGH and consistent hashing
Consistent hashing is shown with an HTTP header name.
Load balancing strategies
istioctl analyze and three istioctl proxy-config commands
Checks VirtualService configuration, effective routes, endpoints and debug logs.
Runs code · Debugging commands

From the official docs

Permissions

Low risk

What it can do

Read your data
Create and change things
Delete things
Read-only mode

Watch out for

Check which cluster a command targets
The templates and istioctl commands do not name a cluster. Confirm your current kubectl context before you apply any generated YAML. github.com
The fault injection template breaks real requests
Template 6 adds a 5 second delay to 10% of requests and a 503 to 5%. Apply it only where failures are acceptable. github.com

Security advisories

No published security advisories as of Nov 2, 2026.

Technical details

Turning on read-only	No read-only mode. Use version control and review YAML before applying it.
Sign-in and keys	SKILL.md does not mention any account or key. The ingress gateway template refers to a TLS secret named my-tls-secret in your cluster.
Scopes	Claude can write Istio YAML files in your project when you ask for routing or gateway changes The debugging section lists istioctl commands, including one with --level debug on a workload's proxy log

Questions

How do I install istio-traffic-management?

Use the install box at the top of this page. It offers the cloud-infrastructure plugin and two skills-only commands. Pick a skills-only command if you want just this skill without the plugin's other parts.

What does the istio-traffic-management skill do?

It gives Claude Istio patterns for service-to-service routing. Claude uses them to write VirtualService and DestinationRule YAML for canary releases, circuit breakers, retries, mirroring and fault injection.

Istio or Linkerd skill?

Pick by the mesh you run. This skill covers Istio resources such as VirtualService and DestinationRule. The linkerd-patterns skill in the same plugin covers Linkerd installation, ServiceProfile, traffic splits and authorization policy.

Should I install the whole cloud-infrastructure plugin?

Only if you want the rest. The plugin folder holds 7 agents, 0 commands and 8 skills, counted from the repo tree, and the tree shows no hooks or MCP config files in it. The plugin's other skills include linkerd-patterns, mtls-configuration and service-mesh-observability.

Is istio-traffic-management safe to install?

The folder holds only SKILL.md, with no scripts. Claude writes YAML for you to apply, and the debugging section lists istioctl commands, so check each command against the right cluster before you approve it.

Does istio-traffic-management work in Codex, Cursor or the Claude app?

The README documents Claude Code and Codex CLI plugin routes, and skills-only installs for the tools it lists: Cursor, OpenCode, Antigravity CLI, GitHub Copilot and Pi. We left the Claude app upload out of the install box because this skill's commands run in a terminal.

Information

updated Nov 2, 2026

Repository: wshobson/agents
Folder: plugins/cloud-infrastructure/skills/istio-traffic-management

wshobson/agents skills.sh

Sources

Docs, issue trackers and discussions this page is built from.

Show all 3

istio-traffic-management SKILL.md · github.com
linkerd-patterns SKILL.md · github.com
wshobson/agents README · github.com