CtrlK
BlogDocsLog inGet started
Tessl Logo

ctx-doctor

Run context-mode diagnostics. Checks runtimes, hooks, FTS5, plugin registration, npm and marketplace versions. Trigger: /context-mode:ctx-doctor

75

Quality

Does it follow best practices?

Impact

No eval scenarios have been run

SecuritybySnyk

Passed

No known issues

SKILL.md
Quality
Evals
Security

Quality

Content

100%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The body is concise, actionable, and clearly sequenced with an explicit fallback, making effective use of the token budget. It is a simple, self-contained skill that needs no external references and is well organized.

DimensionReasoningScore

Conciseness

The body is a lean three-step procedure with a tight fallback code block and no explanation of concepts Claude already knows; even the renderer-safe note is skill-specific guidance, fitting the score-3 anchor.

3 / 3

Actionability

Step 1 names the concrete `ctx_doctor` MCP tool and the fallback step gives copy-paste-ready executable Bash with a real two-tier CLI path resolution, matching the score-3 anchor.

3 / 3

Workflow Clarity

A clear numbered sequence with an explicit conditional fallback ("only if MCP tool call fails"); as a simple single-purpose skill, this satisfies the score-3 simple-skill allowance and no destructive/batch validate-loop cap applies.

3 / 3

Progressive Disclosure

Under 50 lines with no external references needed and no references/scripts/assets bundle present, the well-organized title + Instructions sections meet the score-3 simple-skill allowance for progressive disclosure.

3 / 3

Total

12

/

12

Passed

Description

85%

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 is specific and well-scoped, clearly naming the diagnostic checks and an explicit trigger. Its weakest point is trigger-term quality, since the natural-language keywords a user would say are limited and rely heavily on the slash command.

Suggestions

Add a natural-language "Use when..." clause with user-spoken variations (e.g., "Use when debugging context mode, checking hooks or FTS5, or verifying plugin/npm/marketplace versions") so it triggers on free-text requests, not only the slash command.

Include everyday synonyms like "context mode not working" or "plugin won't load" to broaden natural trigger coverage beyond the technical term "context-mode diagnostics".

DimensionReasoningScore

Specificity

"Checks runtimes, hooks, FTS5, plugin registration, npm and marketplace versions" lists multiple specific concrete checks, matching the score-3 anchor rather than the score-2 anchor that names only a domain and some actions.

3 / 3

Completeness

It states what it does ("Run context-mode diagnostics. Checks runtimes, hooks, FTS5...") and supplies equivalent explicit trigger guidance ("Trigger: /context-mode:ctx-doctor"), so it is not capped at 2 by the missing-'Use when' rule and answers both what and when.

3 / 3

Trigger Term Quality

The natural-language keyword "context-mode diagnostics" plus the slash trigger "Trigger: /context-mode:ctx-doctor" give some relevant keywords, but coverage of the variations a user would actually speak is thin, fitting score-2 rather than score-3's broad coverage.

2 / 3

Distinctiveness Conflict Risk

The narrow "context-mode diagnostics" scope bound to a specific slash command is a clear niche unlikely to trigger for other skills, matching the score-3 anchor.

3 / 3

Total

11

/

12

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.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
mksglu/context-mode
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.