CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

context-xray

Inspect and manage the live agent context window with Context X-Ray. Use when context is getting large, the user asks what is in context, or stale tool results/files should be pinned, evicted, restored, or reported by an external host.

Quality

83%

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

SKILL.md
Quality
Evals
Security

Quality

Content

75%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, actionable instruction-only skill: concrete tool names, exact field names, a clear workflow, and meaningful safety rules. The main improvements are trimming host-UI narration from System Sections, making the pre-evict protected-segment check an explicit flow step, and externalizing the provenance-label reference detail.

Suggestions

Trim host-facing UI narration (Agent page Context tab, in-chat X-Ray panel, split meter) from System Sections; the agent only needs the provenance/governance model and the display-only constraint.

Add an explicit validation checkpoint in Typical Flow before eviction, e.g., "Confirm the segment is not marked `protected` before calling `context-evict`", and note re-checking the manifest afterward.

Move the 13-label provenance enumeration and persistence internals into a reference file (e.g., references/manifest.md) and link to it, keeping SKILL.md as a lean overview.

DimensionReasoningScore

Conciseness

The body is mostly lean — a terse actions table, bullet rules, and a 5-step flow — but the System Sections section includes host-UI details that don't help the agent act ("Backs the Agent page Context tab", "The in-chat X-Ray panel groups these under 'System'... renders the full breakdown... with a system-vs-conversation split meter"). Minor over-explanation that could be trimmed fits anchor 4 rather than 5; it stays above anchor 3 because nothing explains concepts Claude already knows.

4 / 5

Actionability

Concrete, executable guidance throughout: exact tool names (`context-manifest-get`, `context-pin`, `context-evict`) with when-to-use notes, exact field names (`threadId`, `tokenCount`, `provenance`, `governance`), and a specific flow ("Call `context-manifest-get` with the active `threadId`; sort segments by `tokenCount`"). As an instruction-only skill no code is required, but there is no sample manifest/segment shape, leaving a minor gap that fits anchor 4 rather than 5.

4 / 5

Workflow Clarity

"Typical Flow" gives a clear, correctly ordered 5-step sequence (manifest → sort/inspect → pin → evict → offer restore), and the Rules supply guardrails ("Never evict or summarize protected segments. The manifest marks active-turn user/tool/thinking context as `protected`"). The destructive-operation cap at 3 does not apply since eviction is explicitly reversible and non-destructive; still, the flow lacks an explicit pre-evict validation step (e.g., confirm the segment is not `protected`), matching anchor 4 (clear sequence, minor validation gaps) rather than 5.

4 / 5

Progressive Disclosure

Sections are well-organized (Actions / System Sections / Rules / Typical Flow) with no bundle files and no nested references. However, at ~60 lines it sits above the under-50-line simple-skill threshold, and the System Sections detail — a 13-label provenance enumeration, governance tiers, and persistence internals — is framework reference material that could be externalized. Good structure with minor organization gaps fits anchor 4 rather than 5.

4 / 5

Total

16

/

20

Passed

Description

87%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: third-person, concise, with a clear what-and-when structure and concrete trigger conditions. The only weaknesses are a missing mention of the compaction capability and a few absent natural trigger variations.

Suggestions

Add compaction to the capability list (e.g., "compact a thread to reclaim context") so the description covers the `context-compact` action documented in the body.

Include one or two common trigger phrasings users would naturally say, such as "context is full" or "running out of context/tokens", to broaden trigger coverage.

DimensionReasoningScore

Specificity

The description lists several concrete actions — "Inspect and manage the live agent context window" plus "pinned, evicted, restored, or reported" — but omits the compaction capability (`context-compact`) that the body documents, a minor coverage gap. This matches anchor 4 (several specific actions, minor gaps) rather than 5 (comprehensive) or 3 (only 1-2 actions).

4 / 5

Completeness

It clearly answers "what" (inspect/manage the live context window; pin, evict, restore, report segments) and explicitly answers "when" with an enumerated "Use when" clause covering three concrete trigger conditions. This directly matches the anchor-5 example structure (concrete what + explicit when with trigger phrases); anchor 4 would require the when-clause to be less explicit.

5 / 5

Trigger Term Quality

Natural trigger phrases like "context is getting large", "what is in context", and "stale tool results/files" match what a user would actually say, but common variations such as "context is full", "running out of tokens", or "free up context" are absent. Good coverage with a few natural terms missing fits anchor 4, not 5 (which requires synonym/variation comprehensiveness).

4 / 5

Distinctiveness Conflict Risk

"Context X-Ray", "live agent context window", and the pin/evict/restore vocabulary carve out a clear niche with distinct triggers; virtually no other skill would compete for these queries. Minimal conflict risk matches anchor 5; it is well above anchor 4's "minor overlap risk with closely related skills".

5 / 5

Total

18

/

20

Passed

Validation

87%

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

Validation — 14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

metadata_version

'metadata.version' is missing

Warning

metadata_field

'metadata' should map string keys to string values

Warning

Total

14

/

16

Passed

Repository

BuilderIO/agent-native

Path

.agents/skills/context-xray/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.