CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

ctx-stats

Show how much context context-mode saved, as a detailed report.

Quality

81%

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

100%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 model of lean, fully actionable instruction for a simple skill: exact tool name, exact presentation requirements with rationale, and a concrete follow-up, all in one sentence. Nothing is missing for the task it describes and nothing is extraneous.

DimensionReasoningScore

Conciseness

The single sentence packs in exactly the needed instructions — which tool to call, how to present the output, why ("so the columns stay aligned"), and one follow-up action — with zero padding or explanation of concepts Claude already knows. Every token earns its place, matching 'Lean and efficient; assumes Claude's competence'.

5 / 5

Actionability

It names the exact tool (`mcp__context_mode__ctx_stats`), the exact output handling ("show the text block of its reply to the user unchanged, inside a code block"), and a concrete follow-up ("one sentence under it that names the largest saving") — fully executable, specific guidance that covers the entire task. As an instruction-only skill, no code is expected and the guidance is unambiguous.

5 / 5

Workflow Clarity

This is a simple single-purpose skill where the single action is unambiguous: call the tool, render its reply verbatim in a code block, add one summarizing sentence. The rubric's simple-skill exception applies, and no destructive or batch operations exist that would require validation checkpoints.

5 / 5

Progressive Disclosure

The skill is well under 50 lines with no need for external references — the entire procedure is complete in one self-contained instruction with no references/, scripts/, or assets/ bundle present. Per the rubric guideline, a short skill with no need for external references scores 5 on organization.

5 / 5

Total

20

/

20

Passed

Description

53%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 communicates a clear, narrow 'what' (a savings report for the context-mode tool) with decent distinctiveness, but it omits any 'when to use' guidance and has thin natural-keyword coverage, capping completeness and trigger-term quality at the midpoint. Adding an explicit trigger clause with common user phrasings would lift the two heaviest-weighted dimensions.

Suggestions

Add an explicit 'Use when...' clause, e.g. 'Use when the user asks how much context or tokens context-mode saved.'

Include natural trigger variations users would actually say, such as 'context usage', 'token savings', or 'context stats', near the core phrase.

Make 'detailed report' concrete by naming what the report shows (e.g. per-conversation savings, largest saving) to strengthen specificity.

DimensionReasoningScore

Specificity

"Show how much context context-mode saved" names the domain and one concrete action (producing a savings report), matching the anchor 'Names domain and 1-2 concrete actions, but not comprehensive'. It is not 4 because "as a detailed report" is vague and no specific report contents are enumerated, and not 2 because it goes beyond merely naming the domain with a concrete deliverable.

3 / 5

Completeness

The 'what' is clear ("Show how much context context-mode saved, as a detailed report") but there is no 'Use when...' clause or equivalent trigger guidance, which per the judging guidelines caps completeness at 3 ('Has a clear what but when is missing or only weakly implied'). Not 4 because the 'when' is entirely absent rather than just imprecise.

3 / 5

Trigger Term Quality

The terms "context", "context-mode", and "saved" are relevant and natural, but common variations users might say ("context usage", "token savings", "context stats") are absent, matching 'Some relevant keywords but missing common variations or synonyms'. Not 4 because keyword coverage is thin rather than good; not 2 because the keywords are domain-specific, not generic.

3 / 5

Distinctiveness Conflict Risk

"how much context context-mode saved" is tied to a named tool and a specific metric, giving a clear niche with only minor overlap risk against closely related context-management skills ('Mostly distinct; minor overlap risk'). Not 5 because the anchor-5 example pairs the niche with distinct trigger phrases, which this description lacks; not 3 because naming a specific tool's specific metric is more distinct than generic 'Works with document files'.

4 / 5

Total

13

/

20

Passed

Validation

100%

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

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository

mksglu/context-mode

Path

plugins/claude-code/codex/skills/ctx-stats/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.