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.

55

Quality

62%

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 content is lean, well-structured, and executable, with a clear Setup/Run/Summarize flow suited to a simple single-purpose skill. The main gap is the absence of an explicit summarization checklist and a hint of what the report contains.

DimensionReasoningScore

Conciseness

The body is efficient and assumes competence — install command, run commands, and a one-line note on --open — with only minor phrasing that could be trimmed, fitting the 4 anchor.

4 / 5

Actionability

Provides concrete, executable commands for the common cases (install, --open, threads, trends) with minor gaps such as missing flag help and no description of what the report contains.

4 / 5

Workflow Clarity

A clear Setup -> Run -> summarize sequence with the --open behavior explained; the skill is non-destructive so the simple-skill exception applies, but it is not 5 because the summarize step lacks an explicit checklist.

4 / 5

Progressive Disclosure

A well-organized skill under 50 lines with clear sections and no need for external references, matching the simple-skill scoring note for a 5.

5 / 5

Total

17

/

20

Passed

Description

46%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 states concrete capabilities and a clear niche but omits any explicit trigger ('Use when...') clause and relies on technical jargon rather than natural user phrasing. It is solid but not exemplary.

Suggestions

Add a 'Use when...' clause naming natural triggers, e.g. 'Use when a coding-agent thread feels large or you want to know where context is going.'

Swap jargon for natural keywords users would say, such as 'context window', 'token usage', or 'thread size'.

Expand the capability list slightly to be more comprehensive (e.g. mention sessions/buckets) so specificity reaches the 4-5 band.

DimensionReasoningScore

Specificity

Names the domain and several concrete actions ('Visualize...context usage, open a report, flag warnings, and suggest...optimizations'), but coverage is moderate rather than comprehensive, matching the 3 anchor.

3 / 5

Completeness

There is a clear 'what' but no explicit 'Use when...' trigger clause, so per the guideline completeness is capped at 3.

3 / 5

Trigger Term Quality

Terms like 'context usage' and 'tooling optimizations' are technical jargon; it lacks the natural phrases a user would actually say (e.g. 'context window', 'where is my context going'), fitting the 2 anchor.

2 / 5

Distinctiveness Conflict Risk

Scoping to 'Codex and Claude Code context usage' gives it a clear niche with only minor overlap risk against general debugging/profiling skills, matching the 4 anchor.

4 / 5

Total

12

/

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_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.