CtrlK
BlogDocsLog inGet started
Tessl Logo

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.

70

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.

A well-organized routing skill body with executable commands, concrete query patterns, and clean one-level-deep references to real bundle files. It is slightly verbose in places and its validation checkpoints are light, but the read-only nature of the commands mitigates the latter.

DimensionReasoningScore

Conciseness

The body is lean and well-structured with tables and code snippets, assuming Claude's competence without explaining what PromQL or spans are; a few prose passages in Cross-Agent Questions and Answer Style could be tightened, keeping it just below the score-5 anchor.

4 / 5

Actionability

It provides copy-paste-ready commands (e.g. `cx metrics search --name '<pattern>'`, `cx logs '<dataprime_query>'`) plus concrete PromQL and DataPrime filter patterns and exact source identifiers, covering the common per-agent cases fully.

5 / 5

Workflow Clarity

The First Response and Loading References sections give a clear sequence (identify agent and goal, ask for missing scope before querying, load agent ref then shared refs) with the 'ask before querying' checkpoint; because all commands are read-only the destructive-validation cap does not apply, but validation checkpoints are otherwise light.

4 / 5

Progressive Disclosure

The body acts as an overview/routing document with a clear Loading References table that signals one-level-deep references (e.g. references/claude-code.md, references/promql-guidelines.md), all of which exist as real files, with content appropriately split and easy to navigate.

5 / 5

Total

18

/

20

Passed

Description

86%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, trigger-rich description that clearly scopes a niche product domain with comprehensive natural keywords and an explicit 'Use when' clause. Its only weakness is that capabilities are framed as user intents rather than the skill's own actions.

DimensionReasoningScore

Specificity

The description lists several concrete topics (usage, cost, tokens, sessions, tools, code impact, users, models, spans, logs) and use cases ('reproduce or extend the Coding Agents dashboards'), but frames them as user intents rather than the skill's own capabilities, leaving minor gaps versus the score-5 anchor.

4 / 5

Completeness

It has an explicit 'Use this skill when...' trigger clause and a clear domain ('AI Center Coding Agents data'), answering both what and when; however the 'what' is expressed as user requests ('asks about', 'wants to reproduce') rather than concrete skill actions, so it falls just short of the score-5 anchor.

4 / 5

Trigger Term Quality

It comprehensively covers natural terms users would say — usage, cost, tokens, sessions, models, spans, logs — plus all five agent names (Claude Code, Codex, Cursor, Gemini CLI, Copilot CLI) and 'dashboards', giving strong keyword coverage with synonyms.

5 / 5

Distinctiveness Conflict Risk

The niche is sharply defined by the product name 'AI Center Coding Agents' and an explicit list of five coding agents, making it highly distinct with minimal risk of triggering for unrelated skills.

5 / 5

Total

18

/

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.

Validation15 / 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
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.