CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

doctor

Diagnose and fix oh-my-codex installation issues

Quality

68%

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/doctor/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

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

A dense, safety-conscious diagnostic workflow with genuinely executable commands and strong validation checkpoints, undermined by convoluted prose and a monolithic single-file structure. The remediation policy is thorough but would benefit from tighter writing and splitting detailed AGENTS.md setup rules into a reference file.

Suggestions

Rewrite the 'Persistent AGENTS guidance' section as a short numbered checklist with the selector-substitution rules stated once, cutting the repeated 'illustrative'/'authorized scope' caveats.

Move the detailed AGENTS.md repair policy (merge/preference/symlink rules) into a reference file and keep a concise decision summary in SKILL.md.

Add explicit commands or short code blocks for the prose-only remediation paths (symlink handling, hook-state restoration).

DimensionReasoningScore

Conciseness

The body avoids generic-concept explanations and is dense with domain-specific policy, but sections like 'Persistent AGENTS guidance' use very long, winding sentences and repeat the 'illustrative' and 'authorized scope' caveats multiple times, so it could be tightened considerably.

3 / 5

Actionability

Copy-paste-ready bash commands cover diagnostics ('omx doctor', the plugin-cache inspection script, rg checks) and remediation previews ('omx setup ... --dry-run'), plus a concrete report template; a few remediation paths (symlinks, hook restoration) are prose-only without commands.

4 / 5

Workflow Clarity

The diagnose -> report -> scoped remediation -> rerun/verify -> exit sequence is clear with explicit validation checkpoints (dry-run previews, post-repair 'omx doctor' rerun, verify-before-success, stop with ISSUES FOUND on failure), but the intricate AGENTS.md repair sequence is buried in long paragraphs rather than a numbered checklist.

4 / 5

Progressive Disclosure

The ~130-line single-file body has clear section headers, but no bundle files exist and dense remediation policy (the full AGENTS.md setup rules) is inlined where a separate reference file would ease navigation; the one referenced path (templates/AGENTS.md) is signaled but not part of a bundle.

3 / 5

Total

14

/

20

Passed

Description

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

A concise, distinct, third-person description that clearly states what the skill does, but it lacks any 'when to use' trigger guidance and natural keyword variations. Adding an explicit 'Use when...' clause with user-facing trigger phrases would lift completeness and trigger-term quality.

Suggestions

Add a 'Use when...' clause, e.g. 'Use when oh-my-codex is not loading, hooks fail, or setup/plugins appear broken.'

Include natural trigger terms users would actually say, such as 'omx not working', 'setup problems', or 'troubleshooting'.

Briefly enumerate the concrete diagnostic areas (hooks, plugin cache, AGENTS.md, skills) to improve specificity.

DimensionReasoningScore

Specificity

'Diagnose and fix oh-my-codex installation issues' names the domain and two concrete actions (diagnose, fix), but does not enumerate what the doctor actually checks (hooks, plugin cache, AGENTS.md, skills), so it falls short of the 'several specific actions' anchor.

3 / 5

Completeness

The 'what' is clear (diagnose and fix installation issues) but there is no 'Use when...' clause or equivalent explicit trigger guidance, which caps completeness at 3 per the rubric guidelines.

3 / 5

Trigger Term Quality

'installation issues', 'diagnose', and 'fix' are relevant, natural terms, but common variations users would say — 'setup', 'not working', 'broken', 'troubleshooting', 'omx' — are missing, matching the 'some relevant keywords but missing variations' anchor.

3 / 5

Distinctiveness Conflict Risk

Naming the specific product (oh-my-codex) with a narrow diagnostic purpose gives it a clear niche with distinct triggers and minimal conflict risk against other skills.

5 / 5

Total

14

/

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

Path

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