CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

coralogix-docs

Search and read official Coralogix platform documentation using **`cx docs search`** and **`cx docs fetch`**. Use when the user asks how Coralogix features work, how to configure or use the UI, set up integrations (OpenTelemetry, agents, collectors, webhooks), manage API keys, explore spans/traces/logs in the product, configure alerts/SLOs/dashboards, or needs authoritative product docs — not live tenant telemetry.

Quality

92%

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

88%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 crisp, highly actionable CLI reference: every command is copy-paste executable, the workflow is sequenced with a worked example and troubleshooting recovery paths, and there is no padding or basic-concept explanation. The only weaknesses are mild redundancy between the workflow, example, tips, and troubleshooting sections, and a monolithic single-file structure slightly past the lean threshold.

Suggestions

Trim the redundancy between 'Standard workflow', the worked example, 'Tips', and 'Troubleshooting' — e.g. state the '2–4 focused terms' advice once and let the worked example reference the workflow instead of repeating its commands verbatim.

Consolidate the overlapping guidance in 'Tips' and 'Troubleshooting' (both cover rephrasing/broadening failed searches) into a single section to cut tokens and bring the body closer to a lean single-screen reference.

If the skill grows, move the flag reference and troubleshooting detail into a references/ file so SKILL.md stays a compact overview with one-level-deep, clearly signaled references.

DimensionReasoningScore

Conciseness

Efficient, table-driven, and free of explanations of concepts Claude already knows, but the worked example repeats the Standard workflow's exact commands, Tips restates the "2–4 focused terms" advice, and Troubleshooting duplicates the synonym/broaden guidance — minor trimmable redundancy. Fits the 'minor instances that could be trimmed' anchor rather than the lean every-token-earns-its-place anchor.

4 / 5

Actionability

Fully executable copy-paste commands with real arguments ("cx docs search \"explore spans\" --limit 5", "cx docs fetch user-guides/data_exploration/spans.md", "-o json"), a flags table, and examples covering search, fetch, and machine-readable output. Matches the copy-paste-ready anchor; not score 4 because no key detail is missing.

5 / 5

Workflow Clarity

Clear 4-step sequence (search → pick suffix → fetch → answer) plus a concrete worked example, and the Troubleshooting table supplies validate-and-retry feedback loops ("No search matches → broaden or rephrase", "Fetched page is too narrow → run a second search"). The operation is read-only, so the destructive/batch validation cap does not apply. Not score 4, since error-recovery loops are explicitly present.

5 / 5

Progressive Disclosure

Well-sectioned single file with clearly signaled cross-links to sibling skills (Related, When not to use tables), and no bulky reference material inlined that belongs in a separate file. However, no bundle files exist and the body is ~96 lines — over the under-50-lines threshold where sections alone can earn a 5 — with some duplicated content that consolidation could address. Fits 'good structure; minor organization gaps' rather than the clean split-and-navigate top anchor.

4 / 5

Total

18

/

20

Passed

Description

95%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 description: it states the exact commands, gives an explicit and richly enumerated 'Use when' clause covering UI, integrations, API keys, and observability topics, and closes with a negative boundary that cleanly separates it from live-telemetry skills. Trigger coverage includes natural synonyms a user would genuinely say.

DimensionReasoningScore

Specificity

Names the domain and two concrete actions with the exact executable commands ("using **`cx docs search`** and **`cx docs fetch`**"), which exceeds the generic 1-2-action anchor but stops short of the multi-action comprehensiveness of the top anchor.

4 / 5

Completeness

Explicitly answers both: what ("Search and read official Coralogix platform documentation using cx docs search and cx docs fetch") and when ("Use when the user asks how Coralogix features work... or needs authoritative product docs"), with concrete trigger phrases and a negative boundary ("not live tenant telemetry"). Matches the top anchor exactly; not the level below, where 'when' would be less explicit.

5 / 5

Trigger Term Quality

Comprehensive natural phrasing users would actually say — "how Coralogix features work", "set up integrations", "manage API keys", "explore spans/traces/logs", "alerts/SLOs/dashboards" — including product synonyms like OpenTelemetry/agents/collectors/webhooks. Clearly matches the comprehensive-synonyms anchor, not merely "good coverage with a few missing".

5 / 5

Distinctiveness Conflict Risk

Clear niche (official product documentation lookup) with Coralogix-specific triggers and an explicit exclusion of the adjacent live-telemetry domain ("not live tenant telemetry"), giving minimal conflict risk with sibling query skills. Not score 4, since the overlap-prone phrases (spans/traces/logs) are explicitly disambiguated by that boundary clause.

5 / 5

Total

19

/

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.

Validation — 15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

relative_links

Relative link issues: 9 suspicious

Warning

Total

15

/

16

Passed

Repository

coralogix/cx-cli

Path

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