Conciseness

The body is a lean rule-book with no concept explanations Claude already knows ('Most failures come down to a handful of Coralogix-specific defaults that vanilla OpenTelemetry docs don't cover'), but a few inlined rules run at reference depth — e.g., the Windows 'coralogixrepo/opentelemetry-collector-contrib-windows:0.92.0' image-pin details and the 'spanNameReplacePattern' '$$1'/'$$2' escaping rule. These could be trimmed or pushed into their reference files.

Actionability

Fully executable guidance throughout: exact commands ('kubectl exec -n <namespace> <collector-pod> -- wget -qO- http://localhost:8888/metrics | grep -E 'otelcol_exporter_...''), exact expected outcomes ('expect 400/401, NOT a TLS or connection error'), literal config keys ('url_sanitizer', 'sanitize_span_name', 'allow_all_keys: true'), and exact version thresholds ('bump the image to ≥ v0.130').

Workflow Clarity

The triage workflow is a 6-step ordered sequence with explicit validation checkpoints and interpretation of each outcome ('Success: otelcol_exporter_sent_* > 0', 'A StatusUnauthenticated confirms a key/region mismatch', 'context deadline exceeded suggests egress/proxy'), and pipeline wiring is deferred until after the earlier checks pass. Other workflows are brief but appropriately delegate to their reference files.

Progressive Disclosure

The 'When to Use This Skill' table maps every use case to a real reference file (all 18 cited files verified present in references/), references are one level deep and clearly signaled, and the body keeps only high-signal rules and routing. Navigation is straightforward.

Specificity

Lists multiple concrete actions and specifics — 'deployment, configuration, and troubleshooting for Coralogix users', the coralogix exporter bracket syntax, 'agent → cluster-collector → gateway topology', and every deployment mode from Helm chart to standalone installer. Comprehensive coverage across exporter, pipeline, topology, and platform domains with no vague filler.

Completeness

Explicitly answers both what ('deployment, configuration, and troubleshooting for Coralogix users' with enumerated capabilities) and when ('Use when writing or debugging collector configs'), and adds negative boundary guidance ('Not for OTTL authoring... use the opentelemetry-ottl skill').

Trigger Term Quality

Comprehensive natural terms users would actually say: 'OpenTelemetry Collector', 'coralogix exporter', 'CORALOGIX_PRIVATE_KEY', 'spanmetrics', 'tail_sampling', 'k8sattributes', 'url_sanitizer', 'daemonset', 'sidecar', 'gateway', 'cardinality', plus platform names like 'EKS Fargate'. Includes component-level and config-key-level synonyms.

Distinctiveness Conflict Risk

Clear niche — the Coralogix-flavored collector — with explicit exclusions delegating OTTL authoring and OpAMP/Fleet Manager internals to other skills, minimizing the chance of triggering for the wrong skill.