Browse Discover
Open skills, MCP servers, workflows, agents, packs, or creator storefronts.
Getting started
OlyWork is the discovery and secure delivery layer. GitHub can be a creator source, but premium buyers install through token-validated Oly CLI delivery.
Open skills, MCP servers, workflows, agents, packs, or creator storefronts.
Choose secure install on a listing. Free and beta access can be granted while monetization is dormant.
Run `npm install -g @olywork/cli` once, then copy the generated `oly install ...` command from Library.
Run the command inside the project where the capability should be installed.
Create a skill, MCP server, agent, or workflow with public metadata and trust details.
Paste distributable content or import a private GitHub repo path server-side.
OlyWork stores a protected package artifact and updates the package manifest.
Publish versioned updates from Package Registry without changing the buyer install flow.
Use the publish form when the package payload is ready to paste directly into OlyWork. This is fastest for small skills, rules, workflow JSON, and MCP configs.
Open publish flowUse GitHub App ingestion when creators maintain packages in private repositories. OlyWork fetches selected paths server-side and never exposes private clone URLs to buyers.
Import from GitHubnpm install -g @olywork/cliInstall the OlyWork CLI from npm.
oly install <token>Friendly secure install command for buyers.
oly sync --token <token>Canonical sync command for scripts and advanced usage.
oly updateRefresh locally tracked packages after `oly auth`.
oly listShow local package install state.
oly auth <token>Store local defaults intentionally. Tokens are not saved by default.
oly doctorCheck local CLI health and configuration.
Open a listing and get access.
OlyWork creates or reuses a purchase entitlement.
An access token is generated for that buyer and product.
Library reveals the install command only to the entitled buyer.
Buyer APIs do not return private repo URLs, object storage paths, or creator infrastructure details.
Tokens can be rotated, revoked, suspended, expired, and audited per product.
The CLI contract stays stable while storage, manifests, and source ingestion evolve behind it.