omc-setup

Install or refresh oh-my-claudecode for plugin, npm, and local-dev setups from the canonical setup flow

Quality

60%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/omc-setup/SKILL.md

Quality

Content

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

The SKILL.md body is highly actionable and well-sequenced with strong validation and resume feedback loops, and it correctly delegates phase detail to separate files. Conciseness is slightly reduced by the inlined help text and repeated flag descriptions.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient and assumes Claude's competence about the environment, but the large verbatim --help text block and repeated flag explanations (explained here and again under 'Keeping Up to Date') add padding that could be tightened.	3 / 5
Actionability	It provides concrete, copy-paste-ready shell commands (the setup-claude-md.sh invocation, jq config checks, setup-progress.sh calls) with explicit arguments and environment-variable fallbacks, covering the common cases fully.	5 / 5
Workflow Clarity	The flow is explicitly sequenced (flag parsing -> pre-setup check -> resume detection -> phases 1-4) with concrete validation checkpoints (coordinator handshake, exit-status validation, fail-closed on protocol disagreement) and explicit interrupt/resume feedback loops, satisfying the destructive/batch validation requirement.	5 / 5
Progressive Disclosure	It acts as an overview that delegates each phase to a separate phases/0X-*.md file with one-level-deep, clearly signaled references, but no references/scripts/assets bundle is present to verify against, leaving minor uncertainty about organization.	4 / 5
	Total	17 / 20 Passed

Description

43%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 clearly identifies the product and setup scope but lacks an explicit 'Use when...' trigger clause and natural trigger terms, which caps completeness and trigger quality. Specificity is adequate but not comprehensive.

Suggestions

Add an explicit trigger clause, e.g. 'Use when the user wants to set up, update, repair, or reconfigure oh-my-claudecode (OMC).'

Include natural user phrases like 'set up OMC', 'update my OMC config', or 'repair my OMC setup' alongside the product name.

Expand the action list to cover the concrete capabilities (configure CLAUDE.md, set up HUD/statusline, configure MCP and team-mode defaults) so coverage is comprehensive.

Dimension	Reasoning	Score
Specificity	The description names the domain (oh-my-claudecode setup) and a couple of concrete actions ('Install or refresh'), but the action verbs are generic and it omits the full range of what the skill does (configure, repair, update CLAUDE.md), so coverage is not comprehensive.	3 / 5
Completeness	It gives a clear 'what' (install/refresh oh-my-claudecode for plugin, npm, and local-dev setups) but has no 'Use when...' clause or equivalent explicit trigger guidance, which caps completeness at 3 per the rubric.	3 / 5
Trigger Term Quality	It relies on the product name 'oh-my-claudecode' and setup/install jargon but lacks the natural phrases a user would actually say ('set up OMC', 'update my OMC config', 'repair my setup'), so the natural keyword coverage is minimal.	2 / 5
Distinctiveness Conflict Risk	The product-specific scope (oh-my-claudecode setup across plugin/npm/local-dev) gives it a clear niche with minimal overlap risk against other skills, though the generic 'Install or refresh' verb leaves minor ambiguity versus a generic installer.	4 / 5
	Total	12 / 20 Passed

Validation

87%

Warnings & errors only

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

Validation — 14 / 16 Passed

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning
referenced_paths_exist	Referenced path issues: 2 missing	Warning

	Total	14 / 16 Passed

Repository: Yeachan-Heo/oh-my-claudecode
Path: skills/omc-setup/SKILL.md
Commit: 5aa678c

Reviewed: 8 days ago

Table of Contents

Discovery Implementation Validation

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.