CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

ctx-doctor

Check that context-mode is installed and working, as a table.

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

The canonical home for this skill is ctx-doctor in mksglu/context-mode

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, unambiguous instruction: it names the exact tool, the exact output behavior, and the ordered failure-handling procedure in two sentences. Nothing is missing for a skill of this scope and nothing should be cut.

DimensionReasoningScore

Conciseness

The two-sentence body ('Call the ctx_doctor tool and show its table to the user unchanged. If a row failed, list the fixes it names, in order.') is entirely load-bearing — even 'unchanged' and 'in order' prevent concrete failure modes. Every token earns its place and nothing explains what Claude already knows.

5 / 5

Actionability

The instruction is fully executable for an instruction-only skill: it names the exact tool ('ctx_doctor'), specifies output handling ('show its table to the user unchanged'), and defines the failure path ('If a row failed, list the fixes it names, in order'). Per the rubric's scoring notes, absence of code is not penalized when guidance is this concrete.

5 / 5

Workflow Clarity

This is a simple single-task skill and the single action is unambiguous, covering both the success path and the failure branch — the rubric's simple-skill exception allows a 5 here. No destructive or batch operations exist that would require validation checkpoints.

5 / 5

Progressive Disclosure

The skill is under 50 lines with no need for external references or bundle files (no references/, scripts/, or assets/ exist), and the entire body is appropriately contained in SKILL.md. The rubric's guideline for short, self-contained skills supports a 5; adding sections or reference files would only add noise.

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 anchors it to a distinctive tool name, but it omits any 'when to use' guidance and lacks natural diagnostic trigger variations (diagnose, troubleshoot, verify). It is serviceable yet under-specified relative to the rubric's exemplar descriptions.

Suggestions

Add an explicit trigger clause, e.g. 'Use when the user asks to check, verify, or troubleshoot context-mode installation or status', to fix the missing 'when' that caps completeness at 3.

Include natural trigger variations and synonyms such as 'diagnose', 'troubleshoot', 'verify', or 'status check' so users' phrasing matches the description more readily.

Briefly enumerate what the check covers (e.g. 'runs installation and connectivity checks and reports results in a table with suggested fixes') to sharpen the single generic action into more concrete capability statements.

DimensionReasoningScore

Specificity

The description names the domain ("context-mode") and one concrete action with a specified deliverable ("Check that context-mode is installed and working, as a table"), matching the 'names domain and 1-2 concrete actions' anchor. It is more informative than the score-2 example ('Processes PDF files') but does not list several specific actions, so it falls short of 4.

3 / 5

Completeness

The 'what' is clear (verify context-mode installation status, presented as a table) but there is no 'Use when...' clause or equivalent trigger guidance, which caps completeness at 3 per the judging guidelines. It is not a 4 because the 'when' is entirely absent rather than merely implicit or improvable.

3 / 5

Trigger Term Quality

Relevant keywords are present ("context-mode", "installed", "working") but common variations a user would naturally say — diagnose, troubleshoot, verify, status, health check — are all missing. This matches 'some relevant keywords but missing common variations or synonyms' rather than the good coverage of a 4.

3 / 5

Distinctiveness Conflict Risk

The unique tool name 'context-mode' gives the skill a clear niche with low conflict risk against unrelated skills. It is not a 5 because distinctiveness rests solely on the tool name with no trigger phrases, leaving minor overlap risk with a closely related context-mode setup/installation skill.

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/pi/skills/ctx-doctor/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.