CtrlK
BlogDocsLog inGet started
Tessl Logo

opentelemetry-instrumentation

Instruments Java, Python, Node.js, .NET, and Go applications with OpenTelemetry SDKs to send traces, metrics, and logs to Coralogix. Use for SDK-side OTel setup, OTLP exporter env vars, Coralogix resource attributes, APM transaction samplers, Kubernetes Operator injection, or debugging missing traces, metrics, logs, or no telemetry from an application. Not for OTel Collector config (use opentelemetry-collector), OTTL authoring (use opentelemetry-ottl), eBPF instrumentation, or Lambda layers.

92

1.10x
Quality

93%

Does it follow best practices?

Impact

92%

1.10x

Average score across 127 eval scenarios

SecuritybySnyk

Passed

No findings from the security scan

The canonical home for this skill is coralogix/opentelemetry-skills

SKILL.md
Quality
Evals
Security

Quality

Content

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

The body is a well-structured index that routes to verified references and packs high-value concrete gotchas without padding. It is slightly held back by deferring most executable code to references and by validation steps being prescribed for generated answers rather than the skill's own workflow.

Suggestions

Add a short inline runnable snippet for one representative language in the body so the skill is fully copy-paste-ready without loading a reference.

Make the debugging workflow's validate→fix→retry loop explicit in the Workflow section rather than only prescribing validation steps for generated answers.

DimensionReasoningScore

Conciseness

Lean overview that assumes Claude's competence — a routing table, terse rules, and a deliberately short gotchas list ('Keep this list short'), with no padding explaining OTel basics.

5 / 5

Actionability

Provides concrete config identifiers and copy-paste literal values (env var names, 'Authorization=Bearer%20<KEY>', 'WithCardinalityLimit(0)'), but most full executable per-language code is deferred to references rather than inline.

4 / 5

Workflow Clarity

Three explicit sequenced paths (new setup, code review, debugging) with a stated load order and an escalation rule, but validation checkpoints are framed as something to include in answers rather than an explicit validate→fix→retry loop in the skill's own workflow.

4 / 5

Progressive Disclosure

Clear overview with a use-case routing table and a stated one-level-deep load order; all nine referenced files exist on disk and are well-signaled for navigation.

5 / 5

Total

18

/

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.

The description is exemplary: concrete multi-language actions, explicit trigger phrases for both what and when, and clear negative boundaries against sibling skills. It uses third person throughout with no fluff.

DimensionReasoningScore

Specificity

Lists multiple concrete actions across five named languages — instrumenting, sending traces/metrics/logs, env vars, resource attributes, transaction samplers, K8s operator injection, and debugging — with no coverage gaps.

5 / 5

Completeness

Explicitly answers both 'what' (instruments apps to send telemetry to Coralogix) and 'when' (concrete 'Use for...' trigger list), plus a negative boundary clause.

5 / 5

Trigger Term Quality

Comprehensive natural trigger phrases users would say ('debugging missing traces', 'no telemetry', 'OTLP exporter env vars', 'Kubernetes Operator injection') with synonyms for each signal.

5 / 5

Distinctiveness Conflict Risk

Clear SDK-side OTel niche with explicit 'Not for...' boundaries redirecting to sibling skills (collector, OTTL, eBPF, Lambda), minimizing wrong-skill triggering.

5 / 5

Total

20

/

20

Passed

Validation

93%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

metadata_field

'metadata' should map string keys to string values

Warning

Total

15

/

16

Passed

Repository
coralogix/cx-skills
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.