Choose type
Select skill, MCP server, workflow, or deployable agent.
Docs1 2 3 4
Creators
Publish installable AI capabilities.
Creator Studio turns public Discover metadata plus protected package payloads into a secure buyer install experience.
Publishing flow
Add metadata
Write the public title, summary, docs, tags, compatibility, and setup notes.
Attach payload
Paste package content or ingest a private GitHub repo path server-side.
Publish version
OlyWork creates an encrypted artifact, manifest, version record, and install target.
Publishing paths
Manual publish
Use `/creator/packages/new` for a single secure package flow. It creates the listing, manifest, first version, encrypted artifact, and install target together.
GitHub import
Best when creators maintain packages in a private repository and want OlyWork to ingest selected paths securely.
Beta access while payments are dormant
Grant buyer access
From `/creator/packages`, enter a signed-in buyer email to create a token-backed library entitlement without Stripe Checkout.
Same secure install path
Beta access still uses `oly install <token>`, token rotation, revocation, sync logging, and encrypted package delivery.
Package readiness
Ready to install
Product is active, manifest exists, encrypted artifact exists, and the listing is published.
Needs review
The artifact can exist before the listing is public. Review state controls Discover visibility.
Trust signals
Verification, security review, ratings, installs, and public links help buyers evaluate creators.
Verification model
Source verified
Automatic when a package is ingested through an authorized GitHub App installation. OlyWork can confirm the creator controlled the source path without exposing private repository URLs.
Creator verified
Used for creators or companies with verified GitHub ownership, company-domain identity, or manual platform review. This is separate from source verification.
Secure delivery
Used when buyers receive Oly CLI access to encrypted artifacts instead of raw clone links or object storage paths.
Creator checklist
Use public metadata for discovery and private payloads for premium delivery.
Never place private repository URLs in buyer-facing documentation.
Add compatibility badges so buyers know where the package installs.
Publish changelogs for every version update.
Use packs to group related capabilities into installable stacks.