CtrlK
BlogDocsLog inGet started
Tessl Logo

service-mesh-expert

Expert service mesh architect specializing in Istio, Linkerd, and cloud-native networking patterns. Masters traffic management, security policies, observability integration, and multi-cluster mesh con

53

Quality

58%

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

42%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 well-structured into sections but is generic and non-actionable: it lists capability topics and a high-level workflow without any concrete commands, YAML examples, or validation steps, and provides no reference material for a domain that warrants it.

Suggestions

Replace generic instructions ('Apply relevant best practices') with concrete, executable guidance such as sample Istio VirtualService/DestinationRule YAML and exact istioctl/kubectl commands for the common cases.

Add validation checkpoints to the workflow (e.g., verify mTLS mode with istioctl authn tlsCheck, confirm policy enforcement before proceeding to traffic shifts) with fix-and-retry feedback loops for batch/destructive operations like policy enforcement and canary rollouts.

Add reference files (e.g., references/traffic-management.md, references/mtls.md) for detailed patterns and link to them one level deep, removing the tautological 'Do not use this skill when' section to save tokens.

DimensionReasoningScore

Conciseness

Largely list-based without explaining concepts Claude already knows, but contains generic boilerplate ('Clarify goals, constraints, and required inputs', 'Apply relevant best practices and validate outcomes') and a near-tautological 'Do not use this skill when' section that add tokens without domain value.

3 / 5

Actionability

Only names topics at a high level ('Design mesh topology and traffic policies', 'Implement security policies (mTLS, AuthorizationPolicy)') with no concrete commands, YAML, or executable examples; it describes rather than instructs.

2 / 5

Workflow Clarity

A 7-step workflow is listed but has no validation checkpoints, concrete commands, or error-recovery feedback loops; service mesh policy/traffic operations warrant validation, capping this at 3.

3 / 5

Progressive Disclosure

Sections are reasonably organized but the skill covers a broad complex domain that would benefit from reference material, and none is provided or referenced; content that could be split into references is simply absent.

3 / 5

Total

11

/

20

Passed

Description

75%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 is strong: domain-specific, third-person, with explicit 'what' and 'when' guidance and natural trigger terms. Its main weakness is that it is cut off mid-word ('mesh con'), truncating the capability list and slightly undermining completeness.

DimensionReasoningScore

Specificity

Names the domain (Istio, Linkerd, service mesh) and several concrete action areas ('traffic management, security policies, observability integration, and multi-cluster mesh con'), though the description is truncated mid-word, slightly weakening the action list — not a 5 due to incomplete coverage from truncation.

4 / 5

Completeness

Provides a clear 'what' (architect specializing in... masters...) and an explicit 'when' trigger ('Use PROACTIVELY for service mesh architecture, zero-trust networking, or microservices communication patterns'), but the truncated 'what' keeps it from a 5.

4 / 5

Trigger Term Quality

Includes natural domain terms like 'service mesh', 'Istio', 'Linkerd', 'zero-trust networking', and 'microservices communication patterns' that users would plausibly say; missing some synonyms and natural phrasings, so not a 5.

4 / 5

Distinctiveness Conflict Risk

A clearly distinct niche (service mesh / Istio / Linkerd) with domain-specific triggers and minimal overlap risk with adjacent Kubernetes or networking skills, though slight overlap risk remains.

4 / 5

Total

16

/

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.

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.