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.
- Installs
- 3.4K
- Last 24h
- +75
- Trending rank
- #2432
- Security
- Not audited
Install
Works with every agent the skills CLI supports.
npx skills add https://github.com/coralogix/cx-cli --skill cx-olly- 01
Install
Run the command in your project. The CLI asks which agents to install for.
- 02
Describe the task
Ask your agent for something this skill covers. It loads cx-olly automatically when relevant.
- 03
Review the result
The agent follows the SKILL.md steps, scripts and references bundled with the skill.
SKILL.md
The instructions your agent reads when the skill is triggered.
Olly Observability Agent Skill
Use this skill to interact with Coralogix's Observability Agent (Olly) via the cx olly CLI commands. Olly can analyze your observability data, answer questions about alerts, metrics, logs, and generate artifacts like charts and reports.
cx olly ask defaults --agent-to-agent-mode to false. If you're an LLM/agent, pass --agent-to-agent-mode - see "Agent-to-agent mode" below.
CLI Commands
| Command | Purpose | Key flags |
|---|---|---|
cx olly ask "message" | Send a message to the Observability Agent | --chat-id, --model, --timeout, --agent-to-agent-mode |
cx olly artifacts list | List all generated artifacts | - |
cx olly artifacts get <id> | Get artifact content by ID | - |
Output format: append -o json or -o toon for machine-readable output.
Single-profile only: cx olly commands do not support multi-profile fan-out. Use -p <profile> to specify a single profile.
Running Olly (async by default)
Run cx olly ask asynchronously by default: launch it as a background process and poll it for completion rather than blocking on it. Olly investigations routinely take minutes, so this is the normal mode for cx olly ask.
Only run cx olly ask inline (foreground, blocking) for a short question you expect Olly to answer quickly — a quick lookup or a one-line follow-up. When in doubt, run it in the background.
Chat Commands
Start a new conversation
cx olly ask "What alerts fired today?" --agent-to-agent-mode
This creates a new chat and returns a response along with a Chat ID that you can use for follow-up questions.
Remove --agent-to-agent-mode if you don't have context to share (like quick access to source files) or if the created chat is only for human usage.
Continue an existing chat
cx olly ask "Tell me more about the error rates" --chat-id <chat-id> --agent-to-agent-mode
Use --chat-id to continue a conversation and maintain context from previous messages. Background the follow-up too when it kicks off another investigation.
Model selection
Available models include gpt-5.2 (default), claude-sonnet-4-5, sonnet-4.6, gpt-5.4, claude-haiku-4-5.
cx olly ask "Explain this error" --model claude-sonnet-4-5 --agent-to-agent-mode
Timeout
For complex queries that may take longer, increase Olly's response timeout (default: 900 seconds):
cx olly ask "Deep analysis of last week's incidents" --timeout 1800 --agent-to-agent-mode
--http-timeout <SECONDS> (or CX_HTTP_TIMEOUT) sets the HTTP request
deadline for all CLI commands, including Olly. It is separate from the Olly
response timeout.
Agent-to-agent mode
--agent-to-agent-mode defaults to false, since cx olly ask is used directly by humans as well as by agents. If you're an LLM/agent, pass --agent-to-agent-mode to opt into shorter, sub-agent-style responses: no charts/tables, clarifying questions instead of guessing, and reliance on your broader context.
cx olly ask "Analyze this for me" --agent-to-agent-mode
It's per-call, not per-chat. --chat-id does not remember it - re-pass --agent-to-agent-mode on every follow-up turn, or the mode silently flips back to human-facing mid-conversation.
Artifacts
Olly can generate artifacts like query results, previews, and citations. Artifact IDs appear as links in the agent's response text.
List all artifacts
cx olly artifacts list
cx olly artifacts list -o json
Get artifact content
cx olly artifacts get <artifact-id>
cx olly artifacts get <artifact-id> -o json
The artifacts get command automatically:
- Fetches artifact metadata
- Downloads content from the presigned URL
- Decompresses gzip content
- Parses JSON and uses spill logic for large content
- Saves non-JSON text to a temp file
Output behavior:
- JSON content: Displayed directly, or spilled to file if large
- Text content: Saved to temp file (e.g.,
/tmp/cx_results_artifact_<id>_<hash>.txt)
Workflow Examples
Investigate an issue
# Start investigation — run in the background and poll for completion
cx olly ask "Why is the checkout service showing high latency? Check logs with 'checkout:' strings and aws related metrics" --agent-to-agent-mode
# Follow up with the chat ID from the response — also background and poll
cx olly ask "What changed in the last hour?" --chat-id abc-123-def --agent-to-agent-mode
# Once the interaction has completed, get any generated charts
cx olly artifacts list -o json | jq '.[0].id'
cx olly artifacts get <artifact-id>
Get JSON output for scripting
# Get response as JSON
cx olly ask "List top 5 error messages" -o json --agent-to-agent-mode | jq '.response'
# Parse artifacts
cx olly artifacts list -o json | jq '.[] | {id, filename, created_at}'
Detailed analysis with specific model
cx olly ask "Perform root cause analysis for the outage on 2024-01-15" \
--model claude-sonnet-4-5 \
--timeout 1800 \
--agent-to-agent-mode
Key Principles
- Async by default - run
cx olly askas a background process and poll it for completion; only run inline (blocking) for short questions you expect Olly to answer quickly - Chat IDs enable context - save the Chat ID from responses to continue conversations
- Use
-o jsonfor scripting - pipe tojqfor filtering and extraction - Artifact IDs are in response text - look for markdown links like
[Chart](https://...artifact_view/<id>) - Single-profile only -
cx ollydoes not support multi-profile queries - Large artifacts auto-spill - JSON content over the configured limit is saved to temp files
- Check source code before asking - give Olly concrete context from the source code if available, such as which metric to start investigating from, before calling it
- Limit investigation scope - guide Olly to the correct limited scope, for example limit to just logs or to specific time ranges
- Pass
--agent-to-agent-modewhen calling as an LLM/agent - it defaults tofalse(human-facing); agents should opt in for shorter, sub-agent-style responses
Related Skills
cx-telemetry-querying- for direct DataPrime/PromQL queries without AI agent assistance (covers logs, spans, metrics, RUM)cx-alerts- for managing alert definitions
FAQ
What does the cx-olly skill do?
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.
How do I install cx-olly?
Run npx skills add https://github.com/coralogix/cx-cli --skill cx-olly in your project. The skills CLI detects the agents you use and copies the skill into the right folder. For Claude Code you can also place the skill folder at ~/.claude/skills/cx-olly/ (personal) or .claude/skills/cx-olly/ (project).
Which AI agents can use cx-olly?
Any agent that supports the open Agent Skills format (a folder with a SKILL.md file), including Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, Windsurf, Cline, OpenCode and more.
Is cx-olly safe to install?
No partner security audit is available yet. Skills can run commands and scripts, so read the SKILL.md and any bundled files before installing.
Who maintains cx-olly?
It is published by coralogix in coralogix/cx-cli. It has 3,394 recorded installs.
More from coralogix/cx-cli
cx-telemetry-querying
coralogix/cx-cli
Use this skill for any question involving telemetry data: "investigate an issue", "debug a problem", "find out why something is slow", "check error rates", "analyze user behavior", "understand a production incident", "query telemetry data", "look at logs", "search logs", "find errors", "find stack traces", "filter by severity", "check traces", "examine spans", "investigate request latency", "debug service-to-service calls", "look up a trace ID", "analyze RUM data", "query rum.events", "check frontend performance", "frontend errors", "Core Web Vitals", "JavaScript exceptions", "query metrics", "check CPU usage", "run a PromQL query", "check error rate", "look up a metric", "check memory usage", "how do I write a DataPrime query", "DataPrime syntax", or wants to answer questions using observability data from logs, metrics, traces, RUM, or APM.
cx-search-dashboard
coralogix/cx-cli
This skill should be used when the user asks to "find a dashboard", "search dashboards", "does a dashboard exist for X", "find widgets that query Y", "which dashboards use this field", "find a dashboard about errors", "look up dashboards by description", "search for existing monitoring dashboards", "find widgets that reference a field", or wants to discover existing Coralogix dashboards or widgets using natural-language or field-based search.
coralogix-docs
coralogix/cx-cli
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.
cx-alerts
coralogix/cx-cli
This skill should be used when the user asks to "manage alerts", "create alert", "list alerts", "delete alert", "check alert status", "enable alert", "disable alert", "investigate firing alerts", "check which alerts are active", "find alerting rules", "set up an alert", "configure alerting", "mute an alert", "silence an alert", "see alert definitions", "check alert priority", or wants to manage Coralogix alert definitions using the cx CLI.
cx-cli
coralogix/cx-cli
This skill should be used whenever the user runs any cx command, uses the cx CLI, Coralogix CLI, or mentions cx in the context of Coralogix observability. This skill provides cross-cutting concerns like update notifications that apply to all cx commands.
cx-observability-setup
coralogix/cx-cli
Use this skill when the user asks to "set up monitoring", "configure observability", "onboard new service", "create saved view", "set up notifications", "configure webhook", "set up Slack integration", "outgoing webhook", "automation action", "webhook for alerts", "create view", "saved view", "view folder", "organize dashboards", "install integration", "configure extension", "contextual data", "connect external service", "create notification connector", "set up email alerts", "configure PagerDuty", "notification routing", "deploy extension", "test webhook", "notification preset", "test notification", "webhook actions", or wants to set up, configure, or manage the observability stack for a service or team.
Popular devops & cloud skills
microsoft-foundry
microsoft/azure-skills
Build, deploy, evaluate, optimize, fine-tune, and manage Microsoft Foundry agents, models, and resources end to end. USE FOR: foundry, azd ai agent, azd provision/deploy, hosted agent scaffold/develop/run/deploy/troubleshoot, prompt agent create, managed harness agent create, GitHub Copilot harness agent, create agent, update agent, add tool to agent, invoke agent, agent insights, evaluate agent, batch eval, continuous eval, continuous monitoring, agent CI/CD, optimize prompt, improve prompt, optimize agent instructions, Agent Optimizer scaffold, dataset curation from traces, deploy model, model fine-tuning (SFT/DPO/RFT), Foundry project, RBAC, role assignment, permissions, quota, capacity, region, deployment failure, AI Services, create Foundry resource, knowledge index, customize deployment, onboard, availability, training-data, grader, distillation, large file upload. DO NOT USE FOR: Azure Functions, App Service, general Azure deploy (use azure-deploy), general Azure prep (use azure
azure-diagnostics
microsoft/azure-skills
Debug Azure production issues on Azure using AppLens, Azure Monitor, resource health, and safe triage. WHEN: debug production issues, troubleshoot app service, app service high CPU, app service deployment failure, troubleshoot container apps, container app 503 or target port mismatch, troubleshoot functions, function telemetry missing or stopped after a config/connection-string change, troubleshoot AKS, VM RDP, Linux SSH, VM black screen, can't connect to VM, reset VM password, NSG or firewall blocking, kubectl cannot connect, kube-system/CoreDNS failures, pod pending, crashloop, node not ready, upgrade failures, analyze logs, KQL, insights, image pull failures, cold start issues, health probe failures, resource health, root cause of errors, troubleshoot event hubs, troubleshoot service bus, messaging SDK error, AMQP connection failure, message lock lost, lock renewal during long-running processing, service bus dead letter.
azure-prepare
microsoft/azure-skills
Prepare azd-based Azure projects for deployment: generates azure.yaml, infrastructure (Bicep/Terraform), and Dockerfiles for the Azure Developer CLI (azd) workflow. USE ONLY when the user explicitly wants to use azd as the deployment tool, or the project already has an azure.yaml file. DO NOT USE FOR: non-azd deployments, Python App Service code-only deploys (use python-appservice-deploy), or cross-cloud migration (use azure-cloud-migrate). WHEN: prepare app for azd, create azure.yaml, set up azd infrastructure, modernize app for Azure with azd, deploy with azd, function app, timer trigger, service bus trigger, event-driven function, managed identity, generate Bicep, generate Terraform, create and deploy to Azure.
azure-ai
microsoft/azure-skills
Use for Azure AI: Search, Speech, OpenAI, Document Intelligence. Helps with search, vector/hybrid search, speech-to-text, text-to-speech, transcription, OCR. WHEN: AI Search, query search, vector search, hybrid search, semantic search, speech-to-text, text-to-speech, transcribe, OCR, convert text to speech.
azure-deploy
microsoft/azure-skills
Execute Azure deployments for ALREADY-PREPARED applications that have existing .azure/deployment-plan.md and infrastructure files. DO NOT use this skill when the user asks to CREATE a new application — use azure-prepare instead. This skill runs azd up, azd deploy, terraform apply, and az deployment commands with built-in error recovery. Requires .azure/deployment-plan.md from azure-prepare and validated status from azure-validate. WHEN: "run azd up", "run azd deploy", "execute deployment", "push to production", "push to cloud", "go live", "ship it", "bicep deploy", "terraform apply", "publish to Azure", "launch on Azure". DO NOT USE WHEN: "create and deploy", "build and deploy", "create a new app", "set up infrastructure", "create and deploy to Azure using Terraform" — use azure-prepare for these.
azure-validate
microsoft/azure-skills
Pre-deployment validation for Azure readiness. Run deep checks on configuration, infrastructure (Bicep or Terraform), RBAC role assignments, managed identity permissions, and prerequisites before deploying. WHEN: validate my app, check deployment readiness, run preflight checks, verify configuration, check if ready to deploy, validate azure.yaml, validate Bicep, test before deploying, troubleshoot deployment errors, validate Azure Functions, validate function app, validate serverless deployment, verify RBAC roles, check role assignments, review managed identity permissions, what-if analysis, validate Container Apps deployment.