CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

cx-data-pipeline

Use this skill when the user asks to "set up parsing", "create parsing rule", "extract fields from logs", "regex extraction", "log parsing", "enrich logs", "add context to logs", "custom enrichment table", "lookup table", "geo enrichment", "create metric from logs", "events to metrics", "convert logs to metrics", "generate metrics from events", "recording rule", "precomputed metrics", "PromQL recording", "configure data pipeline", "transform log data", "data processing rules", "rule group", "enrichment settings", "E2M definition", "labels cardinality", "bulk delete rules", "enrichment limits", "search enrichment table", "what should I convert to metrics", "E2M not producing metrics", "E2M no series", "reduce log cost with E2M", "logs to metrics aggregation", "spans to metrics", or wants to configure how Coralogix processes, enriches, or transforms ingested data.

Quality

86%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Low

Low-risk findings worth noting

SKILL.md
Quality
Evals
Security

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 skill body with copy-paste-ready CLI commands, exact wire-format examples, explicit verification steps, and strong troubleshooting feedback loops for all four workflows. The main improvement areas are deduplicating the E2M compute-model content between the body and the reference file and adding validation guidance around the destructive bulk-delete operation.

Suggestions

Deduplicate the "How E2M is computed" explanation and TCO-tier table between SKILL.md and references/e2m-schemas.md — keep a one-line summary in the body and point to the reference for the full model.

Add validation guidance around the destructive batch operation `cx parsing-rules bulk-delete --ids`, e.g., run `cx parsing-rules list -o json` first, confirm the IDs and count, then delete.

Tighten the labels-cardinality caveat paragraph to the essential instruction (endpoint unavailable via REST; forecast via the UI or estimate permutations manually and set `permutationsLimit`).

DimensionReasoningScore

Conciseness

The body is dense with Coralogix-specific knowledge Claude would not have (wire-format gotchas like "must use `requestEnrichments` (not `enrichments` from list output)", tier behavior, hidden CLI caveats) and avoids explaining known concepts. It falls short of anchor 5 because the "How E2M is computed" section and TCO-tier table substantially duplicate content in references/e2m-schemas.md, and the labels-cardinality caveat paragraph could be tightened to the essential instruction.

4 / 5

Actionability

Commands are copy-paste ready throughout (`cx parsing-rules get <rule-group-id> -o json > template.json`, jq pipelines like `del(.id, .permutations, .createTime, .updateTime, .metricName)`), JSON payload examples show the exact wire format including common-mistake corrections, and coverage spans the common cases for all four command families plus troubleshooting. This matches the anchor for fully executable, copy-paste-ready guidance covering common cases.

5 / 5

Workflow Clarity

All four workflows are clearly sequenced with explicit verification checkpoints after every create ("Verify Parsing", "Verify Enriched Fields", "Verify the metric", "Verify with PromQL"), limits checks before creating, and a troubleshooting section with error-recovery feedback loops plus a correctly ordered "verify the E2M first, then change TCO" sequence. A 5 is withheld because the destructive batch operation `cx parsing-rules bulk-delete --ids` is recommended in Key Principles with no validation guidance (e.g., list and confirm IDs first), a minor validation gap under anchor 4.

4 / 5

Progressive Disclosure

The single bundle file references/e2m-schemas.md exists, is referenced one level deep, and is well signaled with descriptive link text stating its contents ("Complete Events2Metrics JSON wire format... cardinality/permutations sizing, and gotchas"), with the bulk wire format correctly split out of the body. It is not anchor 5 because the E2M compute model / TCO-tier table is duplicated between the body and the reference file rather than living in one place, a minor organization gap.

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 strong trigger-phrase-driven description with excellent natural keyword coverage, including synonyms and failure-mode phrasings, and an explicit "Use when" clause. Its main weakness is that the capability side is conveyed implicitly through keywords rather than a direct statement of what the skill does.

DimensionReasoningScore

Specificity

Concrete actions are named through trigger phrases like "extract fields from logs", "enrich logs", "convert logs to metrics", and "bulk delete rules", plus the closing capability clause "configure how Coralogix processes, enriches, or transforms ingested data". It stops short of anchor 5 because the capability coverage is implied by keyword list rather than an explicit, comprehensive statement of what the skill does (e.g., manage parsing rules, enrichments, E2M, and recording rules).

4 / 5

Completeness

The "when" is explicit and strong ("Use this skill when the user asks to...") with concrete trigger phrases, and a "what" is present via the action phrases and the final clause about configuring Coralogix data processing. It is not anchor 5 because the "what" is never stated directly as a capability description (the four functional areas are only surfaced implicitly through keywords), leaving the what-side slightly less explicit than the anchor-5 example.

4 / 5

Trigger Term Quality

The description covers an extensive set of natural phrasings users would actually say, including synonyms ("log parsing" / "regex extraction" / "create parsing rule"; "events to metrics" / "convert logs to metrics" / "generate metrics from events") and problem statements ("E2M not producing metrics", "E2M no series", "what should I convert to metrics"). This matches the anchor for comprehensive natural-term coverage including synonyms.

5 / 5

Distinctiveness Conflict Risk

The description is well-scoped to a clear niche (Coralogix data-pipeline configuration) with product-specific terms (E2M, PromQL recording, Coralogix) that minimize generic conflict. Minor overlap risk remains with closely related skills in the same ecosystem — e.g., "reduce log cost with E2M" and "search enrichment table" border on cost-optimization and telemetry-querying territory — which fits anchor 4 better than anchor 5.

4 / 5

Total

17

/

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

coralogix/cx-cli

Path

skills/cx-data-pipeline/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.