CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

cx-coding-agents

Use this skill 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, tools, code impact, users, models, spans, or logs for Claude Code, Codex, Cursor, Gemini CLI, or Copilot CLI.

Quality

86%

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

86%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.

An excellent instruction-only skill body: token-efficient, dense with non-obvious operational knowledge (source identifiers, label casing, unit normalization), and backed by a clean one-level-deep reference bundle that fully matches its citations. The only gaps are the absence of a complete assembled example query per data source and an explicit error-recovery path for empty or failed queries.

Suggestions

Add one fully assembled example per data source (e.g. cx logs 'source ai_sessions_claude | filter $l.applicationname == \'x\' | groupby $l.user | count') so a first-time user has a copy-paste-complete query, which would close the actionability gap.

Add a short error-recovery note for empty or failed query results (e.g. run cx metrics search to discover the metric family, or verify label names) to give the workflow an explicit validate/fix/retry loop.

DimensionReasoningScore

Conciseness

The body is lean tables and terse bullets with zero padding — it never explains concepts Claude already knows (no 'what is PromQL/OTel' preamble) and concentrates entirely on non-obvious, skill-specific facts like source identifiers, the '$l.applicationName' vs '$l.applicationname' casing trap, and unit normalization caveats. Every token earns its place, matching anchor 5 ('lean and efficient; assumes Claude's competence').

5 / 5

Actionability

Guidance is highly concrete: exact CLI commands ('cx metrics search --name \'<pattern>\'', 'cx logs \'<dataprime_query>\''), exact source identifiers ('service.name == \'codex_cli_rs\''), and copy-paste filter patterns in code blocks. It falls short of anchor 5 only because no fully assembled end-to-end example query is shown — the PromQL snippet and the '| filter $l.applicationName == ...' pattern are fragments, not complete runnable queries — leaving it at anchor 4 ('mostly executable guidance; concrete code or commands with minor gaps').

4 / 5

Workflow Clarity

The sequence is clear and well-ordered: identify agent and goal (First Response, with an explicit ask-before-querying checkpoint), load the mapped reference files, use the dashboard-matching data source, apply time/filters, then follow the answer checklist with caveats. Checkpoints are present (ask when scope is missing, mandatory caveats about empty data and missing labels), and the Safety section confirms all commands are read-only so no destructive-operation validation cap applies. It sits at anchor 4 rather than 5 because there is no explicit error-recovery loop for failed or empty queries — only the after-the-fact caveat requirement, not a validate/fix/retry step.

4 / 5

Progressive Disclosure

SKILL.md is a pure overview/router: the 'Loading References' table maps every agent to the exact files to load, all 10 referenced files exist in references/, and they are one level deep — the only cross-references are sibling files already enumerated in the table, with no buried chains. Verified against the actual bundle structure, this matches anchor 5 ('clear overview with well-signaled one-level-deep references; easy navigation').

5 / 5

Total

18

/

20

Passed

Description

81%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 excellent, comprehensive trigger terms and a well-defined niche that minimizes conflict risk. Its main weakness is that the skill's capabilities are expressed indirectly through user scenarios rather than explicit statements of what the skill does, leaving the 'what' slightly implicit.

Suggestions

Add one explicit capability statement in third person, e.g. 'Identifies the data source for each coding agent and runs the corresponding cx metrics/logs/spans queries' — this would lift the indirect 'what' and raise specificity and completeness.

State the distinguishing operation up front (routing to per-agent reference files and querying via the cx CLI) so the description answers 'what does this do' without requiring inference from trigger scenarios.

DimensionReasoningScore

Specificity

The description names the domain precisely ('AI Center Coding Agents data', 'Coding Agents dashboards') and enumerates data subjects ('usage, cost, tokens, sessions, tools, code impact, users, models, spans, or logs'), but the skill's own concrete actions are limited to 'reproduce or extend the Coding Agents dashboards' — what the skill actually does (identify data sources, load references, run queries) is never stated. This matches anchor 3 ('names domain and 1-2 concrete actions, but not comprehensive') better than anchor 4, which expects several listed specific actions; the richness here is in trigger enumeration rather than capability enumeration.

3 / 5

Completeness

The 'when' is explicit and strong ('Use this skill when the user asks about...'), but the 'what' is only conveyed indirectly through user scenarios ('wants to reproduce or extend the Coding Agents dashboards') rather than an explicit statement of the skill's function. Anchor 4 ('has both what and when; when could be more explicit') fits: the when here is actually better than anchor 4's example, but anchor 5 requires both what AND when explicitly, and the what is inferred, not stated.

4 / 5

Trigger Term Quality

It comprehensively covers natural terms users would say — 'usage, cost, tokens, sessions, tools, code impact, users, models, spans, or logs' — alongside every product name ('Claude Code, Codex, Cursor, Gemini CLI, or Copilot CLI'). This matches anchor 5's 'comprehensive coverage of natural terms including synonyms'; nothing common is missing.

5 / 5

Distinctiveness Conflict Risk

It carves out a clear niche ('AI Center Coding Agents data', 'Coding Agents dashboards') with distinct triggers (five named agent products and specific signal types). It would not plausibly fire for an unrelated skill, matching anchor 5's 'clear niche with distinct triggers; minimal conflict risk' — clearly above anchor 4's 'minor overlap risk with closely related skills'.

5 / 5

Total

17

/

20

Passed

Validation

93%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

metadata_field

'metadata' should map string keys to string values

Warning

Total

15

/

16

Passed

Repository

coralogix/cx-cli

Path

skills/cx-coding-agents/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.