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

Quality

62%

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 ./skills/service-mesh-expert/SKILL.md

Quality

Content

42%

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

The content is well-structured and domain-aware but largely descriptive: it lacks executable commands or examples and has generic boilerplate filler. Its strongest dimension is organization; its weakest is actionability.

Suggestions

Replace the generic Instructions with service-mesh-specific, executable guidance (e.g. sample VirtualService/Gateway YAML, istioctl verify-install commands).

Add validation checkpoints to the Workflow (e.g. "Run `istioctl analyze` and only proceed on a clean report") to support the risky mTLS/policy steps.

Drop the boilerplate "Do not use this skill when" and the description-restating opening paragraph to remove non-earning tokens.

Dimension	Reasoning	Score
Conciseness	The body is mostly lean but includes redundant and generic filler: the opening paragraph restates the frontmatter description, and the Instructions ("Clarify goals, constraints... Apply relevant best practices and validate outcomes") and "Do not use this skill when" sections are boilerplate that could be tightened; not level 3 because tokens are spent on non-specific content Claude already handles.	2 / 3
Actionability	The body describes capabilities and steps ("Implement security policies (mTLS, AuthorizationPolicy)", "Configure observability") without any executable YAML, commands, or copy-paste examples, matching the anchor that describes rather than instructs.	1 / 3
Workflow Clarity	Seven steps are listed in a clear sequence, but there are no validation checkpoints or feedback loops for risky mTLS/policy changes, so per the rubric workflow clarity is capped at 2; not level 1 because the sequence is explicit.	2 / 3
Progressive Disclosure	It is a compact single-file skill with clear, well-organized sections and no need for external references, satisfying the rubric's allowance for simple skills to score 3 on well-organized structure alone.	3 / 3
	Total	8 / 12 Passed

Description

82%

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 distinctive, capability-rich description with good natural trigger terms, weakened by a missing explicit "Use when" clause and a truncated final phrase. Fixing the truncation and adding trigger guidance would bring it to full marks.

Suggestions

Complete the truncated description ("multi-cluster mesh con" -> "multi-cluster mesh configurations") so the sentence is grammatical.

Add an explicit trigger clause, e.g. "Use when designing service mesh architecture, zero-trust networking, or microservices communication patterns in Kubernetes."

Dimension	Reasoning	Score
Specificity	The description lists multiple concrete capability areas ("traffic management, security policies, observability integration, and multi-cluster mesh con"), matching the anchor for multiple specific concrete actions.	3 / 3
Completeness	It answers "what" clearly but provides no explicit "Use when..." trigger clause, and the text is truncated mid-word ("mesh con"), so the when guidance is missing/incomplete; not level 3 which requires explicit triggers, but above 1 since the what is concrete.	2 / 3
Trigger Term Quality	It surfaces natural product and domain terms users would actually say ("Istio", "Linkerd", "service mesh", "cloud-native networking"), giving good coverage of likely trigger language.	3 / 3
Distinctiveness Conflict Risk	The Istio/Linkerd/service-mesh niche is specific with distinct triggers and is unlikely to fire for unrelated skills.	3 / 3
	Total	11 / 12 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: rmyndharis/antigravity-skills
Path: skills/service-mesh-expert/SKILL.md
Commit: e63f7dd

Reviewed: 1 day 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.