CtrlK
BlogDocsLog inGet started
Tessl Logo

doctor

Diagnose and fix oh-my-codex installation issues

60

Quality

76%

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

Fix and improve this skill with Tessl

tessl review fix ./plugins/oh-my-codex/skills/doctor/SKILL.md

The canonical home for this skill is doctor in Yeachan-Heo/oh-my-codex

SKILL.md
Quality
Evals
Security

Quality

Content

88%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 dense, highly actionable task card: exact commands, explicit severity classifications, a clear report contract, confirmation-gated remediation, and explicit exit conditions with a validation loop. The only notable weaknesses are a small amount of duplicated AGENTS.md-refresh guidance and long inline scripts that could be offloaded to a scripts/ bundle.

DimensionReasoningScore

Conciseness

The body is lean and command-first, assuming Claude's competence (no explanations of what bash, npm, or hooks are), but the AGENTS.md-refresh guidance is stated twice ("If AGENTS.md is missing/outdated, fetch the current raw file..." and later "If AGENTS.md is missing or stale, refresh it from the current release source"), so minor trimming is possible. Not level 5 due to this duplication; not level 3 since there is no unnecessary explanation or padding.

4 / 5

Actionability

Fully executable, copy-paste-ready commands throughout: exact `omx doctor` flag combinations, complete bash snippets for cache enumeration and cleanup, a concrete WebFetch call with URL and prompt, an explicit report template, and precise OK/WARN/CRITICAL classification rules. This matches the top anchor for fully executable guidance.

5 / 5

Workflow Clarity

The sequence is explicit and well-ordered: run diagnostics with per-check classification rules, emit the structured report, gate remediation behind user confirmation and OMX-ownership verification (with a `--dry-run --force` preview), then rerun `omx doctor` and report before/after evidence — a full validation feedback loop for destructive operations. Exit conditions state exactly when to stop with HEALTHY vs ISSUES FOUND.

5 / 5

Progressive Disclosure

There are no bundle files and the single file is organized into clear sections (diagnostics, report contract, remediation, exit conditions) with the one external pointer (`templates/AGENTS.md`) clearly signaled. However, the multi-line cache-enumeration and cleanup scripts could plausibly live in a `scripts/` bundle, and the ~120-line body is above the size where 'well-organized sections' alone earns a 5, so 'good structure; minor organization gaps' fits better than the top anchor.

4 / 5

Total

18

/

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 is concise, specific to a named product, and clearly states the core capability, but it omits any 'when to use' trigger guidance and natural trigger variations. Adding a 'Use when...' clause with terms like 'omx', 'omx doctor', or 'oh-my-codex setup' would materially improve it.

Suggestions

Add an explicit trigger clause, e.g., 'Use when oh-my-codex is not working, omx doctor reports issues, or the user mentions OMX/Codex plugin setup problems.'

Enumerate the concrete diagnostic and repair actions (hook/config checks, legacy script cleanup, plugin cache pruning, AGENTS.md refresh) instead of the generic 'diagnose and fix'.

Include natural user-facing terms and aliases such as 'omx', 'omx doctor', 'Codex plugin not found', and 'setup broken' to improve trigger matching.

DimensionReasoningScore

Specificity

"Diagnose and fix oh-my-codex installation issues" names a specific domain and two concrete actions, matching the 'names domain and 1-2 concrete actions' anchor. It is not level 4 because it does not list several specific actions (e.g., hook cleanup, plugin cache pruning, AGENTS.md refresh) that the skill actually performs.

3 / 5

Completeness

The 'what' is clear (diagnose and fix installation issues for oh-my-codex) but there is no 'Use when...' clause or equivalent explicit trigger guidance, which per judging guidelines caps completeness at 3. It is not level 2 because the 'what' is specific, not vague.

3 / 5

Trigger Term Quality

Relevant keywords exist ("diagnose", "fix", "installation issues", "oh-my-codex") but common natural variations users would say are missing: "omx", "omx doctor", "not working", "setup broken". This fits 'some relevant keywords but missing common variations', below level 4's 'good keyword coverage'.

3 / 5

Distinctiveness Conflict Risk

Naming a specific product (oh-my-codex) gives a clear niche with minimal conflict risk against unrelated skills — 'mostly distinct; minor overlap risk' fits. It is not level 5 because it lacks explicit trigger phrases and could overlap with generic codex/setup troubleshooting skills.

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
Yeachan-Heo/oh-my-codex
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.