CtrlK
BlogDocsLog inGet started
Tessl Logo

opentelemetry-collector

OpenTelemetry Collector deployment, configuration, and troubleshooting for Coralogix users. Use when writing or debugging collector configs — the `coralogix` exporter (`domain:` vs `endpoint:`, `${env:CORALOGIX_PRIVATE_KEY}` bracket syntax, `coralogix/resource_catalog` variant), the universal processor chain, agent → cluster-collector → gateway topology, spanmetrics/tail_sampling/k8sattributes placement, component stability checks, data-safety/redaction routing including `url_sanitizer`, `sanitize_span_name`, `allow_all_keys`, and before/after validation for broad sanitizer over-sanitization, spanmetrics cardinality protection, and Coralogix-specific presets. Covers the `otel-integration` Helm chart (EKS/GKE/AKS/ OpenShift, GKE Autopilot Warden, EKS Fargate), ECS EC2 daemonset, ECS Fargate sidecar, Linux/Windows/macOS standalone, Docker, and the universal installer. Not for OTTL authoring (use the `opentelemetry-ottl` skill) or OpAMP supervisor/Fleet Manager internals beyond the config-precedence callout.

92

1.10x
Quality

96%

Does it follow best practices?

Impact

92%

1.10x

Average score across 127 eval scenarios

SecuritybySnyk

Low

Low-risk findings worth noting

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

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 well-architected skill body: actionable commands, a validated multi-step triage workflow, and clean progressive disclosure to a real reference bundle. Only minor conciseness tightening is warranted in the rules section.

Suggestions

Tighten the longest bold 'High-Signal Answer Rule' sentences (e.g. the tail_sampling/spanmetrics double-counting and redaction rules) into shorter imperative clauses with the fix detail kept inline.

The 'When to Use' table and 'High-Signal Answer Rules' overlap on a few items (e.g. resource_catalog, k8sattributes); consider cross-linking rather than restating to save tokens.

DimensionReasoningScore

Conciseness

Dense and domain-specific, assuming Claude's OTel knowledge rather than re-explaining basics, but several bold 'High-Signal Answer Rule' sentences run long and could be trimmed without losing the corrective detail.

4 / 5

Actionability

Provides copy-paste-ready commands (`kubectl exec … wget …/metrics`, `nslookup`, `curl -v`) and exact config values (`domain:` bare hostname, `${env:CORALOGIX_PRIVATE_KEY}` bracket syntax, `memory_limiter` first / `batch` last) covering the common cases.

5 / 5

Workflow Clarity

The 'no data reaching Coralogix' triage is a clearly sequenced 6-step process with explicit validation checkpoints ('otelcol_exporter_sent_* > 0', 'expect 400/401, NOT a TLS error') and a feedback loop via debug-logging status-code interpretation.

5 / 5

Progressive Disclosure

SKILL.md is a concise overview whose 'When to Use' table maps use cases to 17 real, one-level-deep reference files (all verified present in references/), with clearly signaled markdown links and no nested indirection.

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 trigger, rich natural keywords, and a sharp boundary against adjacent skills. No meaningful gaps for the description rubric.

DimensionReasoningScore

Specificity

Lists many concrete actions — exporter config (`domain:` vs `endpoint:`, bracket env syntax, `resource_catalog` variant), universal processor chain, topology placement, component stability checks, redaction routing, and cardinality protection — giving comprehensive coverage rather than vague verbs.

5 / 5

Completeness

Explicitly states both what it does ('deployment, configuration, and troubleshooting … for Coralogix users') and when to use it ('Use when writing or debugging collector configs'), plus a 'Not for …' boundary clause.

5 / 5

Trigger Term Quality

Packs in natural terms and synonyms users actually say — 'OpenTelemetry Collector', 'coralogix exporter', 'otel-integration', 'CORALOGIX_PRIVATE_KEY', 'tail_sampling', 'spanmetrics', 'ECS Fargate', 'daemonset', 'sidecar' — with broad variation.

5 / 5

Distinctiveness Conflict Risk

Occupies a clear Coralogix-flavored niche and explicitly delegates OTTL to the `opentelemetry-ottl` skill and OpAMP/Fleet Manager internals elsewhere, minimizing overlap with sibling skills.

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.