Submit a skill

The pipeline is open. Attach your packaged skill (or a repo URL), and it goes through automated validation plus a human review — usually live within 1–2 days. Basic listings are free, forever.

statusSubmissions are open. The checklist below is the review bar. Validate locally first with the skill-creator-playbook — it runs the same checks the server does.

The publisher checklist

  • [ ]Name follows the rules — lowercase, hyphenated, descriptive of the job (naming rules).
  • [ ]Version starts honestly — 0.x for experimental, 1.0.0 for stable. No 9.9.9 games.
  • [ ]README has all five sections — overview, installation, configuration, inputs table, worked example (requirements).
  • [ ]CHANGELOG.md exists — every version listed, newest first, breaking changes flagged.
  • [ ]License chosen and pinned — MIT or Apache-2.0 to start; the license travels in the manifest.
  • [ ]Inputs are typed and declared — no undocumented parameters, no silent defaults.
  • [ ]Safety review passed — destructive capabilities are marked and gated by confirmation.

Submit your package

One zip (max 25 MB) containing a single <name>/ directory with SKILL.md — or a public repo URL. Either way, the server validates before a human ever sees it.

Lowercase, hyphenated, must match your SKILL.md frontmatter and directory name.

Only used for review status. Never shared, never marketed to.

A zip containing one top-level <name>/ directory with SKILL.md, CHANGELOG.md, and a license.

Optional if you attached a zip. One of the two is required.

What happens next

Automated validation

Frontmatter, name rules, the five README sections, changelog, and license — checked instantly. Failures come back as a specific list.

Human review

Safety, honesty of claims, and version sanity. Destructive capabilities must be marked and gated. Usually 1–2 days.

Published

Detail page, download zip, changelog, and semver pin go live. Free basic listing — featured placement is optional.