CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

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.

Quality

88%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Low

Low-risk findings worth noting

SKILL.md
Quality
Evals
Security

Quality

Content

88%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A well-structured, highly actionable command reference with explicit safety validation for destructive writes and clean delegation of bulk query detail to a reference file. Its only flaws are repeated statements of the same API quirks (target-uppercase, empty-map clearing) and a second-hop reference chain that keeps disclosure from being perfectly one level deep.

DimensionReasoningScore

Conciseness

The body is dense with cx-specific facts (command tables, flag semantics, API quirks) and explains nothing Claude already knows, but there is noticeable duplication: "`target` is REQUIRED and must be UPPERCASE" appears in both the CLI Commands section and the Common workflows section, and the empty-map-`{}`-clears note for model pricing is stated twice. These repeats could be trimmed, matching 'minor instances of over-explanation' rather than the every-token-earns-its-place anchor.

4 / 5

Actionability

Fully executable guidance throughout: complete command tables with flags (`cx ai-center evaluations list --evaluation-type <TYPE>`), a copy-paste bash pipeline (`cx ai-center applications list -o json | jq '[.[] | select(.guardrailsIntegrated==false)]'`), a concrete model-pricing JSON example, and an eval.json body shape with required fields. Common cases are covered by specific examples, with the bulk query detail correctly delegated to the reference file.

5 / 5

Workflow Clarity

The destructive-write path has an explicit validation sequence — "1. Describe the exact operation… 2. Wait for the user to confirm. 3. Only then execute with `--yes`" — plus an error-recovery loop for agent mode (CLI stops with an error telling you to get approval, then re-run with `--yes`), and the config-vs-telemetry decision rule is illustrated with worked question examples. The destructive-operation cap does not apply because validation checkpoints are present and explicit.

5 / 5

Progressive Disclosure

Good structure: SKILL.md is a genuine overview, and the full query library/span schema/playbooks live in references/ai-center-queries.md, pointed to four times with clear signaling. Not a 5 because navigation is not strictly one level deep — ai-center-queries.md itself routes to dataprime-reference.md and spans-querying.md, and those two files are never surfaced from SKILL.md directly, a minor organization gap.

4 / 5

Total

18

/

20

Passed

Description

83%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A strong description with an explicit 'Use this skill for…' trigger clause, a clear two-part capability statement (telemetry analysis + config management), and a rich set of natural trigger terms. The only weaknesses are a topic-enumeration style instead of distinct concrete actions and slight over-breadth in the 'any question or action' framing.

DimensionReasoningScore

Specificity

Names concrete capabilities — "analyzing AI telemetry (GenAI spans)", "managing AI Center config via the `cx ai-center` commands", "comparing or tracking agents over time" — with a comprehensive topic inventory (prompts/responses, hallucinations, guardrails, cost/tokens, model pricing). Not a 5 because the framing "any question or action about" is topical enumeration rather than a list of multiple distinct concrete actions.

4 / 5

Completeness

Explicitly answers both: what — "covers both analyzing AI telemetry (GenAI spans) and managing AI Center config via the `cx ai-center` commands" — and when — the leading "Use this skill for any question or action about the user's AI/GenAI applications or agents" clause with concrete trigger topics. Both are explicit and concrete, matching the top anchor; a missing/weak 'when' clause would have capped it at 3.

5 / 5

Trigger Term Quality

Good coverage of natural terms users would say: "hallucinations", "guardrails", "quality", "cost/tokens", "errors", "model pricing", "AI/GenAI applications", "agents". A few common variations are missing (e.g. "chatbot", "LLM app", "token usage"), which keeps it below the comprehensive-synonym anchor of 5.

4 / 5

Distinctiveness Conflict Risk

Clear niche (Coralogix AI Center, GenAI spans, `cx ai-center`) distinct from generic skills, and the AI/GenAI scoping separates it from the sibling `cx-telemetry-querying` skill. Slight over-breadth remains — "any question or action about the user's AI/GenAI applications" could fire on general LLM-development questions outside this tool's scope — so minor overlap risk rather than minimal.

4 / 5

Total

17

/

20

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 — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository

coralogix/cx-cli

Path

skills/cx-ai-center/SKILL.md

Reviewed

Table of Contents

Is this your skill?

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.