Prometheus Missing Data Troubleshooting
prometheus/prometheus-mcp
Finds where a Prometheus metric stops existing, whether at the target, the scrape, relabeling or the query, using the tools of a connected Prometheus MCP server.
A skill your agent uses for any question involving telemetry data: "investigate an issue", "debug a problem", "find out why something is slow", "check error rates", "analyze user behavior"…
Install Cx Telemetry Querying
$ npx skills add coralogix/cx-cli --skill cx-telemetry-querying -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install coralogix/cx-cli cx-telemetry-querying --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/coralogix/cx-cli.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/cx-telemetry-querying .claude/skills/cx-telemetry-querying && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "cx-telemetry-querying" agent skill from https://github.com/coralogix/cx-cli/tree/master/skills/cx-telemetry-querying into .claude/skills/cx-telemetry-querying/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "cx-telemetry-querying", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/coralogix/cx-cli/tree/master/skills/cx-telemetry-queryingType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add coralogix/cx-cli --skill cx-telemetry-querying -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install coralogix/cx-cli cx-telemetry-querying --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/coralogix/cx-cli.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/cx-telemetry-querying .agents/skills/cx-telemetry-querying && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "cx-telemetry-querying" agent skill from https://github.com/coralogix/cx-cli/tree/master/skills/cx-telemetry-querying into .agents/skills/cx-telemetry-querying/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "cx-telemetry-querying", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add coralogix/cx-cli --skill cx-telemetry-querying -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install coralogix/cx-cli cx-telemetry-querying --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/coralogix/cx-cli.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/cx-telemetry-querying .cursor/skills/cx-telemetry-querying && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "cx-telemetry-querying" agent skill from https://github.com/coralogix/cx-cli/tree/master/skills/cx-telemetry-querying into .cursor/skills/cx-telemetry-querying/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "cx-telemetry-querying", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/coralogix/cx-cli.git --path skills/cx-telemetry-querying--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add coralogix/cx-cli --skill cx-telemetry-querying -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install coralogix/cx-cli cx-telemetry-querying --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/coralogix/cx-cli.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/cx-telemetry-querying .gemini/skills/cx-telemetry-querying && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "cx-telemetry-querying" agent skill from https://github.com/coralogix/cx-cli/tree/master/skills/cx-telemetry-querying into .gemini/skills/cx-telemetry-querying/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "cx-telemetry-querying", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install coralogix/cx-cli cx-telemetry-queryingInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add coralogix/cx-cli --skill cx-telemetry-querying -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/coralogix/cx-cli.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/cx-telemetry-querying .github/skills/cx-telemetry-querying && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "cx-telemetry-querying" agent skill from https://github.com/coralogix/cx-cli/tree/master/skills/cx-telemetry-querying into .github/skills/cx-telemetry-querying/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "cx-telemetry-querying", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add coralogix/cx-cli --skill cx-telemetry-querying -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install coralogix/cx-cli cx-telemetry-querying --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/coralogix/cx-cli.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/cx-telemetry-querying .opencode/skills/cx-telemetry-querying && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "cx-telemetry-querying" agent skill from https://github.com/coralogix/cx-cli/tree/master/skills/cx-telemetry-querying into .opencode/skills/cx-telemetry-querying/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "cx-telemetry-querying", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
cx-telemetry-querying- GitHub stars
- 121
- Token cost
- ~2.6k tokens
- SKILL.md length
- 1,170 words
- Files
- 8 (incl. references)
- Skills in repo
- 21
- Repo updated
- First seen
- Licence
- Apache-2.0
At a glance
A skill your agent uses for any question involving telemetry data: "investigate an issue", "debug a problem", "find out why something is slow", "check error rates", "analyze user behavior"…
- Works in 4 steps: Search Metrics → Search Log and Span Fields → Search the Codebase → …
- Any question involving telemetry data: investigate an issue
- SKILL.md covers Loading References, Safety, Quick Routing Guide and Discovery Workflow, plus 5 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Cx Telemetry Querying is an agent skill from 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…
Its SKILL.md is about 2.6k tokens, which your agent loads only when the skill is triggered. The skill folder holds 8 other files, including reference files (for example `references/dataprime-reference.md`, `references/logs-querying.md` and `references/metrics-querying.md`).
It sits in DevOps & Cloud, covering Observability, Debugging and Web performance. It works with Prometheus and JavaScript. The repository describes itself as: This is the Coralogix CLI. The licence is Apache-2.0.
When your agent uses it
- Any question involving telemetry data: investigate an issue
- Debug a problem
- Find out why something is slow
- Check error rates
Example prompts
- “investigate an issue”
- “debug a problem”
- “find out why something is slow”
- “/cx-telemetry-querying”
Workflow steps
4 steps, taken from the step headings in SKILL.md.
What it can do on your machine
Read from SKILL.md and the folder at commit c071372. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md (its code samples are bash).
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Cx Telemetry Querying loads about 2.6k tokens when it runs, and up to ~19k if it reads all its reference files. Until then it costs about 219 tokens; SKILL.md has 1,170 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from coralogix/cx-cli at commit c071372, republished under its Apache-2.0 licence (© coralogix). 1,170 words, ~2,650 tokens.
Download SKILL.mdSave it as
.claude/skills/cx-telemetry-querying/SKILL.md (or your agent's skills folder). This skill also uses 7 other files; get the full folder from GitHub.- name
- cx-telemetry-querying
- description
- 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.
- metadata.version
- 0.2.1
Telemetry Querying Skill
Use this skill as the entry point for any investigation, debugging, or data question that may be answered from telemetry data. It helps you decide where the relevant signal lives (metrics, logs, traces, RUM) and tells you which reference files to load before querying.
Loading References
Before querying, load the reference files for the chosen pillar:
| Pillar | Load these files |
|---|---|
| Logs | references/dataprime-reference.md + references/logs-querying.md |
| Spans / Traces | references/dataprime-reference.md + references/spans-querying.md |
| Metrics | references/promql-guidelines.md + references/metrics-querying.md |
| RUM (frontend) | references/dataprime-reference.md + references/rum-querying.md + references/rum-fields.md |
| DataPrime syntax only | references/dataprime-reference.md |
Safety
All query commands (cx logs, cx spans, cx metrics, cx dataprime, cx search-fields) are read-only and work in --read-only mode. They never modify data and can be run freely without --yes.
Quick Routing Guide
Use this table for obvious cases where one pillar is the clear first choice:
| Question Type | First Choice | Fallback |
|---|---|---|
| UI behavior, page load, frontend errors | RUM | Traces (if backend-related) |
| Endpoint latency, throughput, error rates | Metrics | Traces (for per-request detail) |
| Service-to-service dependencies, request flow | Traces | Logs (for debug output) |
| Specific error messages, stack traces | Logs | Traces (for request context) |
| Infrastructure health (CPU, memory, disk) | Metrics | - |
| Business events (purchases, signups) | Depends - see Discovery Workflow | - |
For ambiguous questions (e.g., "How much money did users spend last week?"), the signal could live in any pillar. Follow the Discovery Workflow below.
Discovery Workflow
When the answer could reside in multiple pillars, run discovery in parallel to find the best source.
Step 1: Search Metrics
Check if a relevant metric exists:
cx metrics search --name '*transaction*'
cx metrics search --name '*payment*'
cx metrics search --name '*revenue*'
cx metrics search --description "total purchase amount"If a matching metric is found, load references/promql-guidelines.md + references/metrics-querying.md and continue.
Step 2: Search Log and Span Fields
Use semantic field search to find relevant DataPrime paths:
cx search-fields "transaction amount" --dataset logs
cx search-fields "payment total" --dataset spans
cx search-fields "purchase value" --dataset logs --limit 10If you know a concrete value that should appear in the data but don't know which field holds it, use value search instead. It returns the matching field keys alongside sample values, which also lets you infer the field's type (string, numeric, enum, etc.):
cx search-fields "payment_failed" -s value --dataset logs
cx search-fields "grpc.status.UNAVAILABLE" -s value --dataset spans
cx search-fields "eu-west-1" -s value --dataset allRequirements: cx search-fields needs a Coralogix API key or OAuth on the active profile. If credentials are missing, prompt the user to run cx profiles add <name>.
If matching fields are found:
- For logs: load
references/dataprime-reference.md+references/logs-querying.md - For spans: load
references/dataprime-reference.md+references/spans-querying.md
Step 3: Search the Codebase
When discovery results are ambiguous or you need to validate what a metric/field actually represents, search the codebase:
- Look for metric registration code (e.g.,
prometheus.NewCounter,metrics.record) - Look for log statements that emit the field (e.g.,
logger.info("transaction", ...)) - Look for span attributes (e.g.,
span.setAttribute("purchase.amount", ...))
This confirms the semantic meaning and helps you choose the right pillar.
Step 4: Choose and Query
Based on discovery results, pick the pillar with the clearest signal, load its reference files (see Loading References), then query.
Fallback and Pivoting
If your initial route yields no results, pivot to another pillar.
Example pivot paths:
- Metrics empty → try traces (per-request data) or logs (event records)
- Logs empty → try traces (structured span attributes) or metrics (aggregated counters)
- Traces empty → try logs (text-based debug output)
Do not stop after one failed attempt. Try at least two pillars before concluding the data does not exist.
CLI Commands Reference
| Command | Purpose | When to Use |
|---|---|---|
cx schema | Output the full command tree as JSON | Discover all available commands and their flags |
cx metrics search --name <pattern> | Find metrics by name | First step for metrics discovery |
cx metrics search --description <text> | Semantic metric search | When you know what you want but not the name |
cx search-fields "<text>" --dataset logs | Find log fields by description | Discovery for log-based questions |
cx search-fields "<text>" --dataset spans | Find span fields by description | Discovery for trace-based questions |
cx search-fields "<value>" -s value --dataset logs | Find log fields that contain a known value | When you know a value but not which log field holds it — also reveals field type from the returned values |
cx search-fields "<value>" -s value --dataset spans | Find span fields that contain a known value | When you know a value but not which span attribute holds it |
cx search-fields "<value>" -s value --dataset all | Same, across logs and spans | When you want to search across both logs and spans at once |
cx spans "filter $l.serviceName == '<service>'" --limit 10 | Search spans by service | When investigating a specific service |
cx dataprime list | List DataPrime commands/functions | When building log or span queries |
cx dashboards search "<description>" | Find existing dashboards by natural-language description | Before creating a new dashboard — check if one already exists |
cx dashboards query-search --description "<text>" | Find dashboard widgets whose queries cover a topic | Discover how a topic is already being monitored |
cx dashboards query-search --field "<field-path>" | Find widgets that reference a specific field | Reuse existing PromQL/DataPrime patterns for a known field |
Show full SKILL.md (408 more words)Show less
Examples
Example 1: Business Question (Ambiguous Source)
Question: "How much money did people spend on the platform last week?"
Approach:
- Search metrics:
cx metrics search --name '*revenue*'andcx metrics search --name '*transaction*' - Search log fields:
cx search-fields "transaction amount" --dataset logs - Search span fields:
cx search-fields "payment total" --dataset spans - If a metric like
payment_total_usdexists, load metrics references and run a range query - If only logs have the data, load logs references and use DataPrime aggregation
- If traces have
purchase.amountattribute, load spans references
Example 2: Latency Question (Clear First Choice)
Question: "What's the average latency of the checkout route?"
Approach:
- First try metrics:
cx metrics search --name '*checkout*latency*'orcx metrics search --name '*http*duration*' - If a histogram metric exists, load metrics references and use
histogram_quantile - If no metric, fall back to traces: load spans references and aggregate span durations
Example 3: Frontend Performance (RUM)
Question: "Why is the dashboard page loading slowly for users?"
Approach:
- This is clearly a RUM question - load
references/rum-querying.md+references/rum-fields.md+references/dataprime-reference.md - Query web vitals and page load times with
cx dataprime query --source rum.events '...' - If RUM shows backend calls are slow, pivot to spans references for the API calls
Example 4: Error Investigation (Logs + Traces)
Question: "Why are users getting 500 errors on the payment endpoint?"
Approach:
- Check error rate metrics → load metrics references
- Search for error logs → load logs references
- Get traces for failed requests → load spans references
- Cross-reference: find trace IDs in logs, then fetch full traces for root cause
Beyond Investigation
Not every question is answered by querying data. If the user's intent is operational rather than investigative, route to the appropriate workflow skill:
| User Intent | Route To |
|---|---|
| Reducing costs, checking usage, TCO policies | cx-cost-optimization |
| Triaging a case, who got paged, case timeline | cx-cases |
| SLO status, error budget, service-level targets | cx-slos |
| Setting up monitoring, webhooks, notifications | cx-observability-setup |
| Configuring parsing rules, enrichments, E2M | cx-data-pipeline |
| Access audit, API keys, user management | cx-platform-admin |
| Creating or managing dashboards | cx-dashboards |
| Finding or searching existing dashboards | cx-search-dashboard |
Key Principles
- Load references before querying: check the Loading References table first
- Discover before querying: always run search/discovery to find the right source
- Parallel discovery: for ambiguous questions, search metrics, logs, and spans concurrently
- Validate with code: when unsure what a metric or field represents, check the codebase
- Pivot on failure: if one pillar is empty, try another before giving up
© coralogix, Apache-2.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
SKILL.md and 7 other files (references) in skills/cx-telemetry-querying of coralogix/cx-cli.
- SKILL.md
- references/dataprime-reference.md
- references/logs-querying.md
- references/metrics-querying.md
- references/promql-guidelines.md
- references/rum-fields.md
- references/rum-querying.md
- references/spans-querying.md
Open the folder on GitHubat commit c071372
Compare with similar skills
Cx Telemetry Querying next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Cx Telemetry Querying this skillcoralogix/cx-cli | 121 | — | ~2.6k | Automated safety check: Pass | Apache-2.0 | |
| Prometheus Missing Data Troubleshootingprometheus/prometheus-mcp | 121 | — | ~587 | Automated safety check: Pass | Apache-2.0 | |
| Redis Observabilityredis/agent-skills | 166 | 2 repos | ~911 | Automated safety check: Pass | MIT | |
| Logfire Instrumentationbasicmachines-co/basic-memory | 4.1k | — | ~2.3k | Automated safety check: Pass | AGPL-3.0 | |
| Developing Funboost Mixinydf0509/funboost | 895 | — | ~2.1k | Automated safety check: Pass | None | |
| Release Reviewm4r1k/Eneru | 149 | — | ~1.9k | Automated safety check: Pass | MIT |
Similar skills
- Official
Redis Observability
redis/agent-skills
Redis observability guidance — which metrics to monitor (memory, connections, hit ratio, ops/sec, rejected connections), which built-in commands to reach for during incident triage (SLOWLOG, INFO…
Logfire Instrumentation
basicmachines-co/basic-memory
Adds Pydantic Logfire tracing, logging and metrics to Python, JavaScript or TypeScript and Rust projects, with the correct setup order and library extras.
Developing Funboost Mixin
ydf0509/funboost
当需要为 funboost 创建 Consumer 或 Publisher 的 Mixin 扩展类时使用。触发场景：添加监控、熔断、限流、链路追踪等横切关注点，编写自定义前置/后置处理钩子。关键词：mixin, consumeroverridecls, publisheroverridecls, ConsumerMixin, 自定义消费者, hook, 拦截器, 熔断器, 监控…
Release Review
m4r1k/Eneru
Mandatory pre-release deep review for minor/major releases (X.Y.0 / X.0.0).
Archestra Dev Observability
archestra-ai/archestra
A skill your agent uses when changing Archestra tracing, metrics, OpenTelemetry, Tempo, Grafana, Prometheus, LLM/MCP spans, observability labels, or local observability setup.
More from coralogix/cx-cli
All 21 skills in this repoCx AI Center
coralogix/cx-cli
A skill your agent uses for any question or action about the user's AI/GenAI applications or agents — their behavior, prompts/responses, quality, hallucinations, guardrails, security, cost/tokens…
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"…
Cx Coding Agents
coralogix/cx-cli
A skill your agent uses when the user asks about AI Center Coding Agents data, wants to reproduce or extend the Coding Agents dashboards, or asks questions about usage, cost, tokens, sessions…
Cx Cost Optimization
coralogix/cx-cli
A skill your agent uses when the user asks to "check data usage", "list TCO policies", "reduce Coralogix costs", "optimize observability spend", "lower our logging bill", "data budget exceeded"…
Cx Data Pipeline
coralogix/cx-cli
A skill your agent uses when the user asks to "set up parsing", "create parsing rule", "extract fields from logs", "regex extraction", "log parsing", "enrich logs", "add context to logs", "custom…
Cx Dashboards
coralogix/cx-cli
Build and deploy a Coralogix dashboard for a given service from its logs, spans, metrics, and service specs.
Related
Works with
Categories
Questions about Cx Telemetry Querying
What does Cx Telemetry Querying do?
A skill your agent uses for any question involving telemetry data: "investigate an issue", "debug a problem", "find out why something is slow", "check error rates", "analyze user behavior"…. Cx Telemetry Querying is an agent skill from coralogix/cx-cli.
When should I use Cx Telemetry Querying?
Cx Telemetry Querying fits situations like: any question involving telemetry data: investigate an issue; debug a problem; find out why something is slow; check error rates.
How do I install Cx Telemetry Querying in Claude Code?
Run `npx skills add coralogix/cx-cli --skill cx-telemetry-querying -a claude-code`. Or copy the skill folder (skills/cx-telemetry-querying in coralogix/cx-cli) into .claude/skills/cx-telemetry-querying in your project. Claude Code loads it when a task matches its description.
How do I install Cx Telemetry Querying in Codex?
Run `npx skills add coralogix/cx-cli --skill cx-telemetry-querying -a codex`. Or copy the skill folder (skills/cx-telemetry-querying in coralogix/cx-cli) into .agents/skills/cx-telemetry-querying in your project. Codex loads it when a task matches its description.
Can I use Cx Telemetry Querying in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add coralogix/cx-cli --skill cx-telemetry-querying -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/cx-telemetry-querying, .gemini/skills/cx-telemetry-querying, .github/skills/cx-telemetry-querying and .opencode/skills/cx-telemetry-querying in your project.
What does Cx Telemetry Querying need to run?
SKILL.md names no scripts, command-line tools or credentials: Cx Telemetry Querying is instructions for the agent only.
Does Cx Telemetry Querying access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Cx Telemetry Querying safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Cx Telemetry Querying use?
Cx Telemetry Querying is published under the Apache-2.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Cx Telemetry Querying use?
About 2.6k tokens (SKILL.md is roughly 11k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 16k tokens, read only when the agent opens those files.
What are the alternatives to Cx Telemetry Querying?
Skills that share tags, products or a category with Cx Telemetry Querying: Prometheus Missing Data Troubleshooting (prometheus/prometheus-mcp, 121 stars), Redis Observability (redis/agent-skills, 166 stars), Logfire Instrumentation (basicmachines-co/basic-memory, 4.1k stars) and Developing Funboost Mixin (ydf0509/funboost, 895 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Cx Telemetry Querying?
coralogix (a GitHub organization) maintains it in coralogix/cx-cli, which has 121 GitHub stars. The repository holds 21 skills in this directory. The repository was last updated on October 7, 2026.
Source: coralogix/cx-cli on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.