CtrlK
BlogDocsLog inGet started
Tessl Logo

setup

Use first for install/update routing — sends setup, doctor, or MCP requests to the correct OMC setup flow

79

Quality

Does it follow best practices?

Impact

No eval scenarios have been run

SecuritybySnyk

Passed

No known issues

SKILL.md
Quality
Evals
Security

Quality

Content

100%

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

The body is a tight, well-structured routing reference: concise, fully actionable with concrete command examples, and clearly organized. As a simple single-purpose skill under 50 lines it satisfies the workflow-clarity and progressive-disclosure simple-skill allowances.

DimensionReasoningScore

Conciseness

The body is lean and efficient — short Usage/Routing/Notes sections with no re-explanation of concepts Claude already knows, so every token earns its place per the level-3 anchor.

3 / 3

Actionability

Concrete executable commands and copy-paste input→output examples (e.g. "/oh-my-claudecode:setup doctor --json # => /oh-my-claudecode:omc-doctor --json") give fully actionable guidance matching the level-3 anchor.

3 / 3

Workflow Clarity

This is a simple routing skill whose single action ("Process the request by the first argument only") is unambiguous with explicit per-token rules; per the simple-skills note it scores 3 without validation checkpoints since routing is non-destructive.

3 / 3

Progressive Disclosure

Under 50 lines with no need for external references, and well-organized into clear Usage/Routing/Notes sections, so it qualifies for the level-3 simple-skill allowance.

3 / 3

Total

12

/

12

Passed

Description

100%

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 concise yet specific, naming concrete routing actions and providing an explicit 'Use first for' trigger that answers both what and when. It is distinctive within the OMC ecosystem and uses natural trigger terms.

DimensionReasoningScore

Specificity

"sends setup, doctor, or MCP requests to the correct OMC setup flow" enumerates multiple specific concrete routing actions (setup, doctor, MCP), matching the level-3 anchor rather than the level-2 domain-only anchor.

3 / 3

Completeness

It states both what ("sends setup, doctor, or MCP requests to the correct OMC setup flow") and when ("Use first for install/update routing"), an explicit trigger clause, so it is not capped at 2.

3 / 3

Trigger Term Quality

Natural terms users would actually say are well covered — "install/update", "setup", "doctor", and "MCP" — meeting the good-coverage bar of the level-3 anchor rather than the partial-coverage level-2 anchor.

3 / 3

Distinctiveness Conflict Risk

Anchored to "OMC setup flow" with three named sub-flows, giving it a clear niche unlikely to conflict with unrelated skills; not generic enough to warrant the level-2 overlap anchor.

3 / 3

Total

12

/

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.