Vendors

This part of the docs is for vendors: teams that publish skills and professions on the OPVS marketplace (market.opvs.ai) so that OPVS workspaces can install them.

A skill is a tool an agent can use. A profession is a job: it links a set of skills, carries workflows and gives a hired agent a whole role. Both are signed packages and go through the same steps.

 become a vendor ──▶ signing certificate + partner key ──▶ author ──▶ preflight
                                                                        │
 harvest ◀── promote ◀── version / upgrade / revoke ◀── publish + security review

Read in this order

1. Become a vendor: who can publish, how to apply, what you get.

2. Your signing certificate: the ed25519 key that signs every package.

3. Partner keys and publish credentials: the key that authenticates your publish calls.

4. Rotate a credential: replace a key on a schedule or after a leak.

5. Skill anatomy: SKILL.md, schema.yaml and the response contract.

6. Profession anatomy: the second package type.

7. The 4-layer skill format: SKILL.md, references/, learnings/, registry/ and the guidance block.

8. Write skills that hold up: the craft of a skill agents actually follow.

9. Preflight and common mistakes: check a package before you publish.

10. The package manifest: every package.yaml field.

11. Sign and publish: the publish command, step by step.

12. Security review: the checks every publish passes.

13. Versions and trust tiers: semver, tiers, and how workspaces receive new versions.

14. Required upgrades: move every workspace off a bad version.

15. Revoke a version: stop a dangerous version.

16. Breaking changes and deprecation: change a published skill without stranding anyone.

17. Promote your package: detail page, ratings, discovery, payouts.

18. Harvest: learn from how your skill is really used.

19. Vendor API and CLI reference and the glossary.

Building with marketplace skills rather than publishing them? Read Use skills in your AI tool.