For creators
Turn a buyer request into a reviewed skill
Use the request board to find a concrete problem, define scope, and share an approved response.
Quick answer
Look for an open request whose inputs and desired output match your expertise. Treat any budget as an unfunded offer, not a guaranteed payment. Build and test a clearly scoped workflow, complete normal review and onboarding, then share your own published, safety-cleared skill on the request. The requester receives an alert inside Skillset.
Translate a broad request into a testable deliverable
A fictional request asks for “a weekly returns report” with a $50 offered budget. That is a starting point, not a finished specification. Identify the input columns, the reporting period, how return reasons are grouped, and whether the output should be a summary, a table, or proposed actions.
Separate a reusable skill from custom operational work. A workflow that analyzes a supplied export does not automatically connect to a store, run each Friday, or change inventory. If the requester needs those additional services, agree on scope and payment before starting custom work rather than assuming the board funds it.
Use tags and alerts to find a relevant fit
Browse the request board by search or tag. Signed-in creators can follow up to eight tags; new matching requests appear in Your alerts. These are in-app alerts, so do not assume an email or a push notification will arrive.
Choose the request because you understand the job, not only because a budget is displayed. The amount is explicitly not funded, and posting a response does not collect it. Avoid asking requesters to put private customer exports, passwords, or API keys into a public description. Use a fictional sample to establish the required structure.
Build the smallest complete workflow
For the returns example, ask for the date range and relevant columns, check missing reason values, summarize the strongest patterns, and distinguish observed causes from guesses. Have the output list uncertainty before proposing actions. A manual export can be a useful first scope if direct store access is unavailable.
Test an ordinary dataset, a missing-column dataset, and a case where the sample is too small to support a confident conclusion. Paste the instructions into the creator editor, describe the dependencies and pricing, and submit for scanning and review. A request response does not bypass publication requirements.
Share the approved listing and leave the choice to the buyer
Once the skill is live and safety-cleared, open the request and use the creator response form with your Skillset link or slug. The form accepts only your own eligible published skill and an open request. The requester gets an alert and can review the listing before choosing whether to acquire it.
The request owner can close the request. Closure is a board status; it is not proof that a payment occurred, a workflow ran, or the requester approved a result. Keep any subsequent claims tied to evidence, and use feedback about missing inputs or confusing steps to prepare a reviewed update.
Common questions
Is the offered budget held in escrow?
No. It is an unfunded offer. Agree on the commercial scope before custom work, and do not describe the displayed amount as money already reserved for you.
Can I respond with an unfinished draft?
The response form requires your own published, safety-cleared skill. Prepare and review the draft first; a request does not grant an exception.
Does sharing a skill automatically buy it for the requester?
No. Sharing creates a response and an in-app alert. The requester still reviews the offer and decides whether to acquire access.
Put a workflow to work.
Connect your library to your AI, or turn your method into a skill.