Enters review firstNever auto-published
Submit a capability
We prioritize projects with clear setup instructions, a clear permission scope, source links, and enough evidence for a developer to evaluate them safely.
What happens after you submit
- 1. You submit the project.
- 2. We tidy it into a consistent capability card.
- 3. We check its details, risk, and setup step by step, where it's safe to do so.
- 4. A person reviews the risk labels before anything goes public.
Never auto-published
A submission only enters the review queue. Before it appears in the public catalog, we tidy its details, check the risks, and a person signs off.
What gets extra review
- Anything needing tokens, write access, shell, external network, or local files gets a closer human review.
- Projects with thin information stay in review and never enter the public catalog automatically.
- The clearer the source, setup, and permission notes, the faster the review.
Coming soon
Submissions are coming soon
The first public release focuses on presenting checked capabilities clearly; the community submission channel is being prepared. Once it opens, submissions enter a review queue and still go through tidy-up, checking, risk review, and a final human sign-off.
In the meantime, browse the catalog or compare capabilities: