Publish your first skill on Sealed: a walkthrough
From skill body to live listing, step by step. There's no listing fee and no minimum: you write the listing, the body seals on upload, and from then on buyers get results while the file stays on our infrastructure. Here is exactly what the publisher console asks for, and what happens after you press publish.
What you need
Two things:
- iThe skill body. Your method — the prompts, rules, and examples an agent follows to do the job well. Keep your own copy: once uploaded, no API returns this text to anyone, including you.
- iiAn email address. Sign-in is a magic link — there is no password to invent or lose.
If you're still deciding what to write, start with what you can — and can't — protect; it will save you from publishing something a buyer could imitate from its own outputs.
Step 1 — sign in with a magic link
Go to the sign-in page and enter your email. We send a link; clicking it signs your browser in. No password, nothing to store. Once you're in, the Publish link appears in the marketplace navigation.
Step 2 — the publish form, field by field
The publisher console is one form, five sections. Alongside it, a live preview shows your
listing exactly as GET /skills will return it — note the body is structurally
absent from that response, which is the product working.
- iListing. A skill name (up to 80 characters) and a buyer-facing description (up to 200): what it does, for whom, in one sentence. This is what buyers and their agents see in the catalog.
- iiInputs. A table of fields, each with a name and a buyer-facing description. This table renders the buyer's run form 1:1 — what you name here is what their agent sends. Start a description with "Optional:" to mark that field optional.
- iiiThe sealed body. Your method, prompts, and rules go in here. It is sealed on upload — encrypted at rest, decrypted only to execute — and never shown to buyers. No API returns this text afterwards, not to buyers and not to you, so keep your own copy.
- ivPricing. Pick the model tier your skill runs on; it sets the price floor so every call clears its compute: haiku $0.10, sonnet $0.14, opus $0.19 per call. Price at the floor or above it, never below. The ledger updates as you type: at $0.14 the buyer pays $0.14 and you keep $0.112 — the ledger splits on an integer micro-dollar grid, so 80% is exact at every price.
- vSeller attestation. Six statements you certify before publishing: the skill is lawful and allowed to be sold; it operates only in authorized scope; it is not designed to harm a computer or service; not designed to steal or misuse protected data; not designed to support prohibited goods or regulated abuse; and you own or have the rights to publish it. Read the Prohibited Skill Policy before certifying.
Then one button: Publish — body seals on upload.
Step 3 — screening, then a page of its own
New listings are safety-screened before they list. While the check is pending, your
listing stays out of the public catalog and shows its approval status to you. Once
approved, the skill appears in the marketplace,
in the machine catalog at /skills.json, and on
its own public page at /skills/{id}/page — metadata only: name,
description, inputs, price. Never the body.
Buyers reach it over plain HTTP or through their agent — here is what the buyer side looks like.
Step 4 — earnings
On each successfully settled call, 80% accrues to your Sealed balance. Eligible cash-outs run through a Stripe-hosted Connect account you own; Stripe does the identity checks and moves funds to your bank. The 20% platform fee is published and uniform, and the split is exact at every price — never rounded against you.
The full terms of the deal — what we promise, what we can't, and in what order — are on the seller page.
Hosted or Connected?
This walkthrough publishes Hosted skills: the buyer sends inputs, your skill runs on our infrastructure, and the buyer gets the output back. That is the self-serve path, live today.
Connected skills work on files inside a buyer's project, under a scope the buyer approves — and the skill body still never reaches their machine. A Connected listing needs a seller-authored scope contract and is hand-reviewed before it lists. To propose one, write to support@sealed.run.
What should you publish?
Sell doing, not dispensing. A skill whose value is a method — how it transforms, structures, or judges the buyer's inputs — holds up, because the method stays server-side. A skill whose whole value is a fixed block of text it hands back does not, because there the output is the IP. The doing-versus-dispensing guide walks through which is which.
Building in the open · @sealedrun