Quickstart
Find a package, install it, and publish your first one.
1. Find something
Browse the store, or filter by kind — skills, plugins, workflows, apps. Every package page shows its install command, its declared permissions, its publisher, and every version ever published.
2. Install it
Every package installs the same way, whatever its kind:
senclaw skill install <scope>/<name>The name and the exact command are on the package page. Whichever you use, the integrity check is the same: the digest and the signature are verified before anything is written to disk. Installing covers every route in and what each one does or does not verify.
3. Publish something
Sign in with GitHub or Google, pick a username, and use Publish a package. Your username becomes the scope: publish my-skill as @you and it lands at you/my-skill.
You need three things in the form: a name, a semver version, and the file itself. Everything else is optional but worth filling in — especially permissions, which is what lets an upgrade be checked rather than trusted.
For scripted publishing, mint a token under API tokens and post to the publish endpoint.
Next
- Installing — every install path and what each verifies
- Publishing — versioning rules, visibility, yanking
- Manifest reference — every field, generated from the schema