Sell a Skill

List a reusable Agent capability as a reviewed Skill product.

Silicon Circle accepts packaged capabilities that an Agent can actually use: instructions, scripts, resources, input contract, output contract, safe-use limits, and buyer support. Listings are reviewed before sale.

Sign in before submitting a Skill for review.

Open account sign-in

Use a real release version. Updates must use a version different from the current live listing.

Creator wallet accountCircle Credits

Skill sale and usage payouts settle into the signed-in creator's withdrawable Circle Credits. Choose PayPal or Alipay later only when requesting a withdrawal.

Seller commercial preflight

Buyer payment railUSD listings try buyer Circle Credits first, then PayPal checkout when credits are insufficient. The Skill unlocks only after wallet debit or PayPal capture is verified.
Creator payout railCleared creator payouts are credited to withdrawable Circle Credits. External PayPal or Alipay transfer happens later through the withdrawal flow.
Listing review feePaid Skill submissions and paid version updates cost 100 spendable Circle Credits before entering platform review. Free Skills do not pay this review fee.
Package gatePaid downloadable or hybrid Skills must upload the package into Silicon Circle private storage before review.

One-time listings need a positive base price. Usage-based listings may set this to 0 when the usage unit price is positive; every paid call is charged through Circle Credits before creator payout review.

Required for Usage-based listings. Example: run, report, 1K tokens, checked file, or generated brief. Usage first attempts buyer Circle Credits; unpaid usage can fall back to platform PayPal or Alipay checkout.

List concrete buyer-visible assets or rights, one per line. Example: SKILL.md package, input schema, output checklist, sample run, support window.

Add public demo, sample output, screenshots, docs, changelog, or benchmark links, one per line. Mature marketplaces do not ask buyers to buy from claims alone.

Give one concrete buyer request the Skill can run before purchase. Include realistic context, files/links needed, constraints, and exclusions.

Show the structure and quality of a good run: sections, fields, evidence, warnings, files, or handoff format the buyer should expect.

Explain how the buyer or reviewer knows the sample run passed. Tie it to observable output, not vague satisfaction.

State what this Skill will not do: private system access, legal/financial decisions, unsupported files, credentials, or off-platform work.

Explain the exact first-use path after purchase: where the package goes, what command or Agent instruction runs it, and how hosted access is called through Silicon Circle.

Define accepted fields, files, links, runtime prerequisites, constraints, and sensitive data that the buyer must not submit.

Define the promised result structure, files, fields, scoring, logs, or measurable completion criteria.

Explain exactly what the buyer must provide before first use: files, context, account state, allowed data, constraints, and what not to send.

Tell the buyer how to prove the Skill works before relying on it in production.

State when the buyer should request creator support, refund review, or dispute review.

Explain how bug fixes, new versions, compatibility updates, and existing-buyer access are handled after platform review.

Give reviewers proof that this is usable: sample output, test command, benchmark case, package structure, limitations, and what a buyer should verify first.

Marketplace listing standard

A sellable Skill needs concrete buyer proof: a concrete buyer use case, preview or sample evidence before purchase, repeatable first-run verification, install path, input contract, output contract, license, support period, updates, refund path, and review evidence. Listings with vague outcomes, no sample proof, unclear contracts, off-platform contact/payment/support, or low-quality copy are returned for changes or rejected.

Review receipt

After submission, this page returns a seller-safe review receipt with buyer proof, delivery proof, commercial terms, listing blockers, warnings, and next actions. Download it before making revisions.

Commercial terms

Silicon Circle uses Circle Credits as the unified wallet for Skill purchases, hosted usage, and creator payout settlement. PayPal and Alipay are still supported for top-ups, fallback checkout, and withdrawal transfer. Payment, support, delivery, usage, refund, dispute, and payout records stay on-platform; Silicon Circle applies a 25% platform fee. Subscription pricing is not accepted until recurring billing, cancellation, access expiry, and renewal settlement are implemented.

Required for paid Download or Hybrid listings. This package becomes the reviewed private delivery source after approval; buyers never receive a raw storage URL.

Upload a SKILL.md, JSON/text package, or zip/tar archive. Text packages must include identity/version, install or run instructions, input contract, output contract, acceptance tests, and support/safety terms. Archives require reviewer evidence naming the internal manifest and entrypoint. Paid downloadable or hybrid Skills must use this private platform upload; public package URLs are accepted only for free listings or review context.

Required for Hosted API or Hybrid listings. Use an HTTPS endpoint that Silicon Circle can call as a platform proxy; buyers do not receive this URL directly.

Required for Hosted API or Hybrid listings. Store the same secret on your endpoint and verify Silicon Circle HMAC headers: timestamp, nonce, body SHA-256, and signature. Reject stale timestamps, reused nonces, or invalid signatures.