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.
52
57%
Does it follow best practices?
Impact
—
No eval scenarios have been run
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./skills/cx-olly/SKILL.mdQuality
Discovery
37%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This description is heavily skewed toward trigger terms while almost completely neglecting to explain what the skill actually does. It reads as a list of when-to-use phrases without describing concrete capabilities like sending queries, retrieving observability data, managing chat sessions, or downloading generated artifacts. The Coralogix/Olly specificity helps with distinctiveness but generic AI chat triggers create conflict risk.
Suggestions
Add concrete capability descriptions before the trigger list, e.g., 'Sends natural language queries to the Coralogix Observability Agent (Olly) via the cx CLI, retrieves AI-generated analysis, charts, and artifacts from observability data, and manages multi-turn chat sessions.'
Restructure to clearly separate 'what' from 'when': lead with specific actions (analyze logs, generate charts, query metrics) then follow with 'Use when...' trigger guidance.
Reduce overly generic triggers like 'chat with AI' and 'ask the agent' that could conflict with other skills, or qualify them with domain context (e.g., 'chat with AI about observability data').
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description lists no concrete actions or capabilities. It only describes trigger phrases without explaining what the skill actually does (e.g., what happens when you 'chat with AI' or 'get artifact'). There are no specific operations like 'sends messages to the Coralogix Observability Agent and retrieves analysis results'. | 1 / 3 |
Completeness | The description answers 'when' extensively but almost entirely fails to answer 'what does this do'. There is no explanation of the skill's capabilities, outputs, or concrete actions. The rubric states a missing 'what' or 'when' should result in a low score, and here the 'what' is essentially absent beyond vague references to interacting with an agent. | 1 / 3 |
Trigger Term Quality | The description is essentially a comprehensive list of trigger terms and phrases users might naturally say, including variations like 'chat with AI', 'ask Olly', 'ask the agent', 'send message to AI', 'continue a chat', 'get artifact', 'download artifact', 'list artifacts', 'natural language query', and 'AI analysis'. These cover many natural user phrasings. | 3 / 3 |
Distinctiveness Conflict Risk | The mention of 'Coralogix Observability Agent (Olly)' and 'cx CLI' provides some distinctiveness, but generic triggers like 'chat with AI', 'ask the agent', 'send message to AI', and 'natural language query' could easily conflict with other AI chat or agent interaction skills. | 2 / 3 |
Total | 7 / 12 Passed |
Implementation
77%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a solid, actionable skill with clear executable examples and well-structured workflows for interacting with the Olly CLI. Its main weakness is moderate verbosity—some information is repeated (e.g., single-profile constraint, JSON output flag) and the artifact internals section explains more than Claude needs. The content would benefit from trimming redundancies and potentially splitting detailed reference material into separate files.
Suggestions
Remove the detailed 'automatically' steps list for `artifacts get` (steps 1-5) since Claude doesn't need to know internal implementation details—just the output behavior.
Consolidate the 'Key Principles' section by removing points already covered inline (e.g., `-o json`, single-profile constraint) to reduce repetition.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Generally efficient but includes some unnecessary explanations (e.g., describing what artifacts are, explaining what the artifacts get command 'automatically' does in detail). The model list includes what appear to be fictional model names which adds noise. Some sections like 'Key Principles' repeat information already covered above. | 2 / 3 |
Actionability | Provides fully executable, copy-paste ready bash commands throughout. Every command includes concrete examples with realistic arguments, and the workflow examples show multi-step sequences with actual CLI invocations and jq piping patterns. | 3 / 3 |
Workflow Clarity | The 'Investigate an issue' workflow clearly sequences steps from initial question to follow-up to artifact retrieval. The chat continuation pattern with chat IDs is well-explained. For a non-destructive, read-oriented CLI tool, validation checkpoints aren't critical, and the workflows are clear and well-sequenced. | 3 / 3 |
Progressive Disclosure | Content is well-structured with clear sections and a useful reference table at the top, but everything is inline in a single file. The artifact output behavior details and some workflow examples could be split into separate reference files. The 'Related Skills' section provides good cross-references. No bundle files exist to offload content to. | 2 / 3 |
Total | 10 / 12 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 — 11 / 11 Passed
Validation for skill structure
No warnings or errors.
34d6303
Table of Contents
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.