Agent skill

Skill Management CLI

by Yeachan-Heo in Yeachan-Heo/oh-my-claudecode

Manages local oh-my-claudecode skills with slash subcommands to list, add, remove, search and edit them, plus a setup wizard.

MITAuto-check passedAgent Workflows

Install Skill Management CLI

skills CLI
$ npx skills add Yeachan-Heo/oh-my-claudecode --skill skill -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install Yeachan-Heo/oh-my-claudecode skill --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/Yeachan-Heo/oh-my-claudecode.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/skill .claude/skills/skill && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
skill
GitHub stars
40k
Used in
1 other repo
Token cost
~5.6k tokens
SKILL.md length
1,250 words
Files
1
Skills in repo
47
Repo updated
First seen
Licence
MIT

At a glance

Manages local oh-my-claudecode skills with slash subcommands to list, add, remove, search and edit them, plus a setup wizard.

  • Works in 3 steps: Directory Check and Setup → Skill Scan and Inventory → Quick Actions Menu
  • Seeing which skills are installed at built-in, user and project scope
  • SKILL.md covers Subcommands, Skill Templates, Error Handling and Usage Examples, plus 9 more sections
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

A meta-skill that gives you CLI-style `/skill` subcommands for oh-my-claudecode skills. `/skill list` scans the bundled built-in skills, your user skills under `omc-learned` and the project skills in `.omc/skills/`, reads their YAML frontmatter and shows a table grouped by scope. Built-in skills can be listed and read but not removed or edited.

`/skill add` runs an interactive wizard that asks for a lowercase hyphenated name, a one-line description, trigger keywords, an optional argument hint and a scope of user or project, then writes a `SKILL.md` from a template and reports the path. `/skill remove` finds the skill in both scopes, shows its details, asks for confirmation and then deletes the whole skill directory. The description also lists search, edit and a setup wizard, which the excerpt does not reach.

When your agent uses it

  • Seeing which skills are installed at built-in, user and project scope
  • Creating a new local skill through a guided wizard
  • Removing an outdated user or project skill after confirmation
  • Looking up or editing an existing local skill

Example prompts

  • “/skill list to show me everything installed, grouped by scope.”
  • “Add a new project-scoped skill called custom-logger with triggers error, fix and debug.”
  • “Remove the old custom-logger skill from my user skills.”

Requirements

  • The oh-my-claudecode plugin

Workflow steps

3 steps, taken from the step headings in SKILL.md.

  1. Directory Check and Setup
  2. Skill Scan and Inventory
  3. Quick Actions Menu

What it can do on your machine

Read from SKILL.md and the folder at commit 454bae0. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md (its code samples are markdown, bash and yaml).

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Skill Management CLI loads about 5.6k tokens when it runs. Until then it costs about 18 tokens; SKILL.md has 1,250 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~18
When it runs · the whole SKILL.md, loaded when a task matches
~5.6k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from Yeachan-Heo/oh-my-claudecode at commit 454bae0, republished under its MIT licence (© Yeachan-Heo). 1,250 words, ~5,561 tokens.

Download SKILL.mdSave it as .claude/skills/skill/SKILL.md (or your agent's skills folder).
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:
yaml
---
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]
  1. Report success with file path
  2. 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: "typescript error handling patterns"

2. error-handler (user)
   Description: Generic error handling utilities
   Match: "Supports TypeScript and JavaScript errors"

3. lint-fix (project)
   Description: Auto-fix linting errors
   Match: "TypeScript ESLint error resolution"

Ranking: Prioritize matches in name/triggers over content matches

Example:

User: /skill search api endpoint
Assistant: Found 2 skills matching "api endpoint":

1. api-builder (user)
   Description: Generate REST API endpoints
   Triggers: api, endpoint, rest

2. backend-scaffold (project)
   Description: Scaffold backend services
   Match: "Creates API endpoint boilerplate"

/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:
Skill: custom-logger
Scope: user (~/.claude/skills/omc-learned/custom-logger/)
Description: Enhanced logging with structured output
Triggers: log, logger, logging
Argument Hint: <level> [message]
Quality: 95% (if available)
Usage Count: 42 times (if available)
File Path: /home/user/.claude/skills/omc-learned/custom-logger/SKILL.md

--- FULL CONTENT ---
[entire markdown content]

