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.

1.01x

Quality

85%

Does it follow best practices?

Impact

93%

1.01x

Average score across 3 eval scenarios

Securityby

Passed

No findings from the security scan

The canonical home for this skill is istio-traffic-management in wshobson/agents

Quality

Content

78%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A highly actionable, well-organized reference skill whose templates are immediately usable and whose debugging commands are concrete. Its main weaknesses are that everything lives in one monolithic SKILL.md rather than being split across reference files, and there is no explicit configure-then-verify workflow linking templates to the istioctl validation commands.

Suggestions

Split the seven templates into per-topic reference files (e.g., references/canary.md, references/circuit-breaking.md) with clearly signaled links from SKILL.md, keeping only a quick-start routing example inline.

Add a short explicit workflow — apply the DestinationRule first, then the VirtualService, then verify with 'istioctl analyze' and 'istioctl proxy-config routes' — to tie configuration to the existing debugging commands.

Trim the Core Concepts table and traffic-flow diagram, which restate Istio knowledge Claude already has, and drop the 'Comprehensive guide' intro sentence.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient — templates, a terse resource table, and debugging commands — but sections like the 'Core Concepts' resource table and the traffic-flow diagram partially restate Istio knowledge Claude already has, and the 'Comprehensive guide...' intro line is padding.	4 / 5
Actionability	Seven fully executable, copy-paste-ready YAML templates (routing, canary, circuit breaker, retry/timeout, mirroring, fault injection, ingress) plus concrete istioctl commands cover the common cases with no pseudocode or gaps.	5 / 5
Workflow Clarity	Each template is self-sufficient and unambiguous, and 'istioctl analyze' / proxy-config commands provide verification capability, but no explicit apply-then-verify sequence or error-recovery loop ties configuration to the debugging steps.	4 / 5
Progressive Disclosure	The single ~320-line file is well-sectioned with headers, but all template and reference material is inlined in SKILL.md with no bundle files or split references — content that would fit naturally in separate reference files (e.g., per-template guides) stays inline.	3 / 5
	Total	16 / 20 Passed

Description

92%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A strong description: concise, third-person, and specific, with an explicit 'Use when...' clause covering concrete trigger scenarios. The only gap is a handful of natural trigger synonyms (blue-green, mirroring, fault injection) that would round out keyword coverage.

Dimension	Reasoning	Score
Specificity	The description lists multiple specific concrete actions — 'routing, load balancing, circuit breakers, and canary deployments' — giving comprehensive coverage of Istio traffic management capabilities with no vague filler.	5 / 5
Completeness	It explicitly answers both what it does ('Configure Istio traffic management including routing, load balancing, circuit breakers, and canary deployments') and when to use it ('Use when implementing service mesh traffic policies, progressive delivery, or resilience patterns') with concrete trigger phrases.	5 / 5
Trigger Term Quality	Natural phrases like 'canary deployments', 'circuit breakers', 'service mesh', 'progressive delivery', and 'resilience patterns' are present, but common variations users might say such as 'blue-green', 'traffic mirroring', or 'fault injection' are missing.	4 / 5
Distinctiveness Conflict Risk	It occupies a clear Istio/service-mesh traffic-management niche with distinct triggers ('service mesh traffic policies', 'progressive delivery'), making conflict with other skills minimal.	5 / 5
	Total	19 / 20 Passed

Validation

100%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository: Dicklesworthstone/pi_agent_rust
Path: tests/ext_conformance/artifacts/agents-wshobson/cloud-infrastructure/skills/istio-traffic-management/SKILL.md
Commit: a65ce00

Reviewed: 6 days ago

Table of Contents

Discovery Implementation Validation

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.