
cx-ai-center
Use this skill for any question or action about the user's AI/GenAI applications or agents — their behavior, prompts/responses, quality, hallucinations, guardrails, security, cost/tokens, errors, evaluations/policies, model pricing, or configuration — including comparing or tracking agents over time. It covers both analyzing AI telemetry (GenAI spans) and managing AI Center config via the cx ai-center commands.
- Installs
- 2.3K
- Last 24h
- +75
- Trending rank
- #2410
- Security
- Not audited
Install
Works with every agent the skills CLI supports.
npx skills add https://github.com/coralogix/cx-cli --skill cx-ai-center- 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-ai-center 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.
AI Center Skill
This is the tool for anything about AI/GenAI applications — both questions about their behavior (prompts/responses, quality, hallucinations, guardrails, security, cost/tokens, errors, latency — everything AI apps expose through their GenAI spans/tags) and actions to manage them (applications, evaluations/policies, policy↔app links, model pricing). If a request touches an AI application or its GenAI telemetry, use this skill.
Coralogix AI Center observes, evaluates, and guards GenAI/LLM applications. This skill answers questions about AI apps from two sources:
- Configuration (this skill's
cx ai-centercommands): the AI application inventory, configured evaluations/policies, coverage, custom evaluations, and model pricing — none of which live in span telemetry. - Telemetry (GenAI spans): what users asked, how the model answered, cost, tokens,
latency, errors, tool calls, and eval/guardrail verdicts — queried with
cx spans '<DataPrime>'. See references/ai-center-queries.md for the full, runnable query library, span schema, and playbooks.
Match the source to the question: "which apps lack guardrails" → config
(cx ai-center applications list); "what are users asking my chatbot" → telemetry
(cx spans '…', reading the conversation from the GenAI spans). Some questions need both —
e.g. "is my chatbot's PII policy actually catching PII?" joins config (is the policy enabled)
with telemetry (the PII verdicts + the messages).
Destructive Operation Safety
All write operations (create, update, delete, add, remove, set)
require interactive confirmation. ai-center is a risky command, so writes are also
gated by allow_risky_commands in ~/.cx/config.toml. To skip the prompt in scripts, pass
--yes.
IMPORTANT: NEVER pass --yes without explicit user approval. Before executing any write:
- Describe the exact operation to the user (what will be created/modified/deleted/linked).
- Wait for the user to confirm.
- Only then execute with
--yes.
Read operations (list, get, coverage, list-for-application, model-pricing get) do
not require confirmation and can be run freely.
Read-Only Mode
Use --read-only (or CX_READ_ONLY=1) to block every write at the CLI level — safe for
exploration.
Agent Mode
When running inside an AI agent (Claude Code, Cursor, Codex, …), cx detects it and — instead of
showing a confirmation prompt that would hang forever (no human is there to type y/n) — stops
immediately with an error telling you to get the user's approval, then re-run with --yes.
No delete commands (by design)
The CLI intentionally exposes no delete for custom-evaluation policies, AI applications, or
model pricing — even though the AI v3 API has those delete endpoints, cx ai-center does not
surface them.
- Custom-evaluation policy: can't be deleted; to take it off an app, detach with
custom-evaluations remove(the policy object survives and can be re-attached). - Model pricing: no delete command. It's team-wide (not per-app), so to change or clear
it, run
model-pricing setwith a new map (an empty map{}clears all overrides) —setreplaces the whole set.
Golden rule
For content questions (quality, hallucination, sentiment, topics) read the actual
conversation and cite the traceID — don't rely on verdict tags alone. The transcript lives in
one of two conventions (gen_ai.input.messages/output.messages, or the older indexed
gen_ai.prompt.<n>/completion.<n> tags); read it with the Reading conversations (content
questions) queries in the library, which handle both and exclude the system prompt and tool
traffic. Full guidance:
references/ai-center-queries.md.
CLI Commands
Show names to the user; use UUIDs only internally. When presenting results, refer to apps
and evaluations by their human names (application/subsystem, evaluation name), not raw UUIDs.
The UUID is only needed to call a by-id or write command — resolve it yourself from the
matching list command (never guess or make the user paste a UUID).
Applications (inventory + guarded status)
| Command | Purpose |
|---|---|
cx ai-center applications list | List AI apps incl. guardrailsIntegrated (guarded) status |
cx ai-center applications list --evaluation-type <TYPE> | Filter to apps using an eval type (repeatable) |
cx ai-center applications list --page-size <N> --page-offset <N> | Paginate |
cx ai-center applications get <application-id> | One application by UUID |
Evaluations (configured policies on apps)
| Command | Purpose |
|---|---|
cx ai-center evaluations list | All configured evaluations |
cx ai-center evaluations list --application <app> --subsystem <sub> | Scope to one app (the pair) |
cx ai-center evaluations list --evaluation-type <TYPE> | Filter by type — <TYPE> is the API enum (e.g. PII, TOXICITY, PROMPT_INJECTION; the keys from coverage), not the lowercase form |
cx ai-center evaluations get <evaluation-id> | One evaluation by UUID |
cx ai-center evaluations create --from-file eval.json | Create/enable an evaluation (write) |
cx ai-center evaluations update <evaluation-id> --from-file patch.json | Partial update (write) |
cx ai-center evaluations delete <evaluation-id> | Remove an evaluation from its app (write) |
Custom evaluations (policies) & application links
| Command | Purpose |
|---|---|
cx ai-center custom-evaluations list | All custom evaluation policies |
cx ai-center custom-evaluations list-for-application <application-id> | Policies linked to one app |
cx ai-center custom-evaluations create --from-file policy.json | Create a custom policy (write) |
cx ai-center custom-evaluations update <id> --from-file patch.json | Partial update (write) |
cx ai-center custom-evaluations add <evaluation-id> <application-id> | Attach a policy to an app (write) |
cx ai-center custom-evaluations remove <evaluation-id> <application-id> | Detach (reversible) (write) |
By-id is prebuilt-only.
evaluations get <id>fetches a prebuilt/configured evaluation. Custom policies have no get-by-id — find one viacustom-evaluations list/list-for-applicationand match byid/name.
Coverage & model pricing
| Command | Purpose |
|---|---|
cx ai-center coverage | Map of each evaluation type → number of apps using it (coverage / gap analysis) |
cx ai-center model-pricing get | Team's custom per-model pricing overrides |
cx ai-center model-pricing set --from-file prices.json | Set team pricing (team-wide, new data only) (write) |
The --from-file bodies for evaluations and custom-evaluations match the AI v3 API
shape verbatim; use - to read JSON from stdin. For evaluations create, target is
required and must be uppercase (PROMPT or RESPONSE); for custom-evaluations create,
name, instructions, and policyType are required. Exception: model-pricing set takes just
the raw model→price map — cx wraps it as {"prices": …} for you, so do not include the
outer prices envelope. Each model maps to a price object; all four fields are optional doubles
(USD per one million tokens), omit the ones that don't apply:
{
"gpt-4o": {
"inputPricePerMillionTokens": 2.5,
"outputPricePerMillionTokens": 10,
"cacheReadPricePerMillionTokens": 1.25,
"cacheWritePricePerMillionTokens": 3.75
}
}
An empty map {} clears all overrides (set replaces the whole set — it's team-wide, new data only).
model-pricing get returns the wrapper { "pricing": { "id", "companyId", "prices": { … } } } — the
per-model overrides live under prices (empty when none are set).
Common workflows
Inventory & guardrail gaps
# Which apps are NOT guarded?
cx ai-center applications list -o json | jq '[.[] | select(.guardrailsIntegrated==false)]'
Enable a policy on an app (write — confirm first!)
# 1. Describe to the user; 2. get approval; 3. then:
cx ai-center evaluations create --from-file eval.json --yes
# eval.json: { "application": "...", "subsystem": "...", "target": "PROMPT", "config": { "<type>": {...} }, "isEnabled": true }
# `target` is REQUIRED and must be UPPERCASE — "PROMPT" or "RESPONSE" (the API rejects lowercase / a missing target).
Read the actual conversations (telemetry, not config)
Use cx spans with the query library in
references/ai-center-queries.md — reading messages, cost,
latency, errors, tool calls, and per-user analysis.
Key principles
- Config vs. telemetry: inventory / evaluations / policies / coverage / pricing →
cx ai-center; content / cost / latency / errors / verdicts → GenAI spans viacx spans. Don't answer one from the other. - Confirm before writes. Describe the operation, get approval, then run with
--yes.
Related Skills
cx-telemetry-querying— general logs/spans/metrics/DataPrime querying (the engine behind thecx spansqueries used here).cx-olly— the conversational AI assistant (cx olly ask).
FAQ
What does the cx-ai-center skill do?
Use this skill for any question or action about the user's AI/GenAI applications or agents — their behavior, prompts/responses, quality, hallucinations, guardrails, security, cost/tokens, errors, evaluations/policies, model pricing, or configuration — including comparing or tracking agents over time. It covers both analyzing AI telemetry (GenAI spans) and managing AI Center config via the cx ai-center commands.
How do I install cx-ai-center?
Run npx skills add https://github.com/coralogix/cx-cli --skill cx-ai-center 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-ai-center/ (personal) or .claude/skills/cx-ai-center/ (project).
Which AI agents can use cx-ai-center?
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-ai-center 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-ai-center?
It is published by coralogix in coralogix/cx-cli. It has 2,313 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 ai & agents skills
google-agents-cli-publish
google/agents-cli
This skill should be used when the user wants to "publish an agent", "publish my ADK agent", "register an agent with Gemini", "publish to Gemini" (formerly Gemini Enterprise), or needs guidance on the agents-cli publish gemini command. Also use when the user wants to "manage agents in Agent Registry", "list/update/delete registered agents", or "register an MCP server". Covers ADK vs A2A registration modes, programmatic and interactive usage, flag reference, auto-detection from deployment metadata, Agent Registry fleet management, and troubleshooting. Part of the agents-cli skills suite. Do NOT use for deployment (use google-agents-cli-deploy).
google-agents-cli-eval
google/agents-cli
This skill should be used when the user wants to "run an evaluation", "evaluate my agent", "evaluate my ADK agent", "write an eval dataset", "analyze eval failures", "compare eval results", "optimize agent", or needs guidance on the Gemini platform eval methodology and the Quality Flywheel. Covers eval metrics, dataset schema, LLM-as-judge scoring, and common failure causes. Applies to any agents-cli project, whatever framework the agent is written in. Do NOT use for agent API code patterns (ADK: use google-agents-cli-adk-code), deployment (use google-agents-cli-deploy), or project scaffolding (use google-agents-cli-scaffold).
skill-creator
anthropics/skills
Create new skills, modify and improve existing skills, and measure skill performance. Use when users want to create a skill from scratch, edit, or optimize an existing skill, run evals to test a skill, benchmark skill performance with variance analysis, or optimize a skill's description for better triggering accuracy.
codex-pet
prime-skills/runcomfy-agent-skills
Codex Pet generator on RunComfy. Build a Codex-compatible Codex Pet spritesheet.webp + pet.json from a single reference image, drop it into ${CODEXHOME:-$HOME/.codex}/pets/ / and Codex picks it up as a custom Codex Pet next to the 8 built-ins. This skill produces the exact Codex Pet atlas Codex expects (1536x1872 PNG/WebP, 8 cols x 9 rows, 192x208 cells, 9 animation states — idle, running-right, running-left, waving, jumping, failed, waiting, running, review). Calls OpenAI GPT Image 2 edit ONCE via the local RunComfy CLI as runcomfy run openai/gpt-image-2/edit to produce a canonical Codex Pet pose, then assembles all 9 animation rows programmatically with ImageMagick micro-transforms — no Codex Pro, no $imagegen, no OPENAIAPIKEY required, only RUNCOMFYTOKEN. Triggers on "codex pet", "create codex pet", "make codex pet", "hatch codex pet", "/hatch image", "desktop pet codex", "codex pets", "spritesheet.webp", or any explicit ask to build a custom pet for OpenAI Codex.
full-output-enforcement
leonxlnx/taste-skill
Overrides default LLM truncation behavior. Enforces complete code generation, bans placeholder patterns, and handles token-limit splits cleanly. Apply to any task requiring exhaustive, unabridged output.
executing-plans
obra/superpowers
Use when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is available