CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

ctx-purge

Purge the context-mode knowledge base. Permanently deletes all indexed content and resets session stats. This is destructive and cannot be undone. Trigger: /context-mode:ctx-purge

Quality

79%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Medium

Suggest reviewing before use

Fix and improve this skill with Tessl

tessl review fix ./skills/ctx-purge/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

86%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 tight, single-purpose destructive skill executed well: concrete tool invocations with exact payloads, a scoped-purge decision workflow with confirmation checkpoints, and explicit schema error rules. The only refinements would be a brief error-recovery note for failed purge calls and deduplicating the irreversibility warnings.

DimensionReasoningScore

Conciseness

The body is lean and assumes Claude's competence — no concept explanations, just scopes, parameters, and rules — but the irreversibility warning recurs across the description, step 2, and the Important section, which could be trimmed. Not a 5 because of that minor redundancy.

4 / 5

Actionability

Fully executable guidance: the exact tool ("mcp__context-mode__ctx_purge") is given with copy-ready parameter objects for every supported form ("{ confirm: true, sessionId: \"<id>\" }", "{ confirm: true, scope: \"project\" }", and the deprecated bare form), plus explicit schema rules for rejected combinations.

5 / 5

Workflow Clarity

A clearly sequenced 4-step workflow with explicit validation for the destructive operation — user scope confirmation, a warning step, the mandatory "confirm: true" checkpoint, and result reporting — plus enumerated error conditions (rejected ambiguous params, throws without sessionId). Not a 5 because there is no guidance on recovering from a failed or errored purge call.

4 / 5

Progressive Disclosure

The skill is under 50 lines, needs no external references, and no bundle files exist; per the simple-skill exception, its well-organized sections (Instructions, Schema rules, When to Use, Important) warrant a 5.

5 / 5

Total

18

/

20

Passed

Description

62%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 specific, distinctive, destructive capability in lean third-person prose, but it lacks a natural-language "when to use" clause and offers only a slash-command trigger rather than user-sayable phrases. It also undersells the skill by omitting the project vs. session scope distinction that the body documents.

Suggestions

Add a "Use when..." clause with concrete trigger phrases, e.g. "Use when the user wants to wipe stale indexed content, reset context-mode stats, or start fresh — or asks to purge/reset/clear the knowledge base."

Include natural-language synonyms users would actually say ("purge", "wipe", "reset", "clear the knowledge base", "fresh start") rather than relying solely on the slash-command path as the trigger.

Mention both purge scopes (whole project vs. a single session) so the description's "deletes all indexed content" matches the skill's actual capabilities.

DimensionReasoningScore

Specificity

The description names concrete third-person actions — "Permanently deletes all indexed content and resets session stats" — which goes beyond the 1-2 action anchor, but coverage is incomplete (the two purge scopes from the body are absent), so it is not a 5.

4 / 5

Completeness

The "what" is clear (deletes indexed content, resets stats), but there is no "Use when..." clause or equivalent usage-condition guidance — the Trigger line only names the invocation command — which caps completeness at 3 per the judging guidelines.

3 / 5

Trigger Term Quality

The only trigger guidance is "Trigger: /context-mode:ctx-purge", a slash-command path rather than natural phrasing; relevant keywords like "purge" and "knowledge base" appear, but common user variations ("reset context", "wipe stale data", "fresh start") are missing.

3 / 5

Distinctiveness Conflict Risk

"Purge the context-mode knowledge base" plus the ctx-purge naming carves out a clear niche with a distinct trigger; overlap risk with other skills is minimal.

5 / 5

Total

15

/

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-purge/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.