Intempt Collective Marketplace
Submission guide
Submit your go-to-market recipe so any team's Blu can run your play in their own workspace. This is everything you need to send us one.
Version 1 · 3 October 2026 · First response in two business days
Three ways in. Pick by what you already have
A finished recipe.md
Give it to your coding agent with the two prompts below to validate and submit it. You do not need to start over.
Something you built in Intempt
A segment or attribute that already works in your workspace. The recipe creator reads its setup, never its rows, and interviews you for the judgement behind it.
Just an idea
No file, nothing built, just a play you know works. A guided route that starts from a conversation and drafts the recipe with you.
Paste these into Claude Code, Codex, Cursor or whatever agent you already use, one at a time:
Set up the Intempt recipe creator by following the steps in https://github.com/intempt/recipe-creator Create an Intempt recipe
The first installs the intempt-recipe-creator skill. The second starts it. Keep the link out of the second prompt: a link tells the agent to go and read files, and it then improvises instead of following the installed skill. Your agent interviews you, drafts the recipe.md, validates it against the engine's rules and hands you something ready to send.
What you get, and what you don't have to do
You keep the thinking. We handle the machinery. Rough drafts are welcome.
You bring
- The insight that shapes the recipe
- The title and summary, in your own voice
- Your name, work email, company, byline, LinkedIn and an avatar URL for your creator profile
We do
- Writing each step so the engine can run it, one thing per step with every value stated
- Marking it Install now or Coming soon, honestly
- Group, persona and tags, the boring stuff
- Formatting, safety and QA checks on the file
If you know the play but not which Intempt object does the job, describe what has to happen and we will map it to a segment, an attribute, an email or whatever the engine builds. We do not change what it decides. Your thresholds, your definition of good and your voice come back the way you wrote them. If making it run would change any of those, we ask you first.
Two kinds of recipe, both wanted
Install now
Every step builds something the engine builds today: segments, attributes, events, designed and plain emails, SMS, push, Slack messages, images and brand assets. These run in the installer's workspace the day they publish.
Coming soon
At least one step needs a dashboard, report, journey, workflow, experiment or another object the engine does not build from a recipe yet. They publish marked Coming soon, naming what they wait on, and switch to Install now when the engine catches up.
What makes a strong recipe
Judgement applied to the installer's own data. Anyone can write "email inactive users". A strong recipe says which users, by which event and window, what the email says and why that timing works. A step that points at nothing real gets flagged as vague and sent back to whoever installs it, so name the event, the attribute and the value.
What we turn down
We will help with everything else in this guide. Not these five.
Unsafe recipes
A recipe must not copy data to another service or post anywhere the installer did not authorize. No hidden comments, no invisible characters, no step that says go and get the real instructions from a link. Everything a recipe does stays readable on the page.
Made-up results
Do not claim outcomes the recipe cannot show, and do not name events or attributes as if every workspace has them. If a step needs a specific event, declare it as a prerequisite.
Steps the engine cannot run
Vague steps ("engage the account"), two jobs in one step, and steps that describe a strategy instead of something to build come back for another pass.
Promoting a tool with no play underneath
Building on one tool is normal and naming it is fine. A thin recipe whose real point is to make installers buy another product is not.
Real customer data
No customer names, emails, ids or lists in the file. A recipe describes the play; the installer's workspace supplies the data.
Using API keys is fine
Integrations connect in the installer's own workspace, with their own credentials. A key never goes in the file, in a chat or in a step. If a recipe needs Shopify, HubSpot, Slack or any other connector, declare it under prerequisites so Blu asks the installer to connect it before anything runs. The submit form and the validator refuse a file that contains something that looks like a key or token.
How to submit
- 1Send it from your agent or the formFrom your agent, the recipe creator previews exactly what it will send and waits for your yes before anything leaves your machine. Or upload the recipe.md at intempt.com/recipes/submit. Both land in the same review queue.
- 2Keep the receiptYou get a submission ID on screen. Save it. It is how you and we refer to the same submission.
- 3A person reads itSomya Nayak, who runs the Intempt Collective, reviews submissions for safety, usefulness and whether they run, and replies within two business days during early access. Engine questions go to our engineering team.
From a terminal with the Intempt CLI, once your version has the recipe command (it is rolling out now; until then use your agent or the form):
intempt login intempt recipe validate recipe.md intempt recipe submit recipe.md
What happens after
A person reads your recipe closely. They check it against the rules above, judge whether the thinking holds, and decide. Then curation, which is the part worth being straight about. Some submissions merge into a similar recipe. Some come back for another pass. Some do not publish. Where two recipes overlap we merge them or keep the stronger one, and a no comes with the reason.
Published recipes appear in the Intempt Collective Marketplace with your name on them. Creators on the Build track earn when other teams run their published recipes.
Rights, attribution and withdrawal
Your copyright
You keep it. Submitting grants Intempt a licence to review, edit and, if it meets the bar, publish your recipe with attribution.
Your byline
Published recipes carry your name and live at a permanent path built from it: recipes/<your-name>/<recipe>/ in the public intempt/recipe-creator repository and on intempt.com.
Licence
Published recipes are distributed under the repository's licence with attribution preserved. Copyright in each recipe stays with its author.
Withdrawal
There is no self-service button yet, so it goes through a person. Email hey@intempt.com with "Recipe withdrawal, for Somya" and your submission ID.
Early access, so expect details to move. If a rule here changes, we will tell you.