Name: istio-traffic-management
Rating: 53.6 (1 reviews)
Author: administrakt0r

Blog Docs Log in Get started

istio-traffic-management

Comprehensive guide to Istio traffic management for production service mesh deployments.

Quality

60%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./plugins/AI-Agents-Safe-Coding-Skills-claude/skills/istio-traffic-management/SKILL.md

The canonical home for this skill is istio-traffic-management in administrakt0r/AI-Agents-Safe-Coding-Skills

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.

The body is highly actionable, packed with complete, copy-paste-ready Istio YAML templates and concrete debug commands while staying mostly lean. Its weaknesses are a vague, non-sequenced 'Instructions' workflow lacking validation checkpoints and a dangling reference to a non-existent `resources/implementation-playbook.md` file.

Suggestions

Replace the generic 'Instructions' bullets with a concrete sequenced workflow with a validation checkpoint, e.g. 'Apply manifests → run `istioctl analyze` → fix and re-run until clean → verify routes with `istioctl proxy-config routes`'.

Create the referenced `resources/implementation-playbook.md` (or fix the path to an existing bundle file) so the in-body pointer resolves, removing the broken navigation reference.

Trim the duplicated opening line that restates the description, and tighten the generic instruction bullets to keep the already-lean body fully token-efficient.

Dimension	Reasoning	Score
Conciseness	The body is largely lean — a resource table, a traffic-flow diagram, seven YAML templates, debug commands, and tight do/don't lists — with no padding explaining what Istio or a service mesh is; it sits below 5 only because the generic 'Instructions' bullets and the duplicated opening line could be trimmed.	4 / 5
Actionability	Seven complete, copy-paste-ready YAML manifests (routing, canary, circuit breaker, retry/timeout, mirroring, fault injection, gateway) plus concrete `istioctl` debug commands cover the common cases with executable, specific examples.	5 / 5
Workflow Clarity	The 'Instructions' section offers a vague 4-step process ('Clarify goals...', 'Apply best practices...', 'validate outcomes') with no concrete sequenced checkpoints; because production traffic-mesh changes are destructive/batch-like and no explicit validate→fix→retry feedback loop is sequenced, workflow clarity is capped at 3.	3 / 5
Progressive Disclosure	Sections are well-organized with clear headers and the skill ships no bundle files, but the body signals a reference to `resources/implementation-playbook.md` that does not exist in the bundle — a broken navigation reference that pulls it down from 4.	3 / 5
	Total	15 / 20 Passed

Description

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

The description clearly identifies a specific niche (Istio traffic management for production service meshes) but frames it as a 'comprehensive guide' without naming concrete actions or providing an explicit 'Use when' trigger clause. It is distinguishable and domain-specific, yet falls short on actionability and trigger guidance.

Suggestions

Replace 'Comprehensive guide to' framing with concrete actions, e.g. 'Configure service-to-service routing, canary/blue-green deployments, circuit breakers, retries, and traffic mirroring in Istio service meshes.'

Add an explicit 'Use when' clause naming natural triggers, e.g. 'Use when configuring Istio VirtualService/DestinationRule/Gateway resources, setting up canary releases, or debugging service-mesh traffic routing.'

Include natural synonyms and resource names users say (VirtualService, DestinationRule, service mesh, canary, circuit breaker) to broaden trigger coverage.

Dimension	Reasoning	Score
Specificity	The description names the domain ('Istio traffic management', 'production service mesh deployments') but the only action framing is 'Comprehensive guide to', which is generic rather than a concrete action; it does not reach 3 because no concrete operations (e.g. routing, canary, circuit breaking) are named.	2 / 5
Completeness	It clearly answers 'what' (a comprehensive guide to Istio traffic management for production service mesh deployments) but has no 'when'/'Use when' clause, which per the guidelines caps completeness at 3.	3 / 5
Trigger Term Quality	'Istio traffic management' and 'service mesh' are relevant technical keywords a user might say, but there are no natural trigger phrases, synonyms, or file/extension-style variations; it sits below 4 which expects broader natural-term coverage.	3 / 5
Distinctiveness Conflict Risk	'Istio traffic management' is a clear, specific niche unlikely to trigger for unrelated skills; it does not reach 5 only because the trigger coverage is thin and lacks the explicit 'Use when' phrasing of the top anchor.	4 / 5
	Total	12 / 20 Passed

Validation

93%

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 — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	15 / 16 Passed

Repository: administrakt0r/AI-Agents-Safe-Coding-Skills
Path: plugins/AI-Agents-Safe-Coding-Skills-claude/skills/istio-traffic-management/SKILL.md
Commit: 57c135b

Reviewed: 4 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.