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

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 token-efficient instruction for a simple skill: exact tool invocation, explicit output handling, and an ordered conditional branch for failed rows. Both success and failure cases are covered unambiguously, and nothing is missing that the task requires.

DimensionReasoningScore

Conciseness

Two lean sentences with zero padding: "Call the ctx_doctor tool and show its table to the user unchanged. If a row failed, list the fixes it names, in order." It assumes Claude's competence and explains nothing the model already knows; every token earns its place.

5 / 5

Actionability

The body names the exact tool (ctx_doctor), the exact output behavior ("show its table to the user unchanged"), and a conditional failure branch with explicit ordering ("list the fixes it names, in order") — fully executable, instruction-only guidance that covers both the success and failure cases. Per the rubric's code_vs_instruction note, absence of code is not penalized when the guidance is this actionable.

5 / 5

Workflow Clarity

This is a simple single-task skill and the single action is unambiguous, including the failure path. Per the rubric's simple-skill guideline, workflow clarity can score 5 here; the operation is a read-only diagnostic display, so the destructive/batch validation cap does not apply.

5 / 5

Progressive Disclosure

The entire skill is two sentences, well under 50 lines, with no need for external references — and none exist (no references/, scripts/, or assets/ directories are present in the bundle). All content is appropriately inline for a skill of this size, matching the rubric's simple-skill exception for progressive disclosure.

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 states a clear, single concrete capability but omits any trigger guidance, which caps completeness at 3 and leaves natural keyword coverage thin. It is anchored to the specific context-mode niche, keeping conflict risk low. (The frontmatter sets disable-model-invocation: true, which lessens the practical impact of missing triggers, but the rubric scores only what is written.)

Suggestions

Add an explicit 'Use when...' clause naming when to run this check, e.g. "Use when the user asks whether context-mode is installed, working, or needs a health check", to raise completeness.

Include natural user phrasings and synonyms in the description (e.g. "context-mode status", "context-mode check", "diagnose context-mode") to improve trigger term coverage.

Briefly enumerate what the check covers (installation status, per-row pass/fail, suggested fixes) to sharpen the "what" beyond a single action.

DimensionReasoningScore

Specificity

"Check that context-mode is installed and working, as a table" names the domain (context-mode) and one concrete action (verify installation and working status, rendered as a table), matching the "1-2 concrete actions" anchor. It does not list several specific actions, so it falls short of a 4.

3 / 5

Completeness

The "what" is clear (check context-mode installation and working status as a table), but there is no "when": no "Use when..." clause or equivalent trigger guidance appears, which caps this dimension at 3 per the judging guidelines. It is not a 2 because the "what" is concrete rather than vague.

3 / 5

Trigger Term Quality

The only relevant keyword is the domain term "context-mode"; natural phrases a user would say ("is context-mode working", "context-mode status", "diagnose context-mode") and any synonyms are absent. That is more than the generic one-or-two keywords of a 2, but well short of the good coverage of a 4.

3 / 5

Distinctiveness Conflict Risk

The description targets a specific named tool ("context-mode") with a specific diagnostic action, making it mostly distinct with only minor overlap risk against other diagnostic/health-check skills. It lacks the explicit distinct trigger phrases required for a 5.

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