Agent skill

Cx AI Center

by coralogix in 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…

Apache-2.0Auto-check passedAI & LLM Engineering

Install Cx AI Center

skills CLI
$ npx skills add coralogix/cx-cli --skill cx-ai-center -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install coralogix/cx-cli cx-ai-center --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/coralogix/cx-cli.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/cx-ai-center .claude/skills/cx-ai-center && rm -rf skills-src

Use ~/.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/

Facts

Skill name
cx-ai-center
GitHub stars
121
Token cost
~2.5k tokens
SKILL.md length
1,075 words
Files
4 (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 or action about the user's AI/GenAI applications or agents — their behavior, prompts/responses, quality, hallucinations, guardrails, security, cost/tokens…

  • Works in 3 steps: Describe the exact operation to the user… → Wait for the user to confirm. → Only then execute with --yes.
  • Action about the users AI/GenAI applications
  • SKILL.md covers Destructive Operation Safety, Golden rule, CLI Commands and Common workflows, plus 2 more sections
  • Calls jq

What it does

Cx AI Center is an agent skill from coralogix/cx-cli. 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.

Its SKILL.md is about 2.5k tokens, which your agent loads only when the skill is triggered. The skill folder holds 4 other files, including reference files (for example `references/ai-center-queries.md`, `references/dataprime-reference.md` and `references/spans-querying.md`).

It sits in AI & LLM Engineering, covering LLM guardrails. The repository describes itself as: This is the Coralogix CLI. The licence is Apache-2.0.

When your agent uses it

  • Action about the users AI/GenAI applications
  • Agents — their behavior
  • Prompts/responses
  • Evaluations/policies

Example prompts

  • “/cx-ai-center”

Workflow steps

3 steps, taken from the first numbered list in SKILL.md.

  1. Describe the exact operation to the user (what will be created/modified/deleted/linked).
  2. Wait for the user to confirm.
  3. Only then execute with --yes.

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

    Shell commands in SKILL.md call:

    • jq

    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 AI Center loads about 2.5k tokens when it runs, and up to ~17k if it reads all its reference files. Until then it costs about 107 tokens; SKILL.md has 1,075 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~107
When it runs · the whole SKILL.md, loaded when a task matches
~2.5k
With references · SKILL.md plus every file in references/, read only if the agent opens them
~17k

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,075 words, ~2,470 tokens.

Download SKILL.mdSave it as .claude/skills/cx-ai-center/SKILL.md (or your agent's skills folder). This skill also uses 3 other files; get the full folder from GitHub.
name
cx-ai-center
description
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.
metadata.version
0.1.0

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-center commands): 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:

  1. Describe the exact operation to the user (what will be created/modified/deleted/linked).
  2. Wait for the user to confirm.
  3. 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 set with a new map (an empty map {} clears all overrides) — set replaces 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)
CommandPurpose
cx ai-center applications listList 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
Show full SKILL.md (461 more words)Show less
Evaluations (configured policies on apps)
CommandPurpose
cx ai-center evaluations listAll 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.jsonCreate/enable an evaluation (write)
cx ai-center evaluations update <evaluation-id> --from-file patch.jsonPartial update (write)
cx ai-center evaluations delete <evaluation-id>Remove an evaluation from its app (write)
CommandPurpose
cx ai-center custom-evaluations listAll 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.jsonCreate a custom policy (write)
cx ai-center custom-evaluations update <id> --from-file patch.jsonPartial 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 via custom-evaluations list / list-for-application and match by id/name.

Coverage & model pricing
CommandPurpose
cx ai-center coverageMap of each evaluation type → number of apps using it (coverage / gap analysis)
cx ai-center model-pricing getTeam's custom per-model pricing overrides
cx ai-center model-pricing set --from-file prices.jsonSet 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:

