How to use the Local Skill Manager agent skill

What the skill makes the agent do

Once installed, the skill gives you a set of commands that look like /skill list, /skill add, /skill edit, /skill search, /skill info, /skill remove and /skill sync. When you use one, the agent reads, creates, changes or deletes skill folders in your user skill directory or in your project's skill directory.

The skill works step by step. For example, when you add a skill it asks for a name, a description, trigger keywords, an optional argument hint and a scope, then creates the SKILL.md file for you. Before deleting anything, it asks you to confirm.

• List: shows built-in, user and project skills in tables.
• Add: a wizard that creates a new skill folder and SKILL.md file.
• Edit: change the description, triggers, argument hint, content or name of an existing skill.
• Search: finds skills by name, description, triggers or full content.
• Remove: deletes a skill folder after you answer yes to a confirmation question.
• Built-in skills that ship with oh-my-claudecode are read-only and cannot be removed or edited through this tool.

Install the Local Skill Manager skill

Download the ZIP file for this skill from the page, then choose one of the two install routes below. The skill's own file is named SKILL.md.

For a personal skill available in all your projects, unzip the download into ~/.claude/skills/. For a skill limited to one project, unzip it into the .claude/skills/ folder inside that project.

If you use the Claude apps instead, you can upload the ZIP under Settings → Capabilities → Skills.

• Requires Claude Code with the oh-my-claudecode plugin installed.
• Needs read and write access to ~/.claude/skills and the project .omc/skills folder.

Trigger the skill with natural requests

You can use the slash commands directly. Type the command, followed by any arguments, and the agent will walk you through the rest. The command format is /skill <command> [args].

The source lists these commands: list, add [name], remove <name>, edit <name>, search <query>, info <name> and sync. Each one follows the same pattern of questions and confirmations described above.

• /skill list
• /skill add custom-logger
• /skill edit custom-logger
• /skill search api endpoint
• /skill remove old-logger

Where your skills are stored

User skills are saved in ${CLAUDE_CONFIG_DIR:-~/.claude}/skills/omc-learned/<name>/SKILL.md. Project skills are saved in .omc/skills/<name>/SKILL.md inside your repository. Each skill is a folder with a SKILL.md file, and removing a skill deletes that whole folder.

Built-in skills are bundled with oh-my-claudecode in the plugin skills/ directory. The tool can list and read them, but it will not remove or edit them.

• Keep team-shared skills in .omc/skills so they live with the project.
• Keep personal skills in your user folder so they follow you across projects.

Example: create, edit and remove a skill

A typical session starts with /skill add. The source example creates a skill called custom-logger with the description 'Enhanced logging with structured output', triggers log, logger and logging, and scope user. The skill is saved to ~/.claude/skills/omc-learned/custom-logger/SKILL.md, and the agent suggests running /skill edit custom-logger to refine it.

To change the triggers later, run /skill edit custom-logger and choose triggers. To remove an old skill, run /skill remove old-logger. The agent shows the skill's name, description and scope, then asks 'Delete old-logger skill? (yes/no)'. Only a yes deletes the folder.