service-mesh-observability

Implement comprehensive observability for service meshes including distributed tracing, metrics, and visualization. Use when setting up mesh monitoring, debugging latency issues, or implementing SLOs for service communication.

Quality

82%

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

Quality

Content

65%

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

A content-rich, highly actionable skill packed with executable Istio/Linkerd/Jaeger/Kiali/OTel templates. Its weaknesses are token efficiency (concept explanations and generic boilerplate Claude doesn't need) and the absence of a sequenced, validated setup workflow.

Suggestions

Remove or compress the 'Three Pillars' ASCII diagram and 'Golden Signals' table — these are observability fundamentals Claude already knows — and drop the generic 'Instructions' boilerplate.

Add a numbered setup workflow (metrics → tracing → visualization → alerting) with explicit validation checkpoints, e.g. 'verify Prometheus targets are up' and 'confirm spans appear in Jaeger UI at :16686'.

Move the longer manifests (Jaeger deployment, Grafana dashboard JSON, OTel collector) into reference files under references/ and link to them one level deep to slim the main SKILL.md.

Dimension	Reasoning	Score
Conciseness	The bulk is concrete and valuable, but it explains concepts Claude already knows (the 'Three Pillars of Observability' ASCII diagram, the 'Golden Signals' table) and carries generic boilerplate ('Clarify goals... Apply relevant best practices... Provide actionable steps') that adds no domain value.	2 / 3
Actionability	Templates 1–7 are fully executable and copy-paste ready: real Kubernetes YAML manifests, PromQL queries, `linkerd viz` shell commands, a Grafana dashboard JSON, and OTel/Kiali configs.	3 / 3
Workflow Clarity	Templates are grouped logically but there is no end-to-end sequenced workflow (install metrics → tracing → visualization → alerting) and no validation checkpoints (e.g., confirm Prometheus is scraping, verify traces appear in Jaeger); the 'Instructions' bullets are generic, not a real task sequence.	2 / 3
Progressive Disclosure	Well organized into labeled sections with no nested references, but it is a monolithic ~250-line file with seven templates that could be split into one-level-deep reference files; no bundle files exist to offload detail.	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: it states concrete capabilities and pairs them with an explicit, natural 'Use when...' trigger clause covering the core mesh-observability scenarios. It is concise, third-person, and clearly scoped to service meshes.

Dimension	Reasoning	Score
Specificity	Lists multiple specific concrete actions — 'distributed tracing, metrics, and visualization' — beyond naming the service-mesh domain, matching the 'lists multiple specific concrete actions' anchor.	3 / 3
Completeness	Clearly answers both what ('Implement comprehensive observability for service meshes including distributed tracing, metrics, and visualization') and when via an explicit 'Use when...' clause, matching the top anchor.	3 / 3
Trigger Term Quality	Natural trigger phrases users would say — 'setting up mesh monitoring', 'debugging latency issues', 'implementing SLOs', 'distributed tracing' — give good coverage across the domain.	3 / 3
Distinctiveness Conflict Risk	Occupies a clear niche (service-mesh observability) with distinct triggers ('service meshes', 'mesh monitoring', 'SLOs for service communication') unlikely to fire for unrelated skills.	3 / 3
	Total	12 / 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-observability/SKILL.md
Commit: e63f7dd

Reviewed: about 24 hours 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.