CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

otel-profiles

OpenTelemetry profiles signal and the eBPF profiler (otelcol-ebpf-profiler, `profiling` receiver). Use when setting up continuous profiling with OpenTelemetry, deploying the eBPF profiler on Linux hosts, Docker, or Kubernetes (DaemonSet, kind, k3d), building a profiles pipeline, sending OTLP profiles to Pyroscope, Grafana Cloud Profiles, or another backend, getting flame graphs from OTel, enabling off-CPU profiling, or debugging profiler errors about tracefs, PID namespaces, missing pods, or the service.profilesSupport feature gate. Not for SDK tracing or metrics setup.

Quality

97%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

Quality

Content

92%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 high-quality operational skill: executable commands and configs, a validated workflow with explicit verification steps, and clean one-level progressive disclosure. The only weakness is the dated version-matrix section with its evidence link list, which is useful for pinning but could be tightened or pushed to a reference.

DimensionReasoningScore

Conciseness

The body is dense and operational with almost no explanation of concepts Claude already knows (e.g., 'built FROM scratch: no shell, so debug from logs, not exec' is non-obvious operational detail), but the version-matrix section carries dated, version-pinned rows plus a five-link evidence paragraph ('Evidence: Docker Hub tags... v0.164.0 changelog') that could be trimmed. It is isolated in a dedicated version section rather than scattered, which keeps this above the midpoint but not fully lean.

4 / 5

Actionability

Fully executable, copy-paste-ready guidance: a complete `docker run` command with mounts and the `--feature-gates=+service.profilesSupport` flag, a full config YAML, the `validate --config=<file>` check, expected startup lines ('eBPF tracer loaded', 'Everything is ready'), and concrete debug-verification output ('"resource profiles": N, "sample records": M'). These cover the common host/Docker case end to end.

5 / 5

Workflow Clarity

The 5-step Workflow is clearly sequenced (pick image/pin, pick environment, wire pipeline, export and verify, troubleshoot) with explicit validation checkpoints: 'Run `validate --config=<file> --feature-gates=+service.profilesSupport`... it catches wrong keys', and a verify step that interprets failure ('no lines or zero counts mean the receiver is not producing'). Error recovery is routed to exact-error-string troubleshooting, matching the top anchor.

5 / 5

Progressive Disclosure

SKILL.md is a concise overview that points to five one-level-deep references (receiver.md, kubernetes.md, nested-containers.md, backends.md, troubleshooting.md), each referenced at the point of need with what it covers ('DaemonSet, RBAC, Kubernetes metadata, memory sizing'). All five files exist in references/ and none reference each other, so navigation is flat and well-signaled.

5 / 5

Total

19

/

20

Passed

Description

100%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.

An exemplary description: concrete capabilities, explicit 'Use when' triggers with natural synonyms and product names, third-person voice, and a negative boundary that sharply limits conflict with adjacent OTel skills. No changes needed.

DimensionReasoningScore

Specificity

It names the concrete artifacts ('otelcol-ebpf-profiler, `profiling` receiver') and lists multiple specific actions: 'setting up continuous profiling', 'deploying the eBPF profiler on Linux hosts, Docker, or Kubernetes (DaemonSet, kind, k3d)', 'building a profiles pipeline', 'sending OTLP profiles to Pyroscope, Grafana Cloud Profiles', 'enabling off-CPU profiling', 'debugging profiler errors about tracefs, PID namespaces'. Coverage is comprehensive and in third person, matching the top anchor rather than the 'several specific actions; minor gaps' level below.

5 / 5

Completeness

It explicitly answers both questions: the 'what' in the first sentence ('OpenTelemetry profiles signal and the eBPF profiler (otelcol-ebpf-profiler, `profiling` receiver)') and the 'when' via a full 'Use when...' clause with concrete triggers, plus a negative boundary ('Not for SDK tracing or metrics setup'). This mirrors the anchor-5 example structure exactly.

5 / 5

Trigger Term Quality

Natural user phrasing is comprehensively covered with synonyms and product names: 'continuous profiling', 'eBPF profiler', 'flame graphs', 'off-CPU profiling', 'Pyroscope', 'Grafana Cloud Profiles', 'DaemonSet', 'kind', 'k3d', 'tracefs', 'PID namespaces', 'service.profilesSupport'. A user needing this skill would naturally say several of these; nothing obvious is missing.

5 / 5

Distinctiveness Conflict Risk

It occupies a clear niche (the OTel profiles signal specifically) with distinct triggers (Pyroscope, flame graphs, service.profilesSupport) and an explicit exclusion ('Not for SDK tracing or metrics setup') that prevents overlap with generic tracing/metrics skills, giving minimal conflict risk.

5 / 5

Total

20

/

20

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

Validation for skill structure

No warnings or errors.

Repository

ollygarden/opentelemetry-agent-skills

Path

skills/otel-profiles/SKILL.md

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.