If not found: Report error with suggestion to use /skill search

Example:

User: /skill info custom-logger
Assistant: Skill: custom-logger
Scope: user
Description: Enhanced logging with structured output
Triggers: log, logger, logging
File: ~/.claude/skills/omc-learned/custom-logger/SKILL.md

--- CONTENT ---
# Custom Logger Skill

## Purpose
Enhanced logging with structured JSON output...
[rest of content]

/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:
SYNC REPORT:

User-only skills (5):
  - error-handler
  - api-builder
  - custom-logger
  - test-generator
  - deploy-helper

Project-only skills (2):
  - test-runner
  - backend-scaffold

Common skills (3):
  - frontend-ui-ux
  - git-master
  - planner

Options:
  [1] Copy user skill to project
  [2] Copy project skill to user
  [3] View differences
  [4] Cancel
  1. 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:

User: /skill sync
Assistant: Found 5 user-only skills and 2 project-only skills.

Copy 'error-handler' from user to project? (yes/no/skip)
User: yes
Assistant: ✓ Copied 'error-handler' to .omc/skills/

Copy 'api-builder' from user to project? (yes/no/skip)
User: skip
...

/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:

bash
# Check and create user-level skills directory
USER_SKILLS_DIR="${CLAUDE_CONFIG_DIR:-$HOME/.claude}/skills/omc-learned"
if [ -d "$USER_SKILLS_DIR" ]; then
  echo "User skills directory exists: $USER_SKILLS_DIR"
else
  mkdir -p "$USER_SKILLS_DIR"
  echo "Created user skills directory: $USER_SKILLS_DIR"
fi

# Check and create project-level skills directory
PROJECT_SKILLS_DIR=".omc/skills"
if [ -d "$PROJECT_SKILLS_DIR" ]; then
  echo "Project skills directory exists: $PROJECT_SKILLS_DIR"
else
  mkdir -p "$PROJECT_SKILLS_DIR"
  echo "Created project skills directory: $PROJECT_SKILLS_DIR"
fi
Step 2: Skill Scan and Inventory

Scan both directories and show a comprehensive inventory:

bash
# Scan user-level skills
echo "=== USER-LEVEL SKILLS (~/.claude/skills/omc-learned/) ==="
if [ -d "${CLAUDE_CONFIG_DIR:-$HOME/.claude}/skills/omc-learned" ]; then
  USER_COUNT=$(find "${CLAUDE_CONFIG_DIR:-$HOME/.claude}/skills/omc-learned" -name "*.md" 2>/dev/null | wc -l)
  echo "Total skills: $USER_COUNT"

  if [ $USER_COUNT -gt 0 ]; then
    echo ""
    echo "Skills found:"
    find "${CLAUDE_CONFIG_DIR:-$HOME/.claude}/skills/omc-learned" -name "*.md" -type f -exec sh -c '
      FILE="$1"
      NAME=$(grep -m1 "^name:" "$FILE" 2>/dev/null | sed "s/name: //")
      DESC=$(grep -m1 "^description:" "$FILE" 2>/dev/null | sed "s/description: //")
      MODIFIED=$(stat -c "%y" "$FILE" 2>/dev/null || stat -f "%Sm" "$FILE" 2>/dev/null)
      echo "  - $NAME"
      [ -n "$DESC" ] && echo "    Description: $DESC"
      echo "    Modified: $MODIFIED"
      echo ""
    ' sh {} \;
  fi
else
  echo "Directory not found"
fi

echo ""
echo "=== PROJECT-LEVEL SKILLS (.omc/skills/) ==="
if [ -d ".omc/skills" ]; then
  PROJECT_COUNT=$(find ".omc/skills" -name "*.md" 2>/dev/null | wc -l)
  echo "Total skills: $PROJECT_COUNT"

  if [ $PROJECT_COUNT -gt 0 ]; then
    echo ""
    echo "Skills found:"
    find ".omc/skills" -name "*.md" -type f -exec sh -c '
      FILE="$1"
      NAME=$(grep -m1 "^name:" "$FILE" 2>/dev/null | sed "s/name: //")
      DESC=$(grep -m1 "^description:" "$FILE" 2>/dev/null | sed "s/description: //")
      MODIFIED=$(stat -c "%y" "$FILE" 2>/dev/null || stat -f "%Sm" "$FILE" 2>/dev/null)
      echo "  - $NAME"
      [ -n "$DESC" ] && echo "    Description: $DESC"
      echo "    Modified: $MODIFIED"
      echo ""
    ' sh {} \;
  fi
