
Publish Skill
- 3 installs
- 3 repo stars
- Updated January 30, 2026
- johnlindquist/skill-publish-skill
Publish Claude Code skills to the Skillselion registry for community discovery and automated installation.
About
Skill publishing tool that validates SKILL.md format, uploads to registry, and manages versioning for distribution.
- Registry validation and upload
- Automatic semantic version management
Publish Skill by the numbers
- 3 all-time installs (skills.sh)
- Ranked #596 of 782 Skill Development skills by installs in the Skillselion catalog
- Data as of Aug 2, 2026 (Skillselion catalog sync)
npx skills add https://github.com/johnlindquist/skill-publish-skill --skill publish-skillAdd your badge
Show developers this skill is listed on Skillselion. Paste this into your README.
| Installs | 3 |
|---|---|
| repo stars | ★ 3 |
| Last updated | January 30, 2026 |
| Repository | johnlindquist/skill-publish-skill ↗ |
What it does
Publish Claude Code skills to the Skillselion registry for community discovery and automated installation.
Files
Publish Skill
Publish skills to GitHub so they're discoverable via npx skills add <org>/<repo>.
How Skills Discovery Works
The npx skills CLI discovers skills from GitHub repositories with this structure:
<repo>/
└── skills/
└── <skill-name>/
└── SKILL.mdUsers install skills with: npx skills add <org>/<repo>
Publishing Workflow
1. Gather Information
Use AskUserQuestion to collect:
- Which skill to publish - Path to the local skill directory (must contain SKILL.md)
- GitHub org/user - The GitHub organization or username to publish under
- Repository name - Name for the skills repository (e.g., "agent-skills", "my-skills")
2. Validate the Skill
Before publishing, verify:
SKILL.mdexists and has valid YAML frontmatter withnameanddescription- SKILL.md is under 200 lines (recommended)
- Any
references/,scripts/, orassets/directories are included
3. Publish to GitHub
Use the GitHub CLI (gh) to publish:
# Check if repo exists
gh repo view <org>/<repo> 2>/dev/null
# If repo doesn't exist, create it
gh repo create <org>/<repo> --public --description "Agent skills collection"
# Clone the repo (or use existing clone)
gh repo clone <org>/<repo> /tmp/skills-publish-<repo>
# Create skills directory structure
mkdir -p /tmp/skills-publish-<repo>/skills/<skill-name>
# Copy skill files
cp -r <local-skill-path>/* /tmp/skills-publish-<repo>/skills/<skill-name>/
# Commit and push
cd /tmp/skills-publish-<repo>
git add .
git commit -m "Add <skill-name> skill"
git push origin main4. Verify Publication
After publishing, verify the skill is discoverable:
npx skills add <org>/<repo> --listExample Session
Agent: Which skill would you like to publish?
User: ~/.claude/skills/my-awesome-skill
Agent: What GitHub org or username should this be published under?
User: my-github-org
Agent: What repository name? (e.g., "agent-skills")
User: my-skills
Agent: Publishing my-awesome-skill to my-github-org/my-skills...
[Creates repo if needed, copies skill, commits, pushes]
Agent: Done! Install with: npx skills add my-github-org/my-skillsNotes
- Skills repos can contain multiple skills in the
skills/directory - The skill name in the directory should match the
namein SKILL.md frontmatter - Public repos are required for skills discovery
- Consider adding a README.md to the repo root describing your skills collection