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.03x

Quality

82%

Does it follow best practices?

Impact

98%

1.03x

Average score across 6 eval scenarios

Securityby

Passed

No findings from the security scan

Quality

Content

72%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.

Highly actionable and token-efficient, with copy-paste-ready Istio templates and debugging commands. Its weaknesses are structural: it lacks a sequenced workflow with validation checkpoints for risky rollout operations, and it keeps all content inline rather than splitting detailed references into separate files.

Suggestions

Add a short ordered workflow for applying changes (e.g., apply VirtualService/DestinationRule → run `istioctl analyze` → verify with `istioctl proxy-config routes` → validate canary traffic split before increasing weight), with an explicit validate-before-proceeding checkpoint for canary and fault-injection operations.

Move the bulkier reference material (full template library, load-balancing strategy catalog) into separate reference files under references/ and link to them from SKILL.md so the main file stays a concise overview.

Add a brief verification section confirming expected behavior after each deployment pattern (e.g., check Kiali graph / Jaeger traces) to close the feedback loop on destructive or rollout operations.

Dimension	Reasoning	Score
Conciseness	Largely lean and example-driven with minimal over-explanation of concepts Claude already knows, though the "Best Practices" Do's/Don'ts and the resource table add some content that could be trimmed further.	4 / 5
Actionability	Seven copy-paste-ready YAML templates plus concrete istioctl debugging commands cover the common routing, canary, circuit-breaker, retry, mirroring, fault-injection, and gateway cases with executable specifics.	5 / 5
Workflow Clarity	The body presents categorized templates rather than a sequenced procedure, and the deployment-affecting operations (canary, circuit breaker, fault injection) lack explicit validate-then-proceed checkpoints; per the feedback-loop guidance this caps the score at 3.	3 / 5
Progressive Disclosure	It is well-sectioned but monolithic — all templates and references live inline in SKILL.md with no one-level-deep reference files, and no bundle files exist to split out the heavier reference material.	3 / 5
	Total	15 / 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, third-person description that concisely states concrete capabilities and provides an explicit "Use when" trigger clause. Minor synonym coverage in the trigger terms is the only gap, keeping it just short of perfect on trigger-term quality.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions — "Configure Istio traffic management including routing, load balancing, circuit breakers, and canary deployments" — giving comprehensive coverage of the skill's capabilities rather than vague abstraction.	5 / 5
Completeness	Explicitly answers both halves: the "what" (configure routing, load balancing, circuit breakers, canary deployments) and the "when" via a clear "Use when implementing service mesh traffic policies, progressive delivery, or resilience patterns" trigger clause.	5 / 5
Trigger Term Quality	Includes natural phrases users would say ("service mesh traffic policies", "progressive delivery", "canary deployments", "circuit breakers") but omits a few common synonyms (e.g., "blue-green", "retries", "traffic mirroring") that appear in the body.	4 / 5
Distinctiveness Conflict Risk	Occupies a clear Istio/service-mesh niche with distinct triggers ("Istio", "service mesh", "progressive delivery") that are unlikely to fire for unrelated skills.	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: wshobson/agents
Path: plugins/cloud-infrastructure/skills/istio-traffic-management/SKILL.md
Commit: d6837ae

Reviewed: about 13 hours 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.