2. Samples and requirements Buyer receives List concrete buyer-visible assets or rights, one per line. Example: SKILL.md package, input schema, output checklist, sample run, support window.
Buyer previews / sample outputs 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.
Sample buyer input Give one concrete buyer request the Skill can run before purchase. Include realistic context, files/links needed, constraints, and exclusions.
Expected sample output Show the structure and quality of a good run: sections, fields, evidence, warnings, files, or handoff format the buyer should expect.
Sample acceptance proof Sample limits
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.
Install / run instructions 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.
Input contract Output contract
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.
Buyer requirements Explain exactly what the buyer must provide before first use: files, context, account state, allowed data, constraints, and what not to send.
First-run verification Tell the buyer how to prove the Skill works before relying on it in production.