CtrlK
BlogDocsLog inGet started
Tessl Logo

context-xray

Visualize local Codex and Claude Code context usage, open a report, flag warnings, and suggest prompt/tooling optimizations.

60

Quality

76%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/context-xray/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

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

The body is a concise, well-structured, self-contained guide with fully executable commands covering install and the common run modes. Its main gaps are the absence of any failure/verification handling around the external command and an underspecified post-run summarization step.

Suggestions

Add one line of fallback guidance for when the context-xray command is not found (e.g., re-run the npx install or verify PATH).

Make the post-run step concrete: point to which part of the generated HTML report contains sessions, context buckets, and warnings so the summary is grounded in actual output.

Trim the defensive clarifications about hosted auth and background servers unless they address a real user confusion.

DimensionReasoningScore

Conciseness

The body is lean and assumes competence — no concept explanations, just install and run commands. Two sentences could be trimmed: "It does not need hosted auth or a remote MCP connector to read local transcript files" and "it does not keep a background server running" are defensive clarifications with marginal value. This matches level 4 ('Efficient; minor instances of over-explanation that could be trimmed') rather than level 5, where every token earns its place.

4 / 5

Actionability

Concrete, copy-paste-ready commands are provided for every common case: install ("npx @agent-native/core@latest skills add context-xray --client all"), current thread ("context-xray --open"), picker ("context-xray threads --open"), and trends ("context-xray trends --since 7d --open"). It stops short of level 5 because the post-run instruction ("summarize the report link, sessions analyzed, largest context buckets, warnings, and concrete optimizations") gives no guidance on where to find these details in the report or what to do if the command is missing or fails.

4 / 5

Workflow Clarity

The Setup → Run → summarize sequence is clear and unambiguous with labeled sections and per-command examples. It does not reach level 5 because there are no checkpoints or error-recovery guidance (e.g., verifying the command installed successfully before running), and the final summarize step is a single underspecified instruction. No validation cap applies since the operations are read-only and non-destructive.

4 / 5

Progressive Disclosure

No bundle files exist (references/, scripts/, assets/ are all absent), so the skill is entirely self-contained — and appropriately so for a simple, single-purpose tool skill. The body is a compact ~54-line overview organized into well-labeled sections (Setup, Run) with no content that belongs in separate reference files, matching the simple-skill pattern where well-organized sections alone merit a 5.

5 / 5

Total

17

/

20

Passed

Description

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

The description is specific, third-person, and lists concrete capabilities, but it omits any explicit 'use when' trigger guidance and lacks common synonym/variation trigger terms (context window, token usage). Adding a 'Use when...' clause with natural trigger phrases would lift completeness and trigger-term quality to the top anchors.

Suggestions

Append a 'Use when' clause, e.g. 'Use when a Codex or Claude Code session is getting long, the user asks where context or tokens are going, or wants to reduce context usage.'

Add natural synonym trigger terms such as 'context window', 'token usage', and 'transcript' so the description matches how users actually phrase the request.

Clarify that it works on local session/transcript files to sharpen distinctiveness from generic prompt-optimization skills.

DimensionReasoningScore

Specificity

Quotes: "Visualize local Codex and Claude Code context usage", "open a report", "flag warnings", "suggest prompt/tooling optimizations" — four concrete actions in third-person voice with comprehensive coverage of the tool's capabilities. This matches the level-5 anchor ('Lists multiple specific concrete actions; comprehensive coverage') and exceeds level 4, which would leave coverage gaps.

5 / 5

Completeness

The 'what' is clear and concrete ("Visualize local Codex and Claude Code context usage, open a report, flag warnings, and suggest prompt/tooling optimizations") but there is no 'Use when...' clause or equivalent explicit trigger guidance in the description. Per the judging guidelines, a missing 'when' clause caps completeness at 3, matching the anchor 'Has a clear what but when is missing or only weakly implied'.

3 / 5

Trigger Term Quality

Relevant keywords like "Codex", "Claude Code", "context usage", "report", and "warnings" are present, but common natural variations users would actually say are missing ("context window", "token usage", "where is my context going", "transcripts"). This fits the level-3 anchor ('Some relevant keywords but missing common variations or synonyms'); it is above level 2 (which would have only generic keywords) but below level 4's 'good keyword coverage'.

3 / 5

Distinctiveness Conflict Risk

Naming the specific clients ("local Codex and Claude Code context usage") carves out a clear niche distinct from generic context or prompt-engineering skills, matching 'Mostly distinct; minor overlap risk'. It falls short of level 5 because the phrase "suggest prompt/tooling optimizations" could mildly overlap with general prompt-optimization or context-management skills.

4 / 5

Total

15

/

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_version

'metadata.version' is missing

Warning

Total

15

/

16

Passed

Repository
BuilderIO/agent-native
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.