CtrlK
BlogDocsLog inGet started
Tessl Logo

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.

68

Quality

82%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

Quality

Content

65%

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

Highly actionable templates and commands make the body practically useful, but generic boilerplate sections, lack of an explicit sequenced workflow with validation checkpoints, and a monolithic inline structure hold it back from top marks.

Suggestions

Remove the generic 'Instructions' and 'Do not use this skill when' boilerplate or replace it with Istio-specific sequencing (e.g., apply VirtualService -> DestinationRule -> run `istioctl analyze` -> verify routes).

Move the seven YAML templates into reference files under references/ (e.g., routing.md, canary.md, resilience.md) and keep SKILL.md as a concise overview that links one level deep.

Add explicit validation checkpoints (istioctl analyze, proxy-config routes) tied to each operation rather than listing debugging commands only at the end.

DimensionReasoningScore

Conciseness

The templates and table are lean, but generic boilerplate ('Clarify goals, constraints, and required inputs', 'The task is unrelated to istio traffic management') adds no Istio-specific value and could be cut — mostly efficient but not every token earns its place.

2 / 3

Actionability

Seven complete, copy-paste-ready YAML templates plus concrete istioctl debugging commands give fully executable guidance with specific examples.

3 / 3

Workflow Clarity

Content is organized by scenario rather than as a sequenced workflow; the 'Instructions' steps are generic and istioctl analyze appears as a tool but not as an explicit validate-then-proceed checkpoint, so validation is implicit.

2 / 3

Progressive Disclosure

Well-structured into clear sections, but at ~330 lines it is a monolithic inline catalog with no bundle reference files to offload the seven templates into — content that could be split is inline, so it is not the lean overview-with-one-level-references anchor.

2 / 3

Total

9

/

12

Passed

Description

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.

A strong description: concrete capabilities, natural trigger terms, explicit when-guidance, and a clearly distinct Istio niche. No first/second-person voice or fluff to penalize.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — 'routing, load balancing, circuit breakers, and canary deployments' — matching the multi-action anchor rather than the single-action score 2.

3 / 3

Completeness

Explicitly answers both what ('Configure Istio traffic management...') and when ('Use when implementing service mesh traffic policies...'), matching the explicit-trigger anchor.

3 / 3

Trigger Term Quality

Covers natural user terms ('Istio', 'service mesh', 'canary deployments', 'circuit breakers', 'progressive delivery') in third person, with no jargon-only or generic phrasing.

3 / 3

Distinctiveness Conflict Risk

Istio-specific niche with distinct triggers unlikely to collide with other skills; far from the generic 'helps with code and documents' anchor.

3 / 3

Total

12

/

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.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
rmyndharis/antigravity-skills
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.