skill
Manage local skills - list, add, remove, search, edit, setup wizard
53
43%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Advisory
Suggest reviewing before use
Optimize this skill with Tessl
npx tessl skill review --optimize ./skills/skill/SKILL.mdQuality
Discovery
32%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 provides a basic list of actions but lacks the explicit trigger guidance ('Use when...') that is critical for skill selection. The terse comma-separated format conveys functionality but doesn't help Claude understand when to choose this skill over others. Adding explicit trigger conditions and more natural user language would significantly improve discoverability.
Suggestions
Add a 'Use when...' clause specifying triggers like 'when the user wants to manage, create, or modify skills' or 'when asked about skill configuration'
Expand the action keywords into more descriptive phrases (e.g., 'create new skills', 'remove existing skills', 'search available skills')
Include natural user phrases like 'skill management', 'configure skills', 'skill setup', or 'my skills' to improve trigger term coverage
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists several actions (list, add, remove, search, edit, setup wizard) but they are terse keywords rather than fully described concrete actions. The domain 'local skills' is named but capabilities aren't elaborated. | 2 / 3 |
Completeness | Only answers 'what' at a basic level. Completely missing any 'Use when...' clause or explicit trigger guidance for when Claude should select this skill. | 1 / 3 |
Trigger Term Quality | Contains some relevant terms like 'skills', 'add', 'remove', 'search', 'edit' that users might say, but missing natural variations like 'create skill', 'delete skill', 'find skill', or 'skill management'. | 2 / 3 |
Distinctiveness Conflict Risk | 'Local skills' provides some specificity, but generic verbs like 'add', 'remove', 'search', 'edit' could overlap with many other management-type skills without the 'skills' context being prominent enough. | 2 / 3 |
Total | 7 / 12 Passed |
Implementation
55%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill is highly actionable with excellent workflow clarity and explicit safety confirmations for destructive operations. However, it severely violates conciseness principles with massive redundancy, duplicate sections, and inline content that should be split into separate reference files. The lack of progressive disclosure makes this a 600+ line monolith when it could be a 100-line overview with linked references.
Suggestions
Extract skill templates into a separate TEMPLATES.md file and reference it with a one-line link
Move bash scripts to separate .sh files or a SCRIPTS.md reference document
Remove the duplicate 'Related Skills' section and consolidate redundant content
Trim verbose examples - show one complete example per subcommand, not multiple variations with full output
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Extremely verbose at 600+ lines with significant redundancy. Templates are repeated in full, examples are overly detailed, and there's substantial duplication (e.g., 'Related Skills' section appears twice, multiple lengthy bash scripts). Much content explains obvious concepts Claude already knows. | 1 / 3 |
Actionability | Highly actionable with complete executable bash scripts, specific file paths, exact YAML templates, and copy-paste ready examples. Every subcommand has concrete implementation details with specific commands and expected outputs. | 3 / 3 |
Workflow Clarity | Clear multi-step workflows with explicit validation and confirmation steps. Destructive operations (remove, sync) require user confirmation. Each subcommand has numbered steps with clear sequencing and error handling patterns defined. | 3 / 3 |
Progressive Disclosure | Monolithic wall of text with no references to external files. All templates, all subcommands, all examples are inline. Content that should be in separate files (templates, bash scripts, detailed examples) bloats the main skill file significantly. | 1 / 3 |
Total | 8 / 12 Passed |
Validation
81%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 9 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
skill_md_line_count | SKILL.md is long (839 lines); consider splitting into references/ and linking | Warning |
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 9 / 11 Passed | |
- Repository
- Yeachan-Heo/oh-my-claudecode
- Commit
48ffaac
- 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.