omc-doctor
Diagnose and fix oh-my-claudecode installation issues
66
58%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Advisory
Suggest reviewing before use
Optimize this skill with Tessl
npx tessl skill review --optimize ./skills/omc-doctor/SKILL.mdQuality
Discovery
40%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 identifies a clear, specific niche (oh-my-claudecode installation) which provides good distinctiveness, but lacks the completeness needed for effective skill selection. It needs explicit trigger guidance and more specific action details to help Claude know when to select this skill over others.
Suggestions
Add a 'Use when...' clause with trigger terms like 'oh-my-claudecode not working', 'omcc setup', 'installation failed', 'shell integration problems'
Expand specific actions beyond 'diagnose and fix' to include concrete capabilities like 'verify PATH configuration, check shell integration, resolve dependency conflicts, validate permissions'
Include common user phrasings and variations such as 'setup error', 'won't install', 'configuration issues', or abbreviations like 'omcc'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (oh-my-claudecode installation) and two actions (diagnose, fix), but doesn't list specific concrete actions like 'check PATH configuration, verify shell integration, resolve dependency conflicts'. | 2 / 3 |
Completeness | Describes what it does (diagnose and fix installation issues) but completely lacks a 'Use when...' clause or any explicit trigger guidance for when Claude should select this skill. | 1 / 3 |
Trigger Term Quality | Includes 'oh-my-claudecode' and 'installation issues' which are relevant, but misses common variations users might say like 'setup problems', 'install error', 'not working', 'configuration', or 'omcc'. | 2 / 3 |
Distinctiveness Conflict Risk | Very specific niche targeting 'oh-my-claudecode' which is a distinct product name, making it unlikely to conflict with other skills or trigger incorrectly. | 3 / 3 |
Total | 8 / 12 Passed |
Implementation
77%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a well-structured diagnostic skill with excellent actionability - every step has concrete, executable commands with clear diagnosis criteria. The workflow is logical with proper validation checkpoints and user confirmation before destructive operations. However, the skill could be more concise by externalizing the lengthy plugin name lists and reducing repetition in the node one-liners.
Suggestions
Extract the 'Known plugin agent/skill/command names' lists to a separate reference file (e.g., PLUGIN-MANIFEST.md) to reduce skill length
Create a reusable shell function or single node script for the repeated cache path resolution logic instead of duplicating the one-liner pattern
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is reasonably efficient but includes some redundancy (e.g., similar node one-liners repeated multiple times with slight variations). The extensive lists of known plugin names could potentially be externalized. | 2 / 3 |
Actionability | Provides fully executable bash commands and node one-liners that are copy-paste ready. Each diagnostic step has concrete commands with clear expected outputs and diagnosis criteria. | 3 / 3 |
Workflow Clarity | Clear 6-step diagnostic sequence with explicit status levels (OK/WARN/CRITICAL) for each check. Includes validation through the report format, user confirmation before fixes, and post-fix instructions to restart. | 3 / 3 |
Progressive Disclosure | Content is well-structured with clear sections (diagnostics, report format, auto-fix, post-fix), but the skill is monolithic at ~180 lines. The known plugin names lists could be externalized to a reference file. | 2 / 3 |
Total | 10 / 12 Passed |
Validation
90%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 10 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 10 / 11 Passed | |
- Repository
- Yeachan-Heo/oh-my-claudecode
- Commit
48ffaac
- 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.