skill

Manage local skills - list, add, remove, search, edit, setup wizard

Quality

—

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Advisory

Suggest reviewing before use

Quality

Content

65%

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

The body is highly actionable with concrete commands, paths, and templates, and its workflows are clearly sequenced. Its main weaknesses are verbosity/redundancy and a lack of progressive disclosure into separate reference files for a skill this large.

Suggestions

Move large reusable blocks — the four skill templates and the bash scan script — into reference files under references/ and link to them from SKILL.md to improve progressive disclosure and reduce inline length.

Remove the duplicated 'Related Skills' section (it appears twice) and trim conceptual filler such as 'Benefits of Local Skills' and 'Future Enhancements' that does not guide execution.

Add post-action verification feedback loops to destructive/batch commands, e.g., after '/skill remove' re-scan to confirm the skill is gone, and after '/skill sync' validate the copied skill's YAML frontmatter.

Dimension	Reasoning	Score
Conciseness	The body is mostly actionable per section but is padded with redundant and conceptual material — a duplicated 'Related Skills' section, full example transcripts, a long bash scan script, plus 'Benefits', 'Tips for Users', and 'Future Enhancements' that could be tightened or removed.	2 / 3
Actionability	It provides concrete, executable guidance throughout: real bash commands, exact file paths, full YAML templates, and copy-paste-ready example transcripts for every subcommand.	3 / 3
Workflow Clarity	Multi-step processes are clearly sequenced with numbered steps, but destructive/batch operations (remove, sync) include confirmation yet lack validate-then-retry feedback loops or post-action verification, which caps workflow clarity at 2 per the rubric.	2 / 3
Progressive Disclosure	The skill is internally well-organized with clear headers, but it is a monolithic ~840-line single file with no bundle references, and content that could be split out (templates, the scan script) is kept inline.	2 / 3
	Total	9 / 12 Passed

Description

67%

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 specific and distinct, naming a clear niche and several concrete subcommands, but it omits any explicit 'when to use' guidance and lacks common trigger-term variations. Adding a 'Use when...' clause would raise its completeness and trigger coverage.

Suggestions

Append a 'Use when...' clause, e.g., 'Use when the user wants to list, create, remove, find, or edit local skills, or run the skills setup wizard.'

Add natural trigger variations users would actually say, such as 'create skill', 'delete skill', 'find skill', and 'organize skills'.

Avoid relying on bare generic verbs ('list', 'search', 'edit') as triggers; pair them consistently with 'skill' to reduce conflict risk.

Dimension	Reasoning	Score
Specificity	The description lists multiple concrete actions — 'list, add, remove, search, edit, setup wizard' — against the named domain of 'local skills', matching the anchor that lists several specific concrete actions.	3 / 3
Completeness	It clearly states what the skill does (manage local skills via subcommands) but provides no 'Use when...' clause or equivalent explicit trigger guidance, which caps completeness at 2 per the rubric.	2 / 3
Trigger Term Quality	Terms like 'local skills', 'list', 'search', and 'setup wizard' are reasonable but common conversational variations (e.g., 'create', 'delete', 'find', 'organize skills') are missing, so coverage is partial rather than complete.	2 / 3
Distinctiveness Conflict Risk	'Manage local skills' is a narrow, well-defined niche tied to skill-management operations, making it unlikely to trigger for unrelated skills despite the generic verbs used.	3 / 3
	Total	10 / 12 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
skill_md_line_count	SKILL.md is long (848 lines); consider splitting into references/ and linking	Warning
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	14 / 16 Passed

Repository: Yeachan-Heo/oh-my-claudecode
Commit: 6c59219

Reviewed: about 5 hours 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.