Recipes

A recipe is a versioned GTM playbook: one motion written out with its prerequisites, credit posture, approval gates, and steps. Categories, each phrased as the question it answers: start-here, pipeline-from-zero, catch-warm-signals, linkedin-engine, convert-faster, revenue-truth, agency-scale.

Recipes are advisory. Reading or installing one costs 0 credits and changes nothing outside the wiki. The paid steps inside a play run through their own primitives, with their own --approved and --max-credits gates.

Start with this one

oxygen recipes show linkedin-network-first-motion --json

If you have no play running yet, run that one. linkedin-network-first-motion captures the people already in your LinkedIn network, plus everyone who connects, follows, views your profile, or engages from here on, into deduped workspace tables — then enrols them into a capped warm sequence once you approve a standing grant. No list, no domain, no cold-email setup; authoring and scoring run on the free tier, and connecting the LinkedIn sender that sends needs a paid plan.

Be aware of two things before you approve the grant. The connections import is a drip: it reads LinkedIn on a metered daily budget, so a real network lands over days, not in one run (oxygen linkedin ingestion status --json shows progress). And reaching the network you already have is opt-in — by default the first cycle baselines everyone already captured and only contacts people who arrive from now on, until you pass --include-existing-network to oxygen linkedin intent autoenroll.

Find the others

oxygen recipes list --stage day-1 --json
oxygen recipes list "outbound" --category pipeline-from-zero --json
oxygen recipes list --audience agency-operator --json

--stage takes day-1, day-7, day-30, or ongoing. --audience takes founder, gtm-operator, or agency-operator. An unknown value is rejected with the allowed list.

In the browser, the catalog is at oxygen-agent.com/recipes — Recipes in the sidebar, under Knowledge — grouped by category with the business-case question above each group. Cards show the journey stage, a trial-safe badge, setup minutes, and the pilot credit cost.

Read one

oxygen recipes show outbound-pilot-50 --json

You get the full body plus the frontmatter facts: outcome, leading metric, a labelled benchmark range, effort, pilot and full credit cost, prerequisites with the check command for each, and the approval gates. /recipes/<slug> shows the same facts as Outcome, Leading metric, Benchmark, Effort, Credits, and Before you start.

Every paid or external step in the body is marked > APPROVAL GATE — <slug> and names what you must see before approving. A recipe marked trial-safe keeps its pilot path at or under 100 credits.

Install one

oxygen recipes install outbound-pilot-50 --draft --json

This writes the play into your workspace wiki as a page at playbook-<recipe-slug> — revisioned, searchable, and readable by your agent. Automatic retrieval of wiki pages into AI columns and drafts is built but switched off in production, so an installed playbook is something your agent opens on purpose, not something injected into every AI call. --draft installs it inactive. Edit it freely afterwards; a re-install refuses to clobber your edits unless you pass --force, and --slug <wiki_slug> installs under a different name instead. Read the result with oxygen knowledge page get playbook-outbound-pilot-50 --json or open the returned link at /knowledge/pages/<slug>.

Three different things are called "recipe"

Blueprints, the optional scaffold

Some recipes name a blueprint that builds the infrastructure the play needs. outbound-pilot-50 names dm-outbound-pilot; the recipe still works without it.

oxygen blueprints list --json
oxygen blueprints describe dm-outbound-pilot --json
oxygen blueprints preflight dm-outbound-pilot --json   # 0 credits, no workspace change
oxygen blueprints apply dm-outbound-pilot --json       # 0 credits, creates workspace objects

Preflight first: it validates inputs against your workspace, reports the per-run credit ceilings you would face later, and returns the exact apply command that preserves the inputs you validated. apply spends no credits and makes no provider calls, but it does create tables, columns, prompt templates, and a workflow — left disabled, so nothing runs until you enable it.

To go the other direction, oxygen blueprints export --workflow <id> --out ./my-play.json bundles a workflow you built, oxygen blueprints save --file ./my-play.json stores it in this workspace, and oxygen blueprints share <slug> returns a public oxygen-agent.com/b/<code> URL anyone can apply.

Blueprints has its own sidebar item under Knowledge, labelled Blueprints and pointing at /blueprints — separate from Recipes, which points at the playbook catalog above. It is beta-gated: it stays hidden until an admin turns on Beta features in organization settings (/settings#/beta-features). The route itself works by URL either way. Recipes is not gated. /blueprints/<slug> lists What this blueprint creates, then Apply via CLI and Share with someone else as copy-paste commands — there is no create button, because blueprints are authored from the CLI.

From MCP

oxygen_recipes_* and oxygen_blueprints_* are not in the default tool list a fresh client sees. Reconnect with ?toolset=knowledge to load them, or call oxygen_capabilities_search to have the right pack named for you. Per-tool detail: MCP tool reference.