Publishing skills is open to every plan, with no listing cap. Open My Skills in the sidebar and hit Post a skill.
What goes in the package
A skill is a folder of plain text files. The root must hold a file named exactly SKILL.md, matched case-sensitively, and that is the entry point an agent reads first. Everything beside it is yours: reference notes, templates, examples.
Step 1: get the files in
The wizard offers three sources, all checked identically:
- Upload files. Pick files, pick a folder, or drag them in. Problems are named before a single byte uploads.
- Upload a .zip. Unpacked on the server. One wrapping top-level folder is unwrapped for you.
- Import from GitHub. A public repo URL, plus an optional branch, tag or commit and an optional subfolder.
Step 2: review the files
Your staged package is listed back with its tree, file count and size, and anything the server excluded is named here. A rejected package returns you here with every listing field you typed still intact.
Step 3: the listing
Title and description are prefilled from your SKILL.md when we can read it, and both are required. Then set the category, recommended model, tags, a licence, and up to 5 cover images.
- Slug. Editable until the skill first publishes, then fixed, because it is half of the install command.
- Free or Premium. Premium contents and installs need an Explorer plan or higher. That gates access, it cannot prevent copying: an installed copy sits in plain text on someone's machine.
Save a draft, or publish.
Review, then installs
Every skill is read by a human before it goes live, free ones included, on first publish and on every later file change. A published skill stays live while its update is reviewed. If changes are requested you get a notification with the reason, and you fix it in place.
Once live, the row action Copy install command gives you the permanent one-liner:
npx promptdock@latest install your-handle/your-skillInstalls and views then show up in Monetization as that skill's contribution to the creator pool.