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: 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: /oh my claudecode:<name example arg 7. Report success with file path 8. Suggest: "Edit /skill edit <name to customize content" Example: /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: /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: 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: /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: Ranking: Prioritize matches in name/triggers over content matches Example: /skill info <name Show detailed information about a skill. Behavior: 1. Find skill by name (search both scopes) 2. Parse YAML frontmatter and content 3. Display complete details: If not found: Report error with suggestion to use /skill search Example: /skill sync Sync skills between user and project scopes. Behavior: 1. Scan both scopes: User skills: ${CLAUDE CONFIG DIR: ~/.claude}/skills/omc learned/ Project skills: .omc/skills/ 2. Compare and categorize: User only skills (not in project) Project only skills (not in user) Common skills (in both) 3. Display sync opportunities: 4. Handle user choice: Option 1: Select skill(s) to copy to project Option 2: Select skill(s) to copy to user Option 3: Show side by side diff for common skills Option 4: Exit Safety: Never overwrite without confirmation Example: /skill setup Interactive wizard for setting up and managing local skills (formerly local skills setup). Behavior: Step 1: Directory Check and Setup First, check if skill directories exist and create them if needed: Step 2: Skill Scan and Inventory Scan both directories and show a comprehensive inventory: Step 3: Quick Actions Menu After scanning, use the AskUserQuestion tool to offer these options: Question: "What would you like to do with your local skills?" Options: 1. Add new skill Start the skill creation wizard (invoke /skill add ) 2. List all skills with details Show comprehensive skill inventory (invoke /skill list ) 3. Scan conversation for patterns Analyze current conversation for skill worthy patterns 4. Import skill Import a skill from URL or paste content 5. Done Exit the wizard Option 3: Scan Conversation for Patterns Analyze the current conversation context to identify potential skill worthy patterns. Look for: Recent debugging sessions with non obvious solutions Tricky bugs that required investigation Codebase specific workarounds discovered Error patterns that took time to resolve Report findings and ask if user wants to extract any as skills (invoke /skillify ; /learner is deprecated compatibility). Option 4: Import Skill Ask user to provide either: URL : Download skill from a URL (e.g., GitHub gist) Paste content : Paste skill markdown content directly Then ask for scope: User level (~/.claude/skills/omc learned/) Available across all projects Project level (.omc/skills/) Only for this project Validate the skill format and save to the chosen location. /skill scan Quick command to scan both skill directories (subset of /skill setup ). Behavior: Run the scan from Step 2 of /skill setup without the interactive wizard. Skill Templates When creating skills via /skill add or /skill setup , offer quick templates for common skill types: Error Solution Template Workflow Skill Template Code Pattern Template Integration Skill Template Error Handling All commands must handle: File/directory doesn't exist Permission errors Invalid YAML frontmatter Duplicate skill names Invalid skill names (spaces, special chars) Error format: Usage Examples Usage Modes Direct Command Mode When invoked with an argument, skip the interactive wizard: /oh my claudecode:skill list Show detailed skill inventory /oh my claudecode:skill add Start skill creation (invoke skillify) /oh my claudecode:skill scan Scan both skill directories Interactive Mode When invoked without arguments, run the full guided wizard. Benefits of Local Skills Automatic Application : Claude detects triggers and applies skills automatically no need to remember or search for solutions. Version Control : Project level skills ( .omc/skills/ ) are intended to be committed with your code so the whole team benefits. In linked worktrees, uncommitted skills remain local to that worktree and disappear if it is removed. Evolving Knowledge : Skills improve over time as you discover better approaches and refine triggers. Reduced Token Usage : Instead of re solving the same problems, Claude applies known patterns efficiently. Codebase Memory : Preserves institutional knowledge that would otherwise be lost in conversation history. Skill Quality Guidelines Good skills are: 1. Non Googleable Can't easily find via search BAD: "How to read files in TypeScript" GOOD: "This codebase uses custom path resolution requiring fileURLToPath" 2. Context Specific References actual files/errors from THIS codebase BAD: "Use try/catch for error handling" GOOD: "The aiohttp proxy in server.py:42 crashes on ClientDisconnectedError" 3. Actionable with Precision Tells exactly WHAT to do and WHERE BAD: "Handle edge cases" GOOD: "When seeing 'Cannot find module' in dist/, check tsconfig.json moduleResolution" 4. Hard Won Required significant debugging effort BAD: Generic programming patterns GOOD: "Race condition in worker.ts Promise.all at line 89 needs await" Related Skills /oh my claudecode:skillify Extract a skill from current conversation ( /oh my claudecode:learner is a deprecated alias) /oh my claudecode:note Save quick notes (less formal than skills) /oh my claudecode:deepinit Generate AGENTS.md codebase hierarchy Example Session Tips for Users Run /oh my claudecode:skill list periodically to review your skill library After solving a tricky bug, immediately run skillify to capture it Use project level skills for codebase specific knowledge Use user level skills for general patterns that apply everywhere Review and refine triggers over time to improve matching accuracy Implementation Notes 1. YAML Parsing: Use frontmatter extraction for metadata 2. File Operations: Use Read/Write tools, never Edit for new files 3. User Confirmation: Always confirm destructive operations 4. Clear Feedback: Use checkmarks (✓), crosses (✗), arrows (→) for clarity 5. Scope Resolution: Always check both user and project scopes 6. Validation: Enforce naming conventions (lowercase, hyphens only) Related Skills /oh my claudecode:skillify Extract a skill from current conversation ( /oh my claudecode:learner is a deprecated alias) /oh my claudecode:note Save quick notes (less formal than skills) /oh my claudecode:deepinit Generate AGENTS.md codebase hierarchy Future Enhancements /skill export <name Export skill as shareable file /skill import <file Import skill from file /skill stats Show usage statistics across all skills /skill validate Check all skills for format errors /skill template <type Create from predefined templates