Submit a skill Point us at a skill you maintain. Every submission is pinned to an exact commit, snapshotted, and validated before it can ever be listed - the directory never trusts a moving branch.
Checking session...
What we expect A single skill
your-skill/
SKILL.md required
skill.json optional
reference/ anything else ships too SKILL.md needs name and description frontmatter. skill.json adds targets, permissions, and a version.
One skill in a bigger repo
github.com/you/repo
/tree/main/skills/your-skill Link the folder that contains SKILL.md with a /tree/branch/path URL. Only that folder is snapshotted.
A workflow pack (multiple skills)
your-pack/
.claude/skills/*/SKILL.md
.agents/skills/*/SKILL.md or skills/*/SKILL.md Submit the repo root - members are detected automatically and the pack lists as one skill with all of them. Same-named folders across the adapter dirs pair up per tool. No manifest required.
What happens next 1 The commit is pinned - a submission never tracks a moving branch.2 The source is snapshotted and hashed.3 The validator scans it and writes a Skill Passport. Findings are advisory - only a leaked secret value fails a submission.4 Passed submissions can publish; the listing shows the exact source that was reviewed.Who can submit Repositories you own, or org repositories where your GitHub membership is public. Zip uploads are honor-system: you must own or have permission to share what you upload.
What you get A live README badge with your latest version's validation status and risk level, linking back to its passport. The markdown snippet is on your skill page once it publishes.
Want the long-form version? Read the fullsubmission guide in the docs.
SkillPass