Skip to content
Contribute

Fork. Add a pack.
Open a PR.

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.

skillforge — browse
$ skillforge browse --featured
liquid-glass-enforcerFeatured
rust-async-patternsv2.0
react-best-practicesPopular
graphql-federation-gateway
prompt-injection-defenderSecurity
302 skills loaded  ·  14 domains  ·  v2.0.0  ·  Apache-2.0

Five steps to a shipped pack

The workflow is simple because it has to be.

A solo-maintained project cannot afford a complex contribution pipeline. This one works.

1

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.

2

Validate locally

Run the repo checks before you push. They catch hygiene issues, stale commands, and missing metadata before review.

3

Open a PR

One pack per PR. Include a clear description of what the pack does, who it helps, and why it belongs in the catalog.

4

Review

The maintainer checks for clarity, portability, honest claims, and long-term maintainability. Most reviews close within days.

5

Ship

Once merged, your pack appears in the generated catalog, the docs site, and the CLI export surface. Immediately usable.

Resources

Everything you need to write a strong pack.

Maintainer

One person reviews. Decisions are fast.

Jami Ojala

@jamiojala · Maintainer

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.

302 packs shippedGitHub-native workflowApache-2.0 licensed
Solo maintainedOpen sourceFast reviews