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

82%

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

82%Weight 40%Scale 1-5

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

A highly actionable, well-structured deployment runbook with executable commands throughout and a clear step sequence. The main gap is the absence of an explicit error-recovery feedback loop after the verification step.

Suggestions

Add an explicit feedback loop after the 'Verify Deployment' step: if any pod is not Running/Ready, instruct how to inspect logs (kubectl logs/describe) and re-run the failing helm upgrade with --wait.

Trim non-essential echo statements inside code blocks to improve token efficiency while keeping the actionable commands.

Consider moving the 'What This Deploys' component table near the top as a brief overview so the deployment scope is visible before the step-by-step procedure.

Dimension	Reasoning	Score
Conciseness	The body is lean and assumes Claude's competence (no padding about what Prometheus/Helm/Kind are), but includes some trimmable echo statements and one-line section intros that keep it just short of fully lean.	4 / 5
Actionability	Every step is given as complete, copy-paste-ready, executable bash (helm/kubectl commands with flags, namespaces, and kubeconfig), covering the full stack deployment.	5 / 5
Workflow Clarity	A clear 8-step sequence with implicit validation via helm --wait flags and an explicit 'Verify Deployment' step, but it lacks an explicit error-recovery feedback loop for failed installs.	4 / 5
Progressive Disclosure	Content is well-organized into clearly headed sections with one-level-deep external file references (examples/otel/*.yaml) clearly signaled, but it is a single monolithic file rather than an overview pointing to split detailed materials.	4 / 5
	Total	17 / 20 Passed

Description

82%Weight 40%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.

A well-constructed description that clearly states both the capability and explicit trigger conditions with concrete, natural terms. Its only weakness is that the action list is essentially a single deploy operation rather than several distinct capabilities.

Dimension	Reasoning	Score
Specificity	Names the domain and one concrete action ('Deploy the OpenTelemetry observability stack ... to a Kind cluster') with specific components, but does not list several distinct actions, so it matches the '1-2 concrete actions' anchor rather than the 'several specific actions' anchor.	3 / 5
Completeness	It explicitly answers both what ('Deploy the OpenTelemetry observability stack ... to a Kind cluster') and when ('Use when you need to set up monitoring, metrics collection, or observability infrastructure') with concrete trigger phrases.	5 / 5
Trigger Term Quality	The 'Use when you need to set up monitoring, metrics collection, or observability infrastructure' clause provides good natural keyword coverage, though a few common synonyms are missing.	4 / 5
Distinctiveness Conflict Risk	The narrow niche (OpenTelemetry stack on a Kind cluster for toolhive telemetry) with specific trigger terms gives it a clear, distinct scope with minimal conflict risk.	5 / 5
	Total	17 / 20 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: ccabad6

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