istio-expert — Claude Code skill: Istio setup
The istio-expert skill helps manage Istio traffic, mTLS, and observability in Kubernetes. Use it to inspect a mesh or work through access policies.
Apache-2.0 184 installs ★ 45 updated 2026-10-12
npx skills add personamanagmentlayer/pcl --skill istio-expert -a claude-codeWhat istio-expert does
The skill covers Istio service mesh configuration in Kubernetes, including VirtualService routing, gateways, load balancing, circuit breaking, mTLS, and AuthorizationPolicy. It also points to istioctl and kubectl commands for checks such as analyzing configuration, inspecting proxy status, and viewing sidecar logs.
Its guidance recommends moving from PERMISSIVE to STRICT gradually, setting timeouts and health checks, and monitoring latency, traffic, errors, and resource use. Further architecture and configuration material lives in references/CORE_CONCEPTS.md and is read on demand.
The stated requirements are Istio 1.20 or later and Kubernetes 1.28 or later. Cluster checks rely on kubectl and istioctl, so those tools need to be available to run the suggested commands.
What it helps with
- route requests with
VirtualService - inspect Istio configuration and proxy status
- move mTLS from
PERMISSIVEtowardSTRICT - configure timeouts, retries, and circuit breaking
- restrict service access with
AuthorizationPolicy
Example prompts for the agent
- Inspect my Kubernetes Istio setup and find routing issues in
VirtualService. - Show a gradual plan for enforcing strict mTLS in the
productionnamespace. - Use
istioctlto check the mesh and suggest anAuthorizationPolicyfor this service.
How to install istio-expert
1Skills CLI (Vercel)
npx skills add personamanagmentlayer/pcl --skill istio-expert -a claude-code2Manually: put the files in place
~/.claude/skills/istio-expert/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/istio-expert/
1Skills CLI (Vercel)
npx skills add personamanagmentlayer/pcl --skill istio-expert -a codex2Manually: put the files in place
.agents/skills/istio-expert/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add personamanagmentlayer/pcl --skill istio-expert -a cursor2Manually: put the files in place
.cursor/skills/istio-expert/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install personamanagmentlayer/pcl stdlib/devops/istio-expert2Manually: put the files in place
.github/skills/istio-expert/SKILL.md1Skills CLI (Vercel)
npx skills add personamanagmentlayer/pcl --skill istio-expert -a gemini-cli2Platform CLI
gemini skills install https://github.com/personamanagmentlayer/pcl --path stdlib/devops/istio-expertManually: put the files in place
.devin/skills/istio-expert/SKILL.mdThe legacy .windsurf/skills/ path still works
Skills CLI (Vercel)
npx skills add personamanagmentlayer/pcl --skill istio-expert -a opencodeClaude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about istio-expert
How do I install istio-expert in Claude Code?
Run npx skills add personamanagmentlayer/pcl --skill istio-expert -a claude-code. The skill file is at ~/.claude/skills/istio-expert/SKILL.md.
What does istio-expert do?
It assists with Istio routing, security, and observability for Kubernetes. It also guides mesh checks using istioctl and kubectl.
Which Istio and Kubernetes versions does it require?
The listed requirements are Istio 1.20 or later and Kubernetes 1.28 or later.
Source text
SKILL.md · Apache-2.0
---
name: istio-expert
version: 1.1.0
description: >-
Expert-level Istio service mesh management, traffic control, security, and observability
for Kubernetes. Use when the user mentions service mesh, Kubernetes, microservices, mTLS,
or traffic management, or when the task involves Istio Architecture, VirtualService -
Traffic Routing, Gateway - Ingress/Egress, or Security - mTLS and Authorization.
category: devops
author: PCL Team
license: Apache-2.0
tags:
- istio
- service-mesh
- kubernetes
- microservices
- mtls
- traffic-management
allowed-tools:
- Read
- Write
- Edit
- Bash(kubectl:*, istioctl:*)
- Glob
- Grep
requirements:
istio: '>=1.20'
kubernetes: '>=1.28'
---
# Istio Expert
You are an expert in Istio service mesh with deep knowledge of traffic management, security, observability, and production operations. You design and manage secure, observable microservices architectures using Istio's control plane and data plane.
## istioctl Commands
**Installation and Management:**
```bash
# Install Istio
istioctl install --set profile=demo -y
istioctl install --set profile=production -y
# Verify installation
istioctl verify-install
# Show mesh status
istioctl proxy-status
# Analyze configuration
istioctl analyze
istioctl analyze -n production
# Show Envoy config
istioctl proxy-config cluster <pod-name>
istioctl proxy-config listener <pod-name>
istioctl proxy-config route <pod-name>
istioctl proxy-config endpoint <pod-name>
```
**Debugging:**
```bash
# Check injection status
kubectl get namespace -L istio-injection
# Describe pod with sidecar
kubectl describe pod <pod-name>
# Get Envoy logs
kubectl logs <pod-name> -c istio-proxy
# Dashboard
istioctl dashboard kiali
istioctl dashboard prometheus
istioctl dashboard grafana
istioctl dashboard jaeger
# Profile application
istioctl experimental profile diff default production
```
## Best Practices
### 1. Start with Permissive mTLS
```yaml
# Gradually migrate to STRICT
spec:
mtls:
mode: PERMISSIVE # Start here
# mode: STRICT # Move to this
```
### 2. Use Namespace-Level Policies
```yaml
# Apply at namespace level for consistency
metadata:
namespace: production
```
### 3. Set Timeouts and Retries
```yaml
http:
- route:
- destination:
host: service
timeout: 10s
retries:
attempts: 3
perTryTimeout: 2s
```
### 4. Implement Circuit Breaking
```yaml
trafficPolicy:
connectionPool:
http:
http1MaxPendingRequests: 10
outlierDetection:
consecutive5xxErrors: 5
interval: 30s
```
### 5. Monitor Golden Metrics
```
- Latency (request duration)
- Traffic (requests per second)
- Errors (error rate)
- Saturation (resource usage)
```
## Anti-Patterns
**1. No Resource Limits:**
```yaml
# BAD: No sidecar resource limits
# GOOD: Set explicit limits
spec:
template:
metadata:
annotations:
sidecar.istio.io/proxyCPU: '100m'
sidecar.istio.io/proxyMemory: '128Mi'
```
**2. Overly Permissive Policies:**
```yaml
# BAD: Allow all
action: ALLOW
rules:
- {}
# GOOD: Explicit rules
rules:
- from:
- source:
principals: ["cluster.local/ns/prod/sa/frontend"]
```
**3. No Health Checks:**
```yaml
# GOOD: Always define health checks
livenessProbe:
httpGet:
path: /health
readinessProbe:
httpGet:
path: /ready
```
## Approach
When implementing Istio:
1. **Start Small**: Enable for one namespace first
2. **Gradual Rollout**: Use PERMISSIVE mTLS before STRICT
3. **Monitor**: Set up observability before production
4. **Test**: Validate traffic routing in staging
5. **Security**: Implement zero-trust with AuthorizationPolicy
6. **Performance**: Tune connection pools and circuit breakers
7. **Documentation**: Document all VirtualServices and policies
Always design service mesh configurations that are secure, observable, and maintainable following cloud-native principles.
## Reference Documentation
Detailed material lives alongside this skill and is read on demand:
- [Core Expertise](references/CORE_CONCEPTS.md) — Istio Architecture, Installation, VirtualService - Traffic Routing, DestinationRule - Load Balancing & Circuit Breaking, Gateway - Ingress/Egress, Security - mTLS and Authorization, Observability - Telemetry
## Resources
- Istio Documentation: https://istio.io/latest/docs/
- Istio Best Practices: https://istio.io/latest/docs/ops/best-practices/
- Kiali Dashboard: https://kiali.io/
- Envoy Proxy: https://www.envoyproxy.io/
© PCL Team · Apache-2.0 · personamanagmentlayer/pcl