publish-to-loadout

An agent skill for publishing to the loadout marketplace: what each field of the publish form means, and a preflight that asks your repository's remote whether an install would actually find your skill.

The repository root is the skill itself — SKILL.md is the skill, and reference.md is the detail it defers to: every install-failure message mapped to its cause, the stored manifest shape, the row-level security that stops an author approving their own listing, and what the installing user sees.

Installing it

Through the loadout marketplace, or by hand:

git clone https://github.com/sslinNn/publish-to-loadout ~/.claude/skills/publish-to-loadout
rm -rf ~/.claude/skills/publish-to-loadout/.git

Codex and other runtimes read ~/.agents/skills/ instead.

Why the preflight exists

A listing stores metadata, not files. Each install clones your ref fresh, anonymously, on someone else's machine — so a skill that is committed but unpushed, or in a private repo, or one directory up from where the listing points, is accepted by the form and approved by a reviewer and then fails for every single user, silently, while still looking fine to its author.

The preflight is three commands that answer that before you submit rather than after.

License

MIT — see LICENSE.