service-mesh-observability

Complete guide to observability patterns for Istio, Linkerd, and service mesh deployments.

Quality

38%

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-observability/SKILL.md

Quality

Content

39%Scale 1-5

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

This skill provides a comprehensive collection of service mesh observability templates with concrete, executable YAML and PromQL examples, which is its primary strength. However, it suffers from being a monolithic reference dump with no clear workflow sequencing, missing validation steps, excessive conceptual content Claude doesn't need, and a broken reference to a non-existent bundle file. It reads more like a reference catalog than an actionable skill.

Suggestions

Add a clear end-to-end workflow with numbered steps, dependencies between templates, and explicit validation checkpoints (e.g., 'Verify Prometheus is scraping: kubectl port-forward ... && curl localhost:9090/targets').

Remove or drastically reduce conceptual content like the Three Pillars diagram and Golden Signals table—Claude already knows these concepts.

Split the large template blocks into separate bundle files (e.g., `templates/istio-prometheus.yaml`, `templates/jaeger.yaml`) and reference them from SKILL.md with brief descriptions of when to use each.

Either create the referenced `resources/implementation-playbook.md` bundle file or remove the dead reference from the Instructions section.

Dimension	Reasoning	Score
Conciseness	The skill is heavily padded with content Claude already knows (three pillars of observability, golden signals table, basic do's/don'ts). The ASCII diagram and conceptual explanations add little value. The templates are extensive but many could be trimmed or referenced externally rather than inlined.	2 / 5
Actionability	The templates provide concrete, copy-paste ready YAML manifests, PromQL queries, and CLI commands that are directly executable. Minor gaps exist—there's no clear guidance on sequencing these templates or adapting them to specific scenarios, and the 'Instructions' section is extremely vague ('Clarify goals, constraints, and required inputs').	4 / 5
Workflow Clarity	There is no clear sequenced workflow for setting up observability end-to-end. Templates are presented as isolated blocks without ordering, dependencies, or validation checkpoints. There's no guidance on verifying that Prometheus is scraping correctly, that traces are flowing, or how to diagnose failures between steps.	2 / 5
Progressive Disclosure	The skill references `resources/implementation-playbook.md` but no bundle files exist, making this a dead reference. Nearly all content is inlined in a single monolithic file (~250+ lines of templates) that would benefit greatly from being split into separate files per template or tool. The structure is flat with no clear navigation hierarchy.	2 / 5
	Total	10 / 20 Passed

Description

36%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 identifies a specific domain (service mesh observability) and names key technologies, but fails to describe any concrete actions or capabilities. It lacks a 'Use when...' clause entirely, making it difficult for Claude to know when to select this skill. The phrase 'complete guide' is vague filler that doesn't communicate what the skill actually does.

Suggestions

Add concrete actions describing what the skill does, e.g., 'Configures distributed tracing, sets up metrics collection with Prometheus/Grafana, and implements logging pipelines for service mesh deployments.'

Add an explicit 'Use when...' clause with trigger terms, e.g., 'Use when the user asks about service mesh monitoring, distributed tracing, Istio/Linkerd observability, or setting up metrics dashboards.'

Replace 'Complete guide' with specific capabilities to improve both specificity and distinctiveness.

Dimension	Reasoning	Score
Specificity	Names the domain (observability patterns for service meshes) and specific technologies (Istio, Linkerd), but 'complete guide' is vague and no concrete actions are listed—no mention of what it actually does (e.g., configure dashboards, set up tracing, analyze metrics).	2 / 5
Completeness	Provides a vague 'what' ('complete guide to observability patterns') but has no 'when' clause at all. There is no explicit trigger guidance for when Claude should select this skill.	2 / 5
Trigger Term Quality	Includes relevant keywords like 'Istio', 'Linkerd', 'service mesh', and 'observability', which users might naturally mention. However, it misses common synonyms and related terms like 'tracing', 'metrics', 'logging', 'Prometheus', 'Grafana', 'Jaeger', 'distributed tracing', or 'monitoring'.	3 / 5
Distinctiveness Conflict Risk	The combination of 'observability' with specific mesh technologies (Istio, Linkerd) provides some distinctiveness, but 'observability patterns' is broad enough to overlap with general monitoring, logging, or Kubernetes observability skills.	3 / 5
	Total	10 / 20 Passed

Validation

90%

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 — 10 / 11 Passed

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	10 / 11 Passed

Repository: administrakt0r/AI-Agents-Safe-Coding-Skills
Path: skills/service-mesh-observability/SKILL.md
Commit: 57c135b

Reviewed: 20 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.