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.
71
57%
Does it follow best practices?
Impact
95%
1.39xAverage score across 3 eval scenarios
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./tests/ext_conformance/artifacts/agents-wshobson/cloud-infrastructure/skills/service-mesh-observability/SKILL.mdQuality
Discovery
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.
This is a strong skill description that clearly defines its scope around service mesh observability, lists concrete capabilities, and includes an explicit 'Use when' clause with natural trigger terms. It follows third-person voice correctly and is concise without being vague. The description effectively differentiates itself from general monitoring or logging skills through its specific focus on service mesh contexts.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'distributed tracing, metrics, and visualization' as capabilities, and 'setting up mesh monitoring, debugging latency issues, implementing SLOs for service communication' as use cases. These are concrete, actionable items. | 3 / 3 |
Completeness | Clearly answers both 'what' (implement observability for service meshes including distributed tracing, metrics, visualization) and 'when' (explicit 'Use when' clause covering mesh monitoring setup, debugging latency, implementing SLOs). | 3 / 3 |
Trigger Term Quality | Includes strong natural keywords users would say: 'service mesh', 'distributed tracing', 'metrics', 'monitoring', 'latency issues', 'SLOs', 'service communication', 'observability', 'visualization'. These cover the domain well with terms practitioners naturally use. | 3 / 3 |
Distinctiveness Conflict Risk | The combination of 'service mesh' + 'observability' creates a clear niche. Terms like 'distributed tracing', 'SLOs for service communication', and 'mesh monitoring' are highly specific and unlikely to conflict with general monitoring or generic observability skills. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
14%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill reads more like a reference dump of YAML/JSON configurations than an actionable guide. It lacks workflow sequencing, validation checkpoints, and progressive disclosure—everything is inlined in one massive file with no clear order of operations. The content explains concepts Claude already knows (three pillars, golden signals) while missing critical guidance on how to actually set up, verify, and troubleshoot a mesh observability stack.
Suggestions
Add a clear sequential workflow: 'Step 1: Install Prometheus (verify with kubectl get pods), Step 2: Configure tracing (verify with test trace), Step 3: Set up dashboards' with explicit validation at each step.
Move large configuration blocks (Grafana dashboard JSON, alerting rules, OTel collector config) into separate referenced files like TEMPLATES.md or ALERTING.md to reduce the main skill to an overview.
Remove the 'Core Concepts' section entirely—Claude knows the three pillars of observability and golden signals. Replace with a brief decision table: 'Use Jaeger for X, Kiali for Y, Linkerd viz for Z.'
Add troubleshooting guidance: what to check when traces aren't appearing, how to verify Prometheus is scraping mesh metrics, common misconfigurations and their symptoms.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is extremely verbose at ~300+ lines, includes conceptual explanations Claude already knows (three pillars of observability, golden signals table), ASCII art diagrams, and extensive boilerplate YAML that could be referenced externally. The Grafana dashboard JSON alone is massive and adds little instructional value inline. | 1 / 3 |
Actionability | The templates contain real, deployable YAML and executable PromQL queries, which is good. However, much of it is boilerplate configuration rather than targeted guidance on how to use these tools to solve specific problems. The Linkerd CLI commands are actionable, but the skill lacks guidance on how to interpret results or what to do when things go wrong. | 2 / 3 |
Workflow Clarity | There is no clear sequential workflow for setting up observability. Templates are presented as disconnected blocks without ordering, dependencies, or validation steps. There's no guidance like 'first install X, verify with Y, then configure Z.' For a complex multi-component setup involving Prometheus, Jaeger, Grafana, and Kiali, the absence of sequencing and validation checkpoints is a significant gap. | 1 / 3 |
Progressive Disclosure | The entire skill is a monolithic wall of configuration templates with no content split into separate files. The Grafana dashboard JSON, alerting rules, and individual tool configurations should be referenced externally. The Resources section links to external docs but doesn't organize the skill's own content across files. | 1 / 3 |
Total | 5 / 12 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.
Validation — 11 / 11 Passed
Validation for skill structure
No warnings or errors.
- Repository
- Dicklesworthstone/pi_agent_rust
- Commit
47823e3
- 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.