CtrlK
BlogDocsLog inGet started
Tessl Logo

cx-olly

This skill should be used when the user asks to "chat with AI", "ask Olly", "ask the agent", "send message to AI", "continue a chat", "follow up on chat", "get artifact", "download artifact", "list artifacts", "retrieve generated content", "AI-generated charts", "AI analysis", "conversational observability", "natural language query", or wants to interact with the Coralogix Observability Agent (Olly) using the cx CLI.

65

Quality

82%

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.

A strong, highly actionable CLI skill body: every command is executable, workflows are sequenced with a concrete example, and content stays lean. The main gaps are minor — repeated agent-to-agent-mode guidance and an abstract 'run in background and poll' instruction without a concrete polling mechanism.

DimensionReasoningScore

Conciseness

The body is lean — a command table, executable examples, and terse principles — and explains nothing Claude already knows. Minor trimmable redundancy: the --agent-to-agent-mode default is stated three times (top note, dedicated section, Key Principles) and async-by-default twice. Fits 'efficient; minor instances that could be trimmed'.

4 / 5

Actionability

Every section gives copy-paste-ready commands with concrete flags (--chat-id, --model, --timeout, --agent-to-agent-mode), jq pipelines, and a complete end-to-end workflow example covering the common cases. Matches 'fully executable; copy-paste ready; specific examples cover the common cases'.

5 / 5

Workflow Clarity

The investigate-workflow example sequences background ask → chat-id follow-up → artifacts list/get with per-step comments, and sections clearly delineate start/continue. However, 'launch as a background process and poll it for completion' lacks a concrete polling mechanism or completion check, leaving checkpoints implicit — anchor 4, not 5.

4 / 5

Progressive Disclosure

No bundle files exist, and the ~150-line single-file CLI reference is well-organized with clear sections (commands, chat, artifacts, workflows, principles). Structure is appropriate for this size, though it exceeds the under-50-lines simple-skill case and could offload the artifacts output-behavior detail. Anchor 4 fits.

4 / 5

Total

17

/

20

Passed

Description

73%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 has excellent trigger-term coverage and an explicit 'use when' clause, but the capability statement is thin — it says 'interact with Olly via the cx CLI' without saying what that interaction does, and several generic AI-related triggers create conflict risk with other agent skills.

Suggestions

Add one sentence stating the concrete capabilities, e.g. 'Ask Olly questions about alerts, logs, metrics, and traces; it investigates your observability data and generates artifacts (charts, reports) you can retrieve.'

Narrow the generic triggers ('ask the agent', 'chat with AI', 'AI analysis', 'natural language query') toward Olly/Coralogix-specific phrasing to reduce conflict with other AI-assistant skills.

Lead with the what before the when: a short capability statement followed by the trigger list reads more naturally than the current trigger-list-first structure.

DimensionReasoningScore

Specificity

The description names the domain ('interact with the Coralogix Observability Agent (Olly) using the cx CLI') but never states concrete capabilities like analyzing alerts/metrics/logs or generating charts and reports — those actions only appear obliquely as quoted trigger phrases. It matches 'names domain and 1-2 concrete actions, but not comprehensive' rather than the multi-action coverage of level 4.

3 / 5

Completeness

The 'when' is explicit and rich with concrete trigger phrases, and a 'what' is present ('interact with the Observability Agent using the cx CLI'), but the 'what' is vague — it doesn't say what interacting accomplishes. It sits at 'has both what and when' with one side weak, below level 5's clearly-explicit both.

4 / 5

Trigger Term Quality

Comprehensive natural-language coverage with synonyms: 'chat with AI', 'ask Olly', 'ask the agent', 'continue a chat', 'follow up on chat', 'get artifact', 'download artifact', 'list artifacts', 'retrieve generated content', 'AI-generated charts', 'AI analysis'. These are phrases a user would naturally say, matching the comprehensive-synonyms anchor.

5 / 5

Distinctiveness Conflict Risk

Product-specific names ('Olly', 'Coralogix') create a niche, but generic triggers like 'ask the agent', 'chat with AI', 'AI analysis', and 'natural language query' could overlap with other agent or AI-analysis skills. Somewhat specific yet with real overlap risk, matching anchor 3.

3 / 5

Total

15

/

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
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.