CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

cx-datasets

Discover the datasets a Coralogix team can query with the `cx datasets` CLI — the fully qualified `<dataspace>/<dataset>` names DataPrime `source` commands need. Use when the user asks to "list datasets", "what datasets do we have", "which datasets can I query", "find datasets", "show dataspaces", "discover datasets", "what data does this team have", "available DataPrime sources", "filter datasets by pillar", "queryable sources", "dataset names for DataPrime", or wants to enumerate or filter the queryable datasets before running a DataPrime query.

Quality

93%

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

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.

The body is a tight, highly actionable reference for a single CLI: executable commands throughout, copy-paste-safe escaping notes, and a coherent list-filter-query workflow. The only deductions are minor redundancy across sections, absent error-recovery guidance in the workflow, and everything being inlined in one file rather than split into references.

Suggestions

Remove the duplicated jq pipeline and filter guidance — state each once (Workflow) and let Key Principles reference it, tightening conciseness toward the 5 anchor.

Add a brief error-recovery step to the workflow (e.g., if `--filter` returns no rows or a 400, drop the filter and list all datasets, or check the `<v1>` version tag) to close the workflow-clarity gap.

If the skill grows, move the DPXL filter syntax and dataset row-field tables into a `references/` file linked from a short section, improving progressive disclosure beyond the single-file layout.

DimensionReasoningScore

Conciseness

The body is lean and assumes Claude's competence — tables for commands and row fields, copy-paste commands, and only the Coralogix-specific context Claude cannot know. It falls short of 5 because of minor duplication: the jq pipeline appears in both the Workflow and Key Principles sections, and `--filter` guidance is repeated across three sections. It is clearly above the 3 anchor's 'some unnecessary explanation'.

4 / 5

Actionability

Every example is executable and copy-paste safe — `cx datasets list -o json | jq -r '.[] | .dataspace + "/" + .dataset'`, shell-escaped DPXL filters (`--filter "<v1> \$d.pillar == 'logs'"`), and real query invocations with concrete source names — plus practical gotchas (version tag required, `$` escaping, `cx logs` takes no `--source`). This matches the 5 anchor's fully executable, common-case-covering standard.

5 / 5

Workflow Clarity

The three-step sequence (list → narrow with a filter → query by full source name) is clearly ordered, and 'Never guess dataset names — list first, then query' acts as an explicit precondition; the operation is read-only, so the destructive-validation cap does not apply. It does not reach 5 because there are no error-recovery feedback loops (e.g., what to do when a filter returns nothing or a 400 is returned beyond the version-tag note).

4 / 5

Progressive Disclosure

The body (~90 lines) has clean, well-labeled sections and a Related Skills pointer, but there are no bundle files and all content is inlined. It exceeds the under-50-line simple-skill case, and content like the DPXL Filter Syntax details could plausibly live in a reference file — 'good structure, most content appropriately placed' with minor organization gaps, i.e. the 4 anchor rather than 5.

4 / 5

Total

17

/

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 a model example: it states concrete capabilities in third person, gives an explicit 'Use when' clause with a dozen natural trigger phrases, and cleanly scopes itself to dataset discovery ahead of DataPrime querying. No fluff, over-claims, or generic language is present.

DimensionReasoningScore

Specificity

The description lists multiple concrete actions — discover datasets a Coralogix team can query, produce the fully qualified `<dataspace>/<dataset>` names DataPrime `source` commands need, and 'enumerate or filter the queryable datasets' — comprehensively covering the CLI's capability. Coverage is complete for this niche rather than minor-gapped, so it matches the 5 anchor over 4.

5 / 5

Completeness

It explicitly answers both what (discover/enumerate/filter queryable datasets and their fully qualified names for DataPrime `source` commands) and when ('Use when the user asks to ... before running a DataPrime query') with concrete trigger phrases, mirroring the 5 anchor's structure. A 4 would require the 'when' to be less explicit, which it is not.

5 / 5

Trigger Term Quality

It includes a comprehensive set of natural user phrasings ('list datasets', 'what datasets do we have', 'which datasets can I query', 'find datasets', 'show dataspaces', 'discover datasets', 'what data does this team have', 'available DataPrime sources', 'filter datasets by pillar', 'queryable sources', 'dataset names for DataPrime') with no obvious synonyms missing. This is at least as thorough as the 5 anchor's 'PDF files, PDFs, forms, document extraction, .pdf'.

5 / 5

Distinctiveness Conflict Risk

It occupies a clear niche — Coralogix dataset discovery via the `cx datasets` CLI — with distinct discovery-oriented triggers ('list datasets', 'find datasets', 'show dataspaces') that would not fire a DataPrime query-writing or general Coralogix skill. Overlap risk is minimal, matching the 5 anchor.

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

coralogix/cx-cli

Path

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