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

—

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Passed

No known issues

Quality

Content

57%

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 and uses progressive disclosure effectively, but it leans on conceptual explanations Claude already knows and defers all executable content to the reference without an explicit, validated workflow sequence.

Suggestions

Move or cut the 'Three Pillars of Observability' ASCII diagram and Golden Signals explanations — Claude already knows these concepts; keep only mesh-specific thresholds and signal mappings.

Add a short, sequenced setup workflow (install telemetry → configure sampling → deploy collector → verify scrape/ingest) with an explicit validation checkpoint so the body is actionable without reading the reference.

Inline at least one copy-paste-ready snippet (e.g., a minimal Istio Telemetry CR or a single PromQL check) so the body is executable on its own, not only by referral to references/details.md.

Dimension	Reasoning	Score
Conciseness	Mostly efficient, but the ASCII 'Three Pillars of Observability' box and Golden Signals table restate concepts Claude already knows (what metrics, traces, and logs are); tightening would remove padded explanation. Not 3 because of this conceptual redundancy; not 1 because the bulk is concrete and token-efficient.	2 / 3
Actionability	The body offers thresholds, sample-rate guidance, and Do's/Don'ts but no executable code or commands itself — concrete templates are deferred to references/details.md. Not 3 because the evaluated body lacks copy-paste-ready code; not 1 because the guidance is specific rather than purely abstract.	2 / 3
Workflow Clarity	'When to Use This Skill' is a trigger list, not a sequenced workflow, and there are no validation checkpoints for the multi-step mesh-setup process. Not 1 because some structure exists; not 3 because no explicit sequence or validate/fix/retry loops are present.	2 / 3
Progressive Disclosure	The body is a concise overview that clearly signals a one-level-deep reference ('Full template library and detailed worked examples live in references/details.md'), and that file exists with the concrete templates — matching the level-3 anchor for well-signaled one-level references.	3 / 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.

The description is specific, uses third person, and clearly answers both what the skill does and when to invoke it with natural trigger terms. It occupies a distinct niche around service mesh observability.

Dimension	Reasoning	Score
Specificity	Names the domain and multiple concrete actions — 'distributed tracing, metrics, and visualization' — matching the 'lists multiple specific concrete actions' anchor rather than the partial level-2 example.	3 / 3
Completeness	Explicitly answers both what ('Implement comprehensive observability for service meshes including distributed tracing, metrics, and visualization') and when (explicit 'Use when...' trigger), matching the level-3 anchor; not below because neither half is missing or merely implied.	3 / 3
Trigger Term Quality	The 'Use when setting up mesh monitoring, debugging latency issues, or implementing SLOs for service communication' clause provides natural terms users would say; not below 3 because coverage is broad and not jargon-only.	3 / 3
Distinctiveness Conflict Risk	Scoped to 'service meshes' with distinct mesh-specific triggers (mesh monitoring, SLOs for service communication), giving a clear niche unlikely to conflict with other 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: wshobson/agents
Commit: 5cc2549

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