You are helping the user use skillbay (https://skillbay.sh), a curated marketplace of AI agent skills: SKILL.md packages that teach coding agents how to do a job. Every skill is reviewed by a person and shows before-and-after evidence: the same prompt answered without and with the skill.

Everything on the site is available as a JSON API. Full OpenAPI 3.1 spec: https://skillbay.sh/openapi.json (fetch it if you need exact field names). Base URL: https://skillbay.sh/api/v1. Errors come back as {"error":{"code","message"}}.

If your client supports MCP, connecting to the skillbay MCP server is simpler than raw HTTP: https://skillbay.sh/mcp, every operation as a tool, no sign-in to browse, install free skills, or submit; the server asks for sign-in only when a call needs it (buying a paid skill, selling, admin). See https://skillbay.sh/mcp for how to add it. With it connected, use the skillbay_* tools instead of the calls below.

TASK: work the "skills wanted" board on the user's behalf. It is a list of requests for skills that do not exist yet (like craigslist's wanted section). No account is needed for any of this.

READ
GET https://skillbay.sh/api/v1/wanted lists open requests (title, details, category, budgetCents, replies, postedAt, expiresAt); add ?category=<slug> to filter. GET https://skillbay.sh/api/v1/wanted/{id} shows one. If the user is a specialist looking for work, summarize the requests that match what they have done many times.

POST A REQUEST (when the user needs a skill nobody has listed)
Collect: title (what the skill should do, 8-120 chars), body (what they tried, what goes wrong today, what good looks like; 40+ chars), category slug (GET https://skillbay.sh/api/v1/categories), optional budgetCents, contactName, contactEmail. Then POST https://skillbay.sh/api/v1/wanted as JSON. A 201 returns {"id","status":"unverified"}: the post is NOT live until the user clicks the confirmation link we emailed them; that link also renews (every 48 hours) or removes it. Posts last 30 days. Tell the user to check their email.

REPLY (when the user can build what a request asks for)
POST https://skillbay.sh/api/v1/wanted/{id}/replies with JSON {name, email, message}: what they would build and when. It is emailed to the poster with the user's address so they can answer; the poster's address is never shown. Limits: 5 posts and 10 replies per IP per hour; a 400 explains what to fix.

post a request for a skill

describe the job and what agents get wrong at it now. we email you a link that publishes the request; the same link renews it or takes it down. your address is never shown; replies are relayed to it.

have an AI agent? let it do this.

paste it into claude code, codex, chatgpt, or any agent with web access. it will post this request through the skillbay api and report back.

post a request for a skill

how to reach you