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.

This is a model lean single-purpose skill: complete and unambiguous instructions in two sentences with no padding, no over-explanation, and nothing that needs splitting into bundle files. Both the tool invocation and the exact output formatting are fully specified.

DimensionReasoningScore

Conciseness

Two sentences with zero padding: "Call the ctx_stats tool and show the text block of its reply to the user unchanged, inside a code block so the columns stay aligned" delivers tool, transformation, format, and rationale; every token earns its place, matching the lean anchor 5.

5 / 5

Actionability

"Call the ctx_stats tool", "show the text block of its reply to the user unchanged, inside a code block", and "Add one sentence under it that names the largest saving" are fully executable instructions covering the single common case; per the rubric's code-vs-instruction note, the absence of code is not penalized when guidance is this specific.

5 / 5

Workflow Clarity

The single-task sequence (call tool, render output unchanged in a code block, add the one-sentence summary naming the largest saving) is unambiguous, and as a read-only display task no validation checkpoints are needed — the simple-skill exception applies.

5 / 5

Progressive Disclosure

The skill is two sentences with no external material needed and no bundle files exist, so everything appropriately lives inline in SKILL.md; the under-50-line simple-skill exception for progressive disclosure applies.

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 clearly states what the skill does and occupies a distinct niche, but it omits any "Use when..." trigger guidance and offers thin keyword coverage, capping completeness and trigger quality at the midpoint. Specificity is adequate but lists only a single action.

Suggestions

Add a "Use when..." clause with explicit triggers (e.g., "Use when the user asks about context savings or how much context context-mode saved") to raise completeness.

Broaden natural trigger terms with synonyms such as "context savings", "token savings", or "context usage" so users' actual phrasings match.

Name one or two more concrete capabilities of the report (e.g., which statistics it includes) to increase specificity beyond a single action.

DimensionReasoningScore

Specificity

"Show how much context context-mode saved, as a detailed report" names the domain (context-mode savings) and one concrete action with an output format, matching the "Names domain and 1-2 concrete actions" anchor; it does not list the several specific actions required for a 4.

3 / 5

Completeness

The 'what' is clear ("Show how much context context-mode saved, as a detailed report") but no "Use when..." clause or equivalent trigger guidance exists, which per the judging guidelines caps completeness at 3.

3 / 5

Trigger Term Quality

"how much context context-mode saved" is a natural phrase, but coverage stops there — no synonyms or variations such as "context savings", "token savings", or "context usage", matching "Some relevant keywords but missing common variations" rather than the good coverage of a 4.

3 / 5

Distinctiveness Conflict Risk

The reference to "context-mode" and its savings statistics carves a clear, narrow niche with only minor overlap risk against generic context-management skills; it lacks the explicit distinct trigger phrasing of the anchor-5 example, so it sits between anchors 4 and 5 at 4.

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

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.