Fork and create
Add a folder under skills/ with four files: README.md, SKILL.md, skill.yaml, and marketplace.yaml. That is the entire pack.
The entire contribution workflow runs on GitHub. No CLI tools to install, no accounts to create, no approval queues. Your work ships when it merges.
Five steps to a shipped pack
A solo-maintained project cannot afford a complex contribution pipeline. This one works.
Add a folder under skills/ with four files: README.md, SKILL.md, skill.yaml, and marketplace.yaml. That is the entire pack.
Run the repo checks before you push. They catch hygiene issues, stale commands, and missing metadata before review.
One pack per PR. Include a clear description of what the pack does, who it helps, and why it belongs in the catalog.
The maintainer checks for clarity, portability, honest claims, and long-term maintainability. Most reviews close within days.
Once merged, your pack appears in the generated catalog, the docs site, and the CLI export surface. Immediately usable.
Resources
Format
Understand the portable manifest format, writing standards, and expected structure.
Open resourceValidation
Check your pack locally before you open a pull request.
Open resourceExamples
Study featured packs and domain-leading examples before you submit.
Open resourceReview
See what happens after submission, from triage to merge and release.
Open resourceMaintainer
SkillForge is solo-maintained by design. The contribution path stays simple because the maintenance path has to stay sustainable. Every process choice reflects that reality.