deploy-otel

Deploy the OpenTelemetry observability stack (Prometheus, Grafana, OTEL Collector) to a Kind cluster for testing toolhive telemetry. Use when you need to set up monitoring, metrics collection, or observability infrastructure.

Quality

85%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Low

Low-risk findings worth noting

Quality

Content

80%

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

A well-organized, executable deployment runbook with concrete commands and a prerequisite/verification gate, but it depends on external values files that are not bundled and omits per-step error-recovery feedback loops for the batched helm installs. Closing those two gaps would lift it to a top score.

Suggestions

Bundle the referenced values files (examples/otel/prometheus-stack-values.yaml, tempo-values.yaml, otel-values.yaml) inside the skill, or inline their key contents, so the helm -f references resolve within the skill bundle.

Add a per-step feedback loop after each helm upgrade --wait (e.g., "if the release does not become ready, run `kubectl describe pod` / `kubectl logs` in the monitoring namespace, then re-run the upgrade") to give explicit error-recovery guidance for the batched installs.

Replace or supplement the `task kind-destroy` cleanup entry with the already-provided manual `kind delete cluster` path as the primary instruction, since the Taskfile target is not part of the skill bundle.

Dimension	Reasoning	Score
Conciseness	The body is lean and almost entirely executable bash with sectioned structure; it avoids explaining concepts Claude already knows and the "What This Deploys" table carries useful configuration detail rather than basic background, so every token earns its place.	3 / 3
Actionability	Each step gives fully-specified, copy-paste-ready commands (helm/kubectl/kind with repos, namespaces, kubeconfig, --wait/--timeout flags) rather than pseudocode or vague direction, matching the level-3 executable anchor.	3 / 3
Workflow Clarity	There is a clear 8-step sequence with an explicit prerequisite gate (step 1 exits on missing tools) and a final pod verification (step 7), but it lacks step-level feedback loops for error recovery when a batched helm install fails to become ready, so it does not reach the level-3 anchor.	2 / 3
Progressive Disclosure	The body is well-sectioned, but it references one-level values files ("-f examples/otel/prometheus-stack-values.yaml", "tempo-values.yaml", "otel-values.yaml") that are not present in the skill bundle (no references/scripts/assets/examples directories), so the references are signaled but point to missing files.	2 / 3
	Total	10 / 12 Passed

Description

90%

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, concrete description with an explicit "Use when" trigger and natural keywords; its only weakness is that it frames a single deployment action rather than enumerating multiple discrete capabilities. Voice is correctly third person with no over-claims.

Dimension	Reasoning	Score
Specificity	It names the domain and concrete deployment target ("Deploy the OpenTelemetry observability stack (Prometheus, Grafana, OTEL Collector) to a Kind cluster for testing toolhive telemetry") but describes essentially a single action rather than enumerating multiple distinct concrete actions, so it falls short of the level-3 "lists multiple specific concrete actions" anchor.	2 / 3
Completeness	It clearly answers both what (deploy the OTEL stack of named components to a Kind cluster) and when ("Use when you need to set up monitoring, metrics collection, or observability infrastructure"), with an explicit trigger clause.	3 / 3
Trigger Term Quality	"Use when you need to set up monitoring, metrics collection, or observability infrastructure" provides good coverage of natural terms a user would actually say, matching the level-3 anchor.	3 / 3
Distinctiveness Conflict Risk	The OTEL-on-Kind-for-toolhive niche is specific with distinct monitoring/observability triggers, making it unlikely to fire for an unrelated skill.	3 / 3
	Total	11 / 12 Passed

Validation

93%

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 — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
allowed_tools_field	'allowed-tools' contains unusual tool name(s)	Warning

	Total	15 / 16 Passed

Repository: stacklok/toolhive
Path: .claude/skills/deploy-otel/SKILL.md
Commit: cd373ec

Reviewed: 2 days 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.