CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

omc-doctor

Diagnose and fix oh-my-claudecode installation issues

Quality

71%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./skills/omc-doctor/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

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

This is a highly actionable, carefully validated diagnostic workflow: concrete commands, explicit decision rules, safety-gated destructive fixes, and a clear report format. Its weaknesses are structural — a monolithic file inlining reference-grade lookup tables — and stylistic, with Step 2's long conditional prose that could be compressed or split into references without losing clarity.

Suggestions

Move the historical SHA-256 fingerprint lists, the filename-to-event mapping table, and the known plugin agent/skill/command name lists into a references/ file (e.g. references/legacy-payloads.md), keeping SKILL.md as a lean overview with clearly signaled one-level-deep pointers.

Rewrite Step 2's run-on paragraphs as a short decision table or bullet checklist (scope resolution, enablement precedence, ownership verification, event equivalence) — the same rules expressed structurally would cut hundreds of tokens and reduce misreading risk.

Trim repeated safety clauses (e.g. 'leave it in place / do not remove' appears many times across Steps 2-3 and the fixes) into one stated policy referenced where needed.

DimensionReasoningScore

Conciseness

The body is dense with genuinely non-obvious, version-specific knowledge (SHA-256 fingerprints, settings precedence rules, filename-to-event mappings) rather than padded explanations of known concepts, but Step 2's multi-paragraph run-on prose on settings-file resolution, plugin-enablement precedence, and hook ownership is severely repetitive and could be tightened or tabulated, matching the 'mostly efficient but could be tightened' anchor rather than the 'minor instances' of anchor 4.

3 / 5

Actionability

Every step ships copy-paste-ready, cross-platform bash/node one-liners with explicit fallback output, each step has concrete diagnosis rules mapping observed output to CRITICAL/WARN/OK, and the report template plus enumerated known plugin file names make the guidance fully executable.

5 / 5

Workflow Clarity

The seven steps are clearly sequenced with explicit per-step diagnosis checkpoints, destructive fixes are gated on user confirmation with timestamped backups, atomic writes, and 'leave in place on any inconclusive verification' feedback rules, and the post-fix restart instruction closes the loop — validation is thorough throughout.

5 / 5

Progressive Disclosure

No bundle files exist and the ~280-line SKILL.md inlines large lookup tables (historical fingerprint lists, filename-to-event mapping, known agent/skill/command names) that clearly belong in separate reference files, though section headers keep the single file navigable — matching the 'some structure but content that should be separate is inline' anchor.

3 / 5

Total

16

/

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 short, accurate, and appropriately scoped to oh-my-claudecode, but it is underspecified: it lists only two generic actions, omits any trigger guidance, and lacks the natural keyword variations that would help a user (or Claude) select this skill over generic troubleshooting. Adding a 'Use when...' clause and naming the concrete diagnostic areas would lift it substantially.

Suggestions

Add an explicit trigger clause, e.g. "Use when the user reports OMC/oh-my-claudecode problems: plugin not loading, stale hooks, outdated CLAUDE.md, plugin cache issues, or after a failed update or migration from the curl-based install."

Enumerate one or two more concrete capabilities in the description (e.g. "checks plugin version, legacy hook registrations, CLAUDE.md freshness, and cache state, then applies confirmed auto-fixes") to raise specificity from generic diagnose/fix verbs.

Include the natural invocation name and synonyms users would say ("omc doctor", "OMC is broken", "oh-my-claudecode not working") to improve trigger-term coverage.

DimensionReasoningScore

Specificity

"Diagnose and fix oh-my-claudecode installation issues" names the domain and two actions (diagnose, fix), but does not enumerate the concrete checks performed (plugin version, legacy hooks, CLAUDE.md, plugin cache, curl-installed content), so coverage is not comprehensive as anchor 4 requires.

3 / 5

Completeness

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

3 / 5

Trigger Term Quality

Relevant keywords like "diagnose", "fix", and "installation issues" are present, but common natural phrasings users would actually say ("OMC is broken", "plugin not loading", "hooks not working", "omc doctor", "update oh-my-claudecode") are missing, matching the 'some relevant keywords but missing common variations' anchor.

3 / 5

Distinctiveness Conflict Risk

The description is scoped to a specific named plugin, giving it a clear niche with minimal conflict risk against unrelated skills; it falls just short of anchor 5 because "installation issues" is still broad enough to overlap with general debugging/setup skills for that plugin.

4 / 5

Total

13

/

20

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.

Validation — 15 / 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

Path

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