Commands

All commands run inside a Claude Code session. Pound also has a CLI for managing your skills.

#

Fetch and activate a skill for the current session. Claude immediately starts following its instructions.

#code-reviewer

Or if you need you need a specific skill you can get it by username:

#frank/code-reviewer

#search

Search the registry by describing the skill you are looking for. Returns the most relevant public skills plus your own.

#search write integration tests using nock
#search git workflow

You can activate multiple skills in one session — just run #<skill-name> again with a different skill.

#create

Start a guided skill creation flow. Instead of writing a skill file by hand, #create walks you through the whole process — what the skill should do, how it should behave, and what to call it.

#create

The flow works like this:

1. Pound asks what you want the skill to do
2. You can provide context through files/folders and prompts
3. It helps you write, refine and iterate on the instructions
4. Once you're happy with it, you choose if the skill should be public or private
5. It uploads it to Pound automatically

#all

List your skills. Optionally filter by visibility.

#all
#all public
#all private

#upload

Upload a skill file directly from your Claude Code session.

#upload ./my-skill.md

Pound will then ask you two things:

• Public or private? Public skills are discoverable by anyone via #search. Private skills are only accessible to you.
• Skill name (slug)? Defaults to the filename — my-skill.md becomes my-skill. You can override this with --slug <name>. The slug is what others use to activate your skill: #code-reviewer.

Next steps

• Skills