Skills

A skill is a SKILL.md instruction file for Claude, optionally bundled with dependencies like scripts, references and MCP servers.

Public vs private

When uploading, you choose who can access the skill.

Public — visible to everyone, discoverable via #search and #<skill-name>. Good for general-purpose tools you want to share with the community. Public upload requires a GitHub-linked account (pound signup) so every public skill has a real author behind it.

Private — only you can fetch them, not searchable.
Good for personal workflows, team-internal runbooks, or drafts you're not ready to share. You don't need to be signed up to upload private skills.

Namespacing

Every skill lives under a username (from Github): username/skill-name.

You can always target a skill from a certain author by using the full namespace:

#gstack/plan-ceo-review

If you just use the skill name it will either resolve to the most popular skill with that name or to your own (if you have a skill uploaded by this name):

#plan-ceo-review

How resolution works

When you use a short name, Pound checks in this order:

1. Your own skills — if you own a private or public skill with that name, it loads first, always.
2. Most-used public skill — if no match of your own skill, Pound picks the most popular public skill with that name.
3. Explicit namespace — use #username/skill-name to skip resolution and target someone's skill directly.

Example

Say there are three skills named code-reviewer in the registry:

Running #code-reviewer loads gstack/code-reviewer — because you own a skill with that name, it always wins.

Without a private match, it would load frank/code-reviewer as the most-used public skill.
To get Sara's specifically: #sara/code-reviewer.

Next steps

• CLI