omc-setup

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

Quality

66%

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

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

A well-structured orchestrator skill with concrete commands, a clear phase sequence, and sound validation/fail-closed design. Its main weaknesses are duplicated and padded prose (help text, update section) and reliance on phase files that cannot be verified from this bundle.

Suggestions

Deduplicate the coordinator-validation sentences shared by the --local and --global help entries into one line, and drop the marketing opener ("This is the only command you need to learn") to save tokens.

Replace the 'Keeping Up to Date' section with a one-line pointer to the already-configured flow it restates.

Add a short error-recovery loop for coordinator/setup-script failure (e.g., what to report and whether to re-run or abort) to close the workflow-clarity gap.

Dimension	Reasoning	Score
Conciseness	Mostly efficient decision logic, but padding exists: the marketing line "This is the only command you need to learn", near-duplicate coordinator-validation sentences in both the --local and --global help entries, and a "Keeping Up to Date" section that restates the already-configured flow.	3 / 5
Actionability	Copy-paste commands ("bash \"${OMC_SETUP_PLUGIN_ROOT:-${CLAUDE_PLUGIN_ROOT}}/scripts/setup-claude-md.sh\" <local\|global>"), a complete executable pre-setup check with jq validation and exit-1 error paths, and concrete AskUserQuestion prompts. Minor gaps: placeholder arguments like <local\|global> and phase execution deferred to files not shown.	4 / 5
Workflow Clarity	Clear sequence (flag parsing -> pre-setup check -> resume detection -> phases 1-4 -> completion) with validation checkpoints (jq config validation, coordinator fails closed on status disagreement). Not 5 because explicit error-recovery loops (what to do when the coordinator script fails mid-setup) are absent.	4 / 5
Progressive Disclosure	The overview delegates phases to four clearly signaled one-level-deep phase files plus two scripts. Minor gaps: no bundle files exist to verify the referenced paths resolve, and the ~50-line help text is fully inlined.	4 / 5
	Total	15 / 20 Passed

Description

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

A concise, product-specific description with a clear 'what' and good domain keywords. It loses points for having no explicit 'when to use' trigger clause and only two named actions.

Suggestions

Add an explicit trigger clause, e.g., "Use when the user wants to set up, update, or repair oh-my-claudecode" — this lifts completeness from 3 to 5.

Broaden action coverage to include repair/reconfigure (the body supports these) and add synonyms like "update" and "OMC" to strengthen trigger terms.

Dimension	Reasoning	Score
Specificity	"Install or refresh" names two concrete actions on a specific domain (oh-my-claudecode setups), matching the 1-2-action anchor; anchor 4 requires several actions and coverage of repair/configure is absent.	3 / 5
Completeness	The 'what' is clear (install or refresh oh-my-claudecode), but there is no 'Use when...' clause or equivalent trigger guidance, which caps completeness at 3 per the rubric guideline.	3 / 5
Trigger Term Quality	Natural terms users would say are present ("install", "refresh", "plugin", "npm", "local-dev"), but common synonyms like "update", "configure", or "OMC" are missing, so it stops short of comprehensive coverage.	4 / 5
Distinctiveness Conflict Risk	Names a specific product (oh-my-claudecode) with its own setup triggers, giving a clear niche with minimal conflict risk against other skills.	5 / 5
	Total	15 / 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: dc7ba1d

Reviewed: 3 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.