else
  echo "Directory not found"
fi

# Summary
TOTAL=$((USER_COUNT + PROJECT_COUNT))
echo "=== SUMMARY ==="
echo "Total skills across all directories: $TOTAL"
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.


Show full SKILL.md (495 more words)Show less

Skill Templates

When creating skills via /skill add or /skill setup, offer quick templates for common skill types:

Error Solution Template
markdown
---
id: error-[unique-id]
name: [Error Name]
description: Solution for [specific error in specific context]
source: conversation
triggers: ["error message fragment", "file path", "symptom"]
quality: high
---

# [Error Name]

## The Insight
What is the underlying cause of this error? What principle did you discover?

## Why This Matters
What goes wrong if you don't know this? What symptom led here?

## Recognition Pattern
How do you know when this applies? What are the signs?
- Error message: "[exact error]"
- File: [specific file path]
- Context: [when does this occur]

## The Approach
Step-by-step solution:
1. [Specific action with file/line reference]
2. [Specific action with file/line reference]
3. [Verification step]

## Example
\`\`\`typescript
// Before (broken)
[problematic code]

// After (fixed)
[corrected code]
\`\`\`
Workflow Skill Template
markdown
---
id: workflow-[unique-id]
name: [Workflow Name]
description: Process for [specific task in this codebase]
source: conversation
triggers: ["task description", "file pattern", "goal keyword"]
quality: high
---

# [Workflow Name]

## The Insight
What makes this workflow different from the obvious approach?

## Why This Matters
What fails if you don't follow this process?

## Recognition Pattern
When should you use this workflow?
- Task type: [specific task]
- Files involved: [specific patterns]
- Indicators: [how to recognize]

## The Approach
1. [Step with specific commands/files]
2. [Step with specific commands/files]
3. [Verification]

## Gotchas
- [Common mistake and how to avoid it]
- [Edge case and how to handle it]
Code Pattern Template
markdown
---
id: pattern-[unique-id]
name: [Pattern Name]
description: Pattern for [specific use case in this codebase]
source: conversation
triggers: ["code pattern", "file type", "problem domain"]
quality: high
---

# [Pattern Name]

## The Insight
What's the key principle behind this pattern?

## Why This Matters
What problems does this pattern solve in THIS codebase?

## Recognition Pattern
When do you apply this pattern?
- File types: [specific files]
- Problem: [specific problem]
- Context: [codebase-specific context]

## The Approach
Decision-making heuristic, not just code:
1. [Principle-based step]
2. [Principle-based step]

## Example
\`\`\`typescript
[Illustrative example showing the principle]
\`\`\`

## Anti-Pattern
What NOT to do and why:
\`\`\`typescript
[Common mistake to avoid]
\`\`\`
Integration Skill Template
markdown
---
id: integration-[unique-id]
name: [Integration Name]
description: How [system A] integrates with [system B] in this codebase
source: conversation
triggers: ["system name", "integration point", "config file"]
quality: high
---

# [Integration Name]

## The Insight
What's non-obvious about how these systems connect?

## Why This Matters
What breaks if you don't understand this integration?

## Recognition Pattern
When are you working with this integration?
- Files: [specific integration files]
- Config: [specific config locations]
- Symptoms: [what indicates integration issues]

## The Approach
How to work with this integration correctly:
1. [Configuration step with file paths]
2. [Setup step with specific details]
3. [Verification step]

## Gotchas
- [Integration-specific pitfall #1]
- [Integration-specific pitfall #2]

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:

✗ Error: <clear message>
→ Suggestion: <helpful next step>

Usage Examples

bash
# List all skills
/skill list

# Create a new skill
/skill add my-custom-skill

# Remove a skill
/skill remove old-skill

# Edit existing skill
/skill edit error-handler

# Search for skills
/skill search typescript error

# Get detailed info
/skill info my-custom-skill

# Sync between scopes
/skill sync

# Run setup wizard
/skill setup

# Quick scan
/skill scan

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"

  • /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

> /oh-my-claudecode:skill list

Checking skill directories...
✓ User skills directory exists: ~/.claude/skills/omc-learned/
✓ Project skills directory exists: .omc/skills/

Scanning for skills...

=== USER-LEVEL SKILLS ===
Total skills: 3
  - async-network-error-handling
    Description: Pattern for handling independent I/O failures in async network code
    Modified: 2026-01-20 14:32:15

  - esm-path-resolution
    Description: Custom path resolution in ESM requiring fileURLToPath
    Modified: 2026-01-19 09:15:42

=== PROJECT-LEVEL SKILLS ===
Total skills: 5
  - session-timeout-fix
    Description: Fix for sessionId undefined after restart in session.ts
    Modified: 2026-01-22 16:45:23

  - build-cache-invalidation
    Description: When to clear TypeScript build cache to fix phantom errors
    Modified: 2026-01-21 11:28:37

=== SUMMARY ===
Total skills: 8

What would you like to do?
1. Add new skill
2. List all skills with details
3. Scan conversation for patterns
4. Import skill
5. Done

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)

  • /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

© Yeachan-Heo, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in skills/skill of Yeachan-Heo/oh-my-claudecode.

Open the folder on GitHubat commit 454bae0

Used in 1 other repository

We found 1 copy of this SKILL.md (exact, near-identical or edited) in other folders, from 1 other GitHub owner. This page covers the copy in Yeachan-Heo/oh-my-claudecode, which our catalogue first saw on October 7, 2026.

Compare with similar skills

Skill Management CLI next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Skill Management CLI compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Skill Management CLI this skillYeachan-Heo/oh-my-claudecode40k1 repos~5.6kAutomated safety check: PassMIT
Darwin Skill Optimizeralchaincyf/darwin-skill6.2k1 repos~4.7kAutomated safety check: PassMIT
Skill Creatorzhayujie/CowAgent47k—~4.7kAutomated safety check: NotesMIT
Open-Science Skill Creatoraipoch/open-science5.5k—~1.7kAutomated safety check: PassApache-2.0
Skill Quality ReviewerGalaxy-Dawn/claude-scholar5.7k1 repos~3kAutomated safety check: PassMIT
Prismer Skill CreatorPrismer-AI/PrismerCloud1.6k—~2.6kAutomated safety check: NotesMIT

Similar skills

  • Darwin Skill Optimizer

    alchaincyf/darwin-skill

    Scores SKILL.md files on a nine-dimension rubric, then improves them in a keep-or-revert loop with independent judge agents, test prompts, git history and human checkpoints.

    6.2k GitHub starsUsed in 1 repo~4.7k tokens
    Agent WorkflowsAuto-check passed
  • Skill Creator

    zhayujie/CowAgent

    Guides creating, installing and updating agent skills in a workspace: SKILL.md frontmatter, bundled scripts and references, with scripts to scaffold, validate and package.

    47k GitHub stars~4.7k tokensUpdated today
    Agent WorkflowsAuto-check: notes
  • Open-Science Skill Creator

    aipoch/open-science

    Creates, revises, evaluates and publishes skills in the Open-Science app through its native host.skills composer, with optional test prompts and benchmarks.

    5.5k GitHub stars~1.7k tokensUpdated today
    Agent WorkflowsAuto-check passed
  • Skill Quality Reviewer

    Galaxy-Dawn/claude-scholar

    Scores a skill across description, content organization, writing style and structure, then produces letter grades and a prioritized improvement plan.

    5.7k GitHub starsUsed in 1 repo~3k tokens
    Agent WorkflowsAuto-check passed
  • Prismer Skill Creator

    Prismer-AI/PrismerCloud

    Walks an agent through creating, importing, editing, validating, testing and publishing Prismer Skills with a fixed workflow and bundled scripts.

    1.6k GitHub stars~2.6k tokensUpdated 9 days ago
    Agent WorkflowsAuto-check: notes
  • Skill Factory

    sangrokjung/claude-forge

    Analyze session work and automatically convert reusable patterns into Claude Code skills.

    852 GitHub stars~2.7k tokensUpdated 1 mo ago
    Agent WorkflowsAuto-check passed

More from Yeachan-Heo/oh-my-claudecode

All 47 skills in this repo
  • Ask Advisor Routing

    Yeachan-Heo/oh-my-claudecode

    Sends a question or task to another locally installed agent CLI, such as Codex or Gemini, through omc ask and saves the answer as a file.

    40k GitHub stars~572 tokensUpdated yesterday
    Auto-check passed
  • Ask Navigator

    Yeachan-Heo/oh-my-claudecode

    Charts a foggy effort into a map of decision tickets on the repo's issue tracker and works through them one per session, producing decisions rather than deliverables.

    40k GitHub stars~4.1k tokensUpdated yesterday
    Auto-check passed
  • Self-Improve Evolutionary Loop

    Yeachan-Heo/oh-my-claudecode

    Runs an autonomous improvement loop on a repository: agents propose and execute plans, a tournament picks the winner by benchmark, and each round is recorded and plotted.

    40k GitHub stars~5.3k tokensUpdated yesterday
    Auto-check: warnings
  • Autopilot

    Yeachan-Heo/oh-my-claudecode

    Takes a short product idea through requirements, design, planning, parallel implementation, QA cycles and multi-reviewer validation to produce working code.

    40k GitHub stars~4.4k tokensUpdated yesterday
    Auto-check passed
  • OMC Mode Cancellation

    Yeachan-Heo/oh-my-claudecode

    Detects and gracefully cancels whichever OMC mode, autopilot, ralph, swarm, pipeline, or team, is currently active, then clears its state.

    40k GitHub stars~4.6k tokensUpdated yesterday
    Auto-check passed
  • Hierarchical AGENTS.md Generator

    Yeachan-Heo/oh-my-claudecode

    Maps a codebase directory by directory and writes linked AGENTS.md files, each pointing to its parent, to document what each area contains.

    40k GitHub stars~2.3k tokensUpdated yesterday
    Auto-check passed

Categories

Questions about Skill Management CLI

What does Skill Management CLI do?

Manages local oh-my-claudecode skills with slash subcommands to list, add, remove, search and edit them, plus a setup wizard. A meta-skill that gives you CLI-style `/skill` subcommands for oh-my-claudecode skills.omc/skills/`, reads their YAML frontmatter and shows a table grouped by scope.

