How to publish on PepeHub

1. Sign in

The Pepe CLI authenticates through GitHub Device Flow, the same model as gh auth login:

1. Running pepe skill publish (or pepe plugin publish) calls POST /api/v1/auth/device/start, which returns an 8-character code and a link.
2. Open the link, paste the code, and approve with your GitHub account.
3. The CLI receives a PepeHub session token as soon as you approve, and uses it for every publish after that.

2. Accepted format

The uploaded artifact is a tarball (.tgz) for plugins or a zip (.zip) for skills, together with a JSON manifest with at least kind, version (semver) and category (one of PepeHub’s fixed categories).

The full manifest format, the package’s internal structure, and how to declare commands, hooks, etc. are documented on the Pepe site, not here, to avoid duplicating content: skills andplugins.

3. Publish

pepe skill publish

The package namespace (@your-handle/name) must start with your GitHub handle: the first publish of a name creates the package automatically.

4. Prefer not to use the CLI?

It is also possible to publish directly from the browser, uploading the file (.zip or .tgz) in a form: publish from the browser.