CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

service-mesh-expert

Design service meshes with Istio or Linkerd, including traffic management, security, and observability. Use when configuring service communication, mesh policies, or multi-cluster networking.

Quality

73%

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

Fix and improve this skill with Tessl

tessl review fix ./skills/service-mesh-expert/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

46%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 a generic template with a domain name substituted in: it lists plausible workflow steps and best practices but contains zero executable guidance — no commands, YAML, or code — and much of it is boilerplate filler. The description is strong, but the content fails to deliver the concrete, actionable instruction a service-mesh skill requires.

Suggestions

Replace vague instructions with executable examples: add istioctl install commands and sample YAML for VirtualService traffic splitting, DestinationRule mTLS, and AuthorizationPolicy so guidance is copy-paste ready.

Delete the boilerplate sections — 'Do not use this skill when' (tautological), the generic 'Instructions' list, and the intro paragraph that restates the description — and keep only domain-specific content.

Add validation checkpoints and feedback loops to the workflow, e.g., after applying policies verify with 'istioctl x describe' or check mTLS status, and only proceed when checks pass.

DimensionReasoningScore

Conciseness

The body is short and doesn't explain concepts Claude already knows, but it is padded with empty boilerplate — 'Apply relevant best practices and validate outcomes', a tautological 'Do not use this skill when the task is unrelated to service mesh expert', and an intro paragraph that duplicates the frontmatter description. Fits the 'mostly efficient but includes some unnecessary content' anchor; not 2 because there is no conceptual over-explanation, only filler.

3 / 5

Actionability

There is no code, command, or configuration example anywhere in the body — no istioctl commands, no VirtualService/DestinationRule/AuthorizationPolicy YAML, nothing executable. It does name concrete Istio primitives ('mTLS, AuthorizationPolicy', 'destination rules'), giving minimal concrete guidance, which places it above the 'entirely vague' anchor but squarely in 'high-level hints missing the specific steps to execute'.

2 / 5

Workflow Clarity

The 7-step workflow lists a coherent sequence (assess → design → implement → configure → test → document), matching the anchor for steps present but checkpoints missing. 'Test failover and resilience patterns' is a test step but there are no explicit validation checkpoints, commands, or feedback loops; not 2 because the sequence is well-defined rather than full of gaps.

3 / 5

Progressive Disclosure

The body is a short (~50 line), well-sectioned overview with no bundle files and no references needed, and no content is inlined that belongs in separate files. Not 5 because organization has minor gaps: redundant trigger sections ('Use this skill when' plus a near-empty 'Do not use this skill when') and boilerplate 'Instructions' section dilute the structure.

4 / 5

Total

12

/

20

Passed

Description

87%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 that explicitly states both what the skill does and when to use it, with concrete, domain-specific trigger phrases and minimal conflict risk. The only weakness is keyword coverage that omits a few natural terms (mTLS, sidecar, Kubernetes) users might say.

DimensionReasoningScore

Specificity

Names the domain ('service meshes with Istio or Linkerd') and several concrete capability areas ('traffic management, security, and observability'), matching the anchor for several specific actions with minor gaps. Not 5 because the list is not comprehensive (e.g., no mention of installation, progressive delivery, or policy authoring); not 3 because it goes beyond just 1-2 actions.

4 / 5

Completeness

Clearly answers both questions: what ('Design service meshes with Istio or Linkerd, including traffic management, security, and observability') and when ('Use when configuring service communication, mesh policies, or multi-cluster networking') with explicit concrete trigger phrases. This matches the top anchor exactly.

5 / 5

Trigger Term Quality

Good natural keyword coverage including 'service meshes', 'Istio', 'Linkerd', 'traffic management', 'mesh policies', and 'multi-cluster networking'. Not 5 because common user phrases like 'mTLS', 'sidecar', 'Kubernetes', or 'microservices' are missing; not 3 because coverage goes well beyond a single generic keyword.

4 / 5

Distinctiveness Conflict Risk

Clear niche with distinct triggers — Istio/Linkerd, mesh policies, and multi-cluster networking are unlikely to fire for unrelated skills. Not 4 because the named mesh technologies and mesh-specific triggers leave only minimal overlap risk with closely related Kubernetes skills.

5 / 5

Total

18

/

20

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

Validation for skill structure

No warnings or errors.

Repository

rmyndharis/antigravity-skills

Path

skills/service-mesh-expert/SKILL.md

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.