When should I use Skill Management CLI?

Skill Management CLI fits situations like: seeing which skills are installed at built-in, user and project scope; creating a new local skill through a guided wizard; removing an outdated user or project skill after confirmation; looking up or editing an existing local skill.

How do I install Skill Management CLI in Claude Code?

Run `npx skills add Yeachan-Heo/oh-my-claudecode --skill skill -a claude-code`. Or copy the skill folder (skills/skill in Yeachan-Heo/oh-my-claudecode) into .claude/skills/skill in your project. Claude Code loads it when a task matches its description.

How do I install Skill Management CLI in Codex?

Run `npx skills add Yeachan-Heo/oh-my-claudecode --skill skill -a codex`. Or copy the skill folder (skills/skill in Yeachan-Heo/oh-my-claudecode) into .agents/skills/skill in your project. Codex loads it when a task matches its description.

Can I use Skill Management CLI in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add Yeachan-Heo/oh-my-claudecode --skill skill -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/skill, .gemini/skills/skill, .github/skills/skill and .opencode/skills/skill in your project.

What does Skill Management CLI need to run?

SKILL.md names no scripts, command-line tools or credentials: Skill Management CLI is instructions for the agent only. Our summary lists: The oh-my-claudecode plugin.

Does Skill Management CLI access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Skill Management CLI safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Skill Management CLI use?

Skill Management CLI is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Skill Management CLI use?

About 5.6k tokens (SKILL.md is roughly 22k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Skill Management CLI?

Skills that share tags, products or a category with Skill Management CLI: Darwin Skill Optimizer (alchaincyf/darwin-skill, 6.2k stars), Skill Creator (zhayujie/CowAgent, 47k stars), Open-Science Skill Creator (aipoch/open-science, 5.5k stars) and Skill Quality Reviewer (Galaxy-Dawn/claude-scholar, 5.7k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Skill Management CLI?

Yeachan-Heo (a GitHub user) maintains it in Yeachan-Heo/oh-my-claudecode, which has 39,720 GitHub stars. The repository holds 47 skills in this directory. The repository was last updated on October 8, 2026.

Source: Yeachan-Heo/oh-my-claudecode on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.