setup
Use first for install/update routing — sends setup, doctor, or MCP requests to the correct OMC setup flow
65
78%
Does it follow best practices?
Impact
—
No eval scenarios have been run
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./skills/setup/SKILL.mdQuality
Discovery
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 establishes a clear routing role for installation and setup tasks within an OMC ecosystem, giving it good distinctiveness. However, it lacks an explicit 'Use when...' clause, relies on some internal jargon ('OMC'), and doesn't fully enumerate the concrete actions or trigger scenarios that would help Claude confidently select this skill.
Suggestions
Add an explicit 'Use when...' clause listing trigger scenarios, e.g., 'Use when the user asks to install, update, configure, or troubleshoot OMC, or mentions MCP setup, doctor commands, or setup flows.'
Expand trigger terms to include natural user language variations such as 'configure', 'installation', 'troubleshoot', 'fix setup', and spell out what 'OMC' stands for to improve keyword matching.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | It names a domain (install/update routing) and some actions (sends setup, doctor, or MCP requests to the correct flow), but the actions are more about routing than concrete end-user capabilities. 'Correct OMC setup flow' is somewhat vague without explaining what those flows actually do. | 2 / 3 |
Completeness | The 'what' is partially addressed (routing install/update/setup/doctor/MCP requests), but the 'when' is only implied through 'Use first for install/update routing' rather than explicitly stated with a 'Use when...' clause listing specific trigger scenarios. | 2 / 3 |
Trigger Term Quality | Includes some relevant keywords like 'install', 'update', 'setup', 'doctor', and 'MCP' that users might naturally say. However, it lacks common variations (e.g., 'configure', 'installation', 'troubleshoot', 'fix') and 'OMC' is jargon that may not match user language. | 2 / 3 |
Distinctiveness Conflict Risk | The description carves out a clear niche as a routing/triage skill specifically for OMC setup flows, with distinct triggers like 'doctor', 'MCP requests', and 'install/update routing' that are unlikely to conflict with other skills. | 3 / 3 |
Total | 9 / 12 Passed |
Implementation
100%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is an excellent routing/dispatch skill that is lean, precise, and well-structured. It provides clear argument-to-command mappings with concrete examples, assumes Claude's competence, and appropriately delegates to sub-skills. The notes section adds useful context about backward compatibility without being verbose.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Every line serves a purpose. No unnecessary explanations of what routing is or how commands work. The skill assumes Claude understands command parsing and delegation, and presents only the routing table and examples needed. | 3 / 3 |
Actionability | The routing rules are concrete and unambiguous with exact argument-to-command mappings. The examples section provides clear input/output pairs showing exactly how arguments are forwarded, making this fully actionable. | 3 / 3 |
Workflow Clarity | This is a simple routing/dispatch skill with a single decision point (first argument). The routing table is clear and exhaustive, covering the no-argument case and all named sub-commands. For this type of simple skill, the workflow is unambiguous and complete. | 3 / 3 |
Progressive Disclosure | The skill appropriately keeps itself as a concise routing overview and delegates to the actual implementation skills (omc-setup, omc-doctor, mcp-setup). This is exactly the right level of progressive disclosure — one level deep with clearly named targets. | 3 / 3 |
Total | 12 / 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
3e94567
- 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.