Publish and update skills

Publishing means naming your repository: the marketplace fetches it, pins it to a commit, runs the automated checks, and hands the result to a human reviewer. You never upload files.

Submit a source

In the dashboard, open Publish.
Paste the repository URL, e.g. https://github.com/acme/acme-skills.
Optionally name a ref - a commit, tag, or branch. Left empty, the default branch’s latest commit is used.
Optionally select which skill directories to submit; by default every directory with a SKILL.md is included.

The server fetches the repository snapshot itself, so the stored files, stars, licence, and commit are marketplace-verified. The automated checks run immediately on every discovered skill; the source is then submitted as a whole - one submission in the review queue, however many skills it carries - with each skill’s check report attached as evidence for the reviewer, who approves or declines the submission as a whole.

One submission carries up to 200 skills. A larger repository answers with its directory list instead, so you pick which skills to inspect and submit.

GitHub rate-limits anonymous API calls (60 per hour per IP; a submission costs 3). If your marketplace host sets the optional GITHUB_TOKEN, the limit is much higher.

Track the submission

Skill Sources lists every repository you publish from; open a source to see its skills, every submitted version with its status and the reviewer’s notes, and each version’s audit check report. If the reviewer requests changes, fix the repository and resubmit; the review trail keeps the history.

Update or archive a source

Updates and archiving act on the source, not on individual skills. Resubmit the repository at a new commit or tag and every skill it carries gets a new version through a fresh review; your published versions stay live and installable the whole time, superseded only on approval. Archiving is one action on the source record itself: the source and every published skill it carries leave the catalog together, and any submission of the source still waiting in the review queue is withdrawn. The review history stays public. Resubmitting an archived source relists it - approval brings every skill back.

What happens on approval

The skill appears in the public catalog under your organisation - and if this is your first published skill, your organisation becomes publicly visible at the same moment. See The review process for what reviewers do.