istio-traffic-management
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.
89
76%
Does it follow best practices?
Impact
98%
1.03xAverage score across 6 eval scenarios
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./plugins/cloud-infrastructure/skills/istio-traffic-management/SKILL.mdQuality
Discovery
100%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This is a well-crafted skill description that clearly identifies the domain (Istio traffic management), lists specific capabilities, and provides explicit trigger guidance via a 'Use when' clause. The trigger terms cover both specific technical terms (Istio, circuit breakers) and broader conceptual terms (progressive delivery, resilience patterns), making it easy for Claude to match against user requests. The description is concise, uses third person voice, and is clearly distinguishable from other skills.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: routing, load balancing, circuit breakers, and canary deployments, all within the clearly named domain of Istio traffic management. | 3 / 3 |
Completeness | Clearly answers both what ('Configure Istio traffic management including routing, load balancing, circuit breakers, and canary deployments') and when ('Use when implementing service mesh traffic policies, progressive delivery, or resilience patterns') with an explicit 'Use when' clause. | 3 / 3 |
Trigger Term Quality | Includes strong natural keywords users would say: 'Istio', 'routing', 'load balancing', 'circuit breakers', 'canary deployments', 'service mesh', 'traffic policies', 'progressive delivery', 'resilience patterns'. Good coverage of both specific and conceptual terms. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive due to the specific mention of 'Istio' and service mesh-specific concepts like circuit breakers and canary deployments. Unlikely to conflict with generic networking or deployment skills. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
52%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
The skill excels at providing concrete, executable Istio YAML templates covering a wide range of traffic management scenarios. However, it reads more like a reference catalog than an actionable workflow guide—templates are presented without sequencing, validation steps, or error recovery guidance. The content would benefit significantly from workflow instructions showing how to apply, validate, and iterate on these configurations.
Suggestions
Add workflow sequences for key operations (e.g., canary deployment: 1. Apply DestinationRule, 2. Apply VirtualService, 3. Validate with `istioctl analyze`, 4. Verify traffic split with `istioctl proxy-config routes`, 5. Gradually increase canary weight)
Include validation checkpoints after applying each resource, such as running `istioctl analyze` and checking for warnings/errors before proceeding
Move the 7 inline templates to a separate TEMPLATES.md or EXAMPLES.md file and keep only 1-2 key examples in the main SKILL.md with references to the full set
Remove the 'Core Concepts' table and traffic flow diagram—Claude already understands Istio's resource model—and use that space for operational workflows instead
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is mostly efficient with good use of templates and tables, but includes some unnecessary content like the 'Core Concepts' table and 'Traffic Flow' diagram that Claude already understands. The 'When to Use This Skill' section and 'Best Practices' do/don't lists add moderate value but could be tighter. The sheer volume of templates (7) makes this quite long. | 2 / 3 |
Actionability | All templates are fully executable, copy-paste ready YAML manifests with correct API versions, proper field names, and realistic values. The debugging commands section provides concrete, runnable istioctl commands. Every example is production-ready rather than pseudocode. | 3 / 3 |
Workflow Clarity | There is no workflow sequencing for multi-step processes. Canary deployments, circuit breaker setup, and gateway configuration are all multi-step operations that need validation checkpoints (e.g., verify deployment exists before applying VirtualService, validate with istioctl analyze after applying, check traffic split is working). Templates are presented in isolation without sequencing or verification steps. | 1 / 3 |
Progressive Disclosure | The content is organized with clear headers and sections, but it's a monolithic document with 7 full YAML templates inline that could benefit from being split into separate reference files. There are no references to external files, and the load balancing and templates sections could be separate documents linked from a concise overview. | 2 / 3 |
Total | 8 / 12 Passed |
Validation
100%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 11 / 11 Passed
Validation for skill structure
No warnings or errors.
- Repository
- wshobson/agents
- Commit
112197c
- Reviewed
Table of Contents
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.