/skill

name: skill
description: Manage local skills - list, add, remove, search, edit, setup wizard
argument-hint: "<command> [args]"
level: 2

Skill Management CLI

Meta-skill for managing oh-my-claudecode skills via CLI-like commands.

Subcommands

/skill list

Show all available skills organized by scope.

**Behavior:** 1. Scan bundled built-in skills in the plugin `skills/` directory (read-only) 2. Scan user skills at `${CLAUDE_CONFIG_DIR:-~/.claude}/skills/omc-learned/` 3. Scan project skills at `.omc/skills/` 4. Parse YAML frontmatter for metadata 5. Display in organized table format:

BUILT-IN SKILLS (bundled with oh-my-claudecode):
| Name              | Description                    | Scope    |
|-------------------|--------------------------------|----------|
| visual-verdict    | Structured visual QA verdicts  | built-in |
| ralph             | Persistence loop               | built-in |

USER SKILLS (~/.claude/skills/omc-learned/):
| Name              | Triggers           | Quality | Usage | Scope |
|-------------------|--------------------|---------|-------|-------|
| error-handler     | fix, error         | 95%     | 42    | user  |
| api-builder       | api, endpoint      | 88%     | 23    | user  |

PROJECT SKILLS (.omc/skills/):
| Name              | Triggers           | Quality | Usage | Scope   |
|-------------------|--------------------|---------|-------|---------|
| test-runner       | test, run          | 92%     | 15    | project |

**Fallback:** If quality/usage stats not available, show "N/A"

**Built-in skill note:** Built-in skills are bundled with oh-my-claudecode and are discoverable/readable, but not removed or edited through `/skill remove` or `/skill edit`.

---

/skill add [name]

Interactive wizard for creating a new skill.

**Behavior:** 1. **Ask for skill name** (if not provided in command)

• Validate: lowercase, hyphens only, no spaces

2. **Ask for description**

• Clear, concise one-liner

3. **Ask for triggers** (comma-separated keywords)

• Example: "error, fix, debug"

4. **Ask for argument hint** (optional)

• Example: "<file> [options]"

5. **Ask for scope:**

• `user` → `${CLAUDE_CONFIG_DIR:-~/.claude}/skills/omc-learned/<name>/SKILL.md`
• `project` → `.omc/skills/<name>/SKILL.md`

6. **Create skill file** with template:

---
name: <name>
description: <description>
triggers:
  - <trigger1>
  - <trigger2>
argument-hint: "<args>"
---

# <Name> Skill

## Purpose

[Describe what this skill does]

## When to Activate

[Describe triggers and conditions]

## Workflow

1. [Step 1]
2. [Step 2]
3. [Step 3]

## Examples

/oh-my-claudecode:<name> example-arg

## Notes

[Additional context, edge cases, gotchas]

7. **Report success** with file path 8. **Suggest:** "Edit `/skill edit <name>` to customize content"

**Example:**

User: /skill add custom-logger
Assistant: Creating new skill 'custom-logger'...

Description: Enhanced logging with structured output
Triggers (comma-separated): log, logger, logging
Argument hint (optional): <level> [message]
Scope (user/project): user

✓ Created skill at ~/.claude/skills/omc-learned/custom-logger/SKILL.md
→ Edit with: /skill edit custom-logger

---

/skill remove <name>

Remove a skill by name.

**Behavior:** 1. **Search for skill** in both scopes:

• `${CLAUDE_CONFIG_DIR:-~/.claude}/skills/omc-learned/<name>/SKILL.md`
• `.omc/skills/<name>/SKILL.md`

2. **If found:**

• Display skill info (name, description, scope)
• **Ask for confirmation:** "Delete '<name>' skill from <scope>? (yes/no)"

3. **If confirmed:**

• Delete entire skill directory (e.g., `${CLAUDE_CONFIG_DIR:-~/.claude}/skills/omc-learned/<name>/`)
• Report: "✓ Removed skill '<name>' from <scope>"

4. **If not found:**

• Report: "✗ Skill '<name>' not found in user or project scope"

**Safety:** Never delete without explicit user confirmation.

**Example:**

User: /skill remove old-logger
Assistant: Found skill 'old-logger' in user scope:
  Description: Legacy logging utility
  Scope: user (~/.claude/skills/omc-learned/)

Delete 'old-logger' skill? (yes/no)

User: yes
Assistant: ✓ Removed skill 'old-logger' from user scope

---

/skill edit <name>

Edit an existing skill interactively.

**Behavior:** 1. **Find skill** by name (search both scopes) 2. **Read current content** via Read tool 3. **Display current values:**

   Current skill 'custom-logger':
   - Description: Enhanced logging with structured output
   - Triggers: log, logger, logging
   - Argument hint: <level> [message]
   - Scope: user

4. **Ask what to change:**

• `description` - Update description
• `triggers` - Update trigger keywords
• `argument-hint` - Update argument hint
• `content` - Edit full markdown content
• `rename` - Rename skill (move file)
• `cancel` - Exit without changes

5. **For selected field:**

• Show current value
• Ask for new value
• Update YAML frontmatter or content
• Write back to file

6. **Report success** with summary of changes

**Example:**

User: /skill edit custom-logger
Assistant: Current skill 'custom-logger':
  - Description: Enhanced logging with structured output
  - Triggers: log, logger, logging
  - Argument hint: <level> [message]

What would you like to edit? (description/triggers/argument-hint/content/rename/cancel)

User: triggers
Assistant: Current triggers: log, logger, logging
New triggers (comma-separated): log, logger, logging, trace

✓ Updated triggers for 'custom-logger'

---

/skill search <query>

Search skills by content, triggers, name, or description.

**Behavior:** 1. **Scan all skills** in both scopes 2. **Match query** (case-insensitive) against:

• Skill name
• Description
• Triggers
• Full markdown content

3. **Display matches** with context:

Found 3 skills matching "typescript error":

1. typescript-fixer (user)
   Description: Fix common TypeScript errors
   Match: "typescri