json
{
  "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
bash
# 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!)
bash
# 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 via cx spans. Don't answer one from the other.
  • Confirm before writes. Describe the operation, get approval, then run with --yes.

  • cx-telemetry-querying — general logs/spans/metrics/DataPrime querying (the engine behind the cx spans queries used here).
  • cx-olly — the conversational AI assistant (cx olly ask).

© 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 3 other files (references) in skills/cx-ai-center of coralogix/cx-cli.

  • SKILL.md
  • references/ai-center-queries.md
  • references/dataprime-reference.md
  • references/spans-querying.md

Open the folder on GitHubat commit c071372

Compare with similar skills

Cx AI Center 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.

Cx AI Center compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Cx AI Center this skillcoralogix/cx-cli121—~2.5kAutomated safety check: PassApache-2.0
Aisafetyhotwuyoscar/AISafetyHot-Hub827—~1.4kAutomated safety check: PassCustom licence
ObliteratusRedWoodOG/Hermes-Desktop1775 repos~3.8kAutomated safety check: PassMIT
Lemonade Router Builderamd/skills408—~4kAutomated safety check: PassMIT
Writing Eval Scenariosopen-bias/open-bias143—~1.5kAutomated safety check: PassApache-2.0
Wp Project Triagegambitph/Stackable3513 repos~371Automated safety check: PassGPL-3.0

Similar skills

  • Aisafetyhot

    wuyoscar/AISafetyHot-Hub

    Query AI Safety HOT news, research papers, incidents, hot topics, and daily/weekly/monthly reports through its public read-only MCP service.

    827 GitHub stars~1.4k tokensUpdated today
    AI & LLM EngineeringAuto-check passed
  • Obliteratus

    RedWoodOG/Hermes-Desktop

    Remove refusal behaviors from open-weight LLMs using OBLITERATUS — mechanistic interpretability techniques (diff-in-means, SVD, whitened SVD, LEACE, SAE decomposition, etc.) to excise guardrails…

    177 GitHub starsUsed in 5 repos~3.8k tokens
    AI & LLM EngineeringAuto-check passed
  • Turns a natural-language description of routing intent into a valid Lemonade collection.router policy JSON.

    408 GitHub stars~4k tokensUpdated yesterday
    AI & LLM EngineeringAuto-check passed
  • Writing Eval Scenarios

    open-bias/open-bias

    Guide for writing eval conversation JSONs and running them through policy engines

    143 GitHub stars~1.5k tokensUpdated 4 days ago
    AI & LLM EngineeringAuto-check passed
  • Wp Project Triage

    gambitph/Stackable

    A skill your agent uses when you need a deterministic inspection of a WordPress repository (plugin/theme/block theme/WP core/Gutenberg/full site) including tooling/tests/version hints, and a…

    351 GitHub starsUsed in 3 repos~371 tokens
    AI & LLM EngineeringAuto-check passed
  • Wa Guardrails

    aws-samples/sample-well-architected-skills-and-steering

    Official

    Generate preventive Well-Architected guardrails — AWS Config rules, Service Control Policies, permission boundaries, CloudWatch alarms, and IaC policy checks (CDK Aspects, cfn-guard, OPA/Sentinel) —…

    275 GitHub stars~2.8k tokensUpdated 5 days ago
    AI & LLM EngineeringAuto-check passed

More from coralogix/cx-cli

All 21 skills in this repo
  • 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"…

    121 GitHub stars~2.5k tokensUpdated 4 days ago
    Auto-check passed
  • 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…

    121 GitHub stars~1.8k tokensUpdated 4 days ago
    Auto-check passed
  • 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"…

    121 GitHub stars~3.4k tokensUpdated 4 days ago
    Auto-check passed
  • 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…

    121 GitHub stars~3k tokensUpdated 4 days ago
    Auto-check passed
  • Cx Telemetry Querying

    coralogix/cx-cli

    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"…

    121 GitHub stars~2.6k tokensUpdated 4 days ago
    Auto-check passed
  • Cx Dashboards

    coralogix/cx-cli

    Build and deploy a Coralogix dashboard for a given service from its logs, spans, metrics, and service specs.

    121 GitHub stars~4.7k tokensUpdated 4 days ago
    Auto-check: warnings

Questions about Cx AI Center

What does Cx AI Center do?

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 AI Center is an agent skill from coralogix/cx-cli. 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.

When should I use Cx AI Center?

Cx AI Center fits situations like: action about the users AI/GenAI applications; agents — their behavior; prompts/responses; evaluations/policies.

How do I install Cx AI Center in Claude Code?

Run `npx skills add coralogix/cx-cli --skill cx-ai-center -a claude-code`. Or copy the skill folder (skills/cx-ai-center in coralogix/cx-cli) into .claude/skills/cx-ai-center in your project. Claude Code loads it when a task matches its description.

How do I install Cx AI Center in Codex?

Run `npx skills add coralogix/cx-cli --skill cx-ai-center -a codex`. Or copy the skill folder (skills/cx-ai-center in coralogix/cx-cli) into .agents/skills/cx-ai-center in your project. Codex loads it when a task matches its description.

Can I use Cx AI Center 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-ai-center -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-ai-center, .gemini/skills/cx-ai-center, .github/skills/cx-ai-center and .opencode/skills/cx-ai-center in your project.

What does Cx AI Center need to run?

Going by SKILL.md and its folder, Cx AI Center needs the command-line tools its instructions call (jq).

Does Cx AI Center 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 AI Center 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 AI Center use?

Cx AI Center 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 AI Center use?

About 2.5k tokens (SKILL.md is roughly 9.9k 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 14k tokens, read only when the agent opens those files.

What are the alternatives to Cx AI Center?

Skills that share tags, products or a category with Cx AI Center: Aisafetyhot (wuyoscar/AISafetyHot-Hub, 827 stars), Obliteratus (RedWoodOG/Hermes-Desktop, 177 stars), Lemonade Router Builder (amd/skills, 408 stars) and Writing Eval Scenarios (open-bias/open-bias, 143 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Cx AI Center?

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.