CtrlK
BlogDocsLog inGet started
Tessl Logo

omc-doctor

Diagnose and fix oh-my-claudecode installation issues

58

Quality

Does it follow best practices?

Impact

No eval scenarios have been run

SecuritybySnyk

Advisory

Suggest reviewing before use

SKILL.md
Quality
Evals
Security

Quality

Content

77%

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

The body is highly actionable with executable commands and a well-sequenced, checkpointed diagnostic workflow, but it is monolithic with no progressive file disclosure and has some verbose one-liners that could be tightened.

Suggestions

Split the long inline agent/skill/command name lists and the auto-fix recipes into a reference file (e.g. references/legacy-names.md) with clearly signaled links to improve progressive disclosure.

Move the dense `node -e` version/cache one-liners into a scripts/ helper (e.g. scripts/omc_versions.js) invoked by a short command to reduce inline noise.

Tighten repeated `${CLAUDE_CONFIG_DIR:-$HOME/.claude}` path boilerplate by defining it once and reusing, or by extracting shared checks into a script.

DimensionReasoningScore

Conciseness

The body is mostly efficient and task-specific with no concept padding, but several dense one-liner `node -e` snippets and repeated path handling could be tightened, matching the 'mostly efficient but could be tightened' anchor.

2 / 3

Actionability

Provides fully executable bash and node snippets (e.g. `npm view ... version`, `grep -q "<!-- OMC:START -->"`, `node -e ...rmSync`) and copy-paste-ready fixes, matching the 'fully executable, copy-paste ready' anchor.

3 / 3

Workflow Clarity

Sequences seven numbered diagnostic steps each with an explicit per-step 'Diagnosis' checkpoint, a defined report format, and user-gated fixes with warnings before destructive removals — clear sequence with validation checkpoints.

3 / 3

Progressive Disclosure

The skill is a single ~231-line monolithic SKILL.md with no bundle files (references/scripts/assets absent) and no one-level-deep external references; sections are well-organized but content that could be split stays inline.

2 / 3

Total

10

/

12

Passed

Description

57%

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 clear and well-scoped to a distinct niche, but it lacks an explicit 'Use when' trigger clause and broader keyword coverage, which caps completeness and trigger-term quality at 2.

Suggestions

Add an explicit trigger clause, e.g. 'Use when diagnosing or fixing oh-my-claudecode installation, hook, or CLAUDE.md issues'.

Expand the action list to concrete capabilities (e.g. 'check plugin version, detect legacy hooks/scripts, verify CLAUDE.md, clear stale cache, auto-fix') to lift specificity.

Include common user phrasings like 'omc setup broken', 'oh-my-claudecode not working', or 'plugin cache' to improve trigger-term coverage.

DimensionReasoningScore

Specificity

Quotes 'Diagnose and fix oh-my-claudecode installation issues' — names the domain and two concrete actions (diagnose, fix), but the action list is not comprehensive enough to reach the 'multiple specific concrete actions' anchor.

2 / 3

Completeness

States what the skill does ('Diagnose and fix') but provides no explicit 'when' / 'Use when' trigger guidance, so per the judging guidelines completeness is capped at 2.

2 / 3

Trigger Term Quality

Includes natural terms like 'installation issues' and the product name 'oh-my-claudecode', but coverage is limited with no synonyms or 'Use when' style variations, matching the 'some relevant keywords but missing common variations' anchor.

2 / 3

Distinctiveness Conflict Risk

Scoped to a specific plugin's installation ('oh-my-claudecode installation issues'), a clear niche with distinct triggers unlikely to conflict with other skills.

3 / 3

Total

9

/

12

Passed

Validation

93%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

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