Skip to main content

​
What ClawRecipes is

ClawRecipes is the OpenClaw plugin for turning repeatable agent setups into reusable, installable recipes. Instead of rebuilding the same agent, team, workflow, folder structure, and operating rules over and over, ClawRecipes lets you package that work once and scaffold it again on demand.

​
Why it exists

Most people experimenting with agents hit the same wall fast:
  • one useful setup turns into five hand-maintained copies
  • team structures live only in chat or memory
  • workflows are hard to repeat consistently
  • the “right way” to run a project becomes tribal knowledge
ClawRecipes exists to fix that. It gives you a file-first way to capture how a team or agent system should be built, so you can recreate it cleanly, share it, improve it, and run it again without starting from zero.

​
What the project is trying to do

ClawRecipes is about making agent systems:
  • repeatable — scaffold the same structure reliably
  • shareable — package working setups as recipes
  • understandable — keep the system readable in files, not hidden in magic
  • operational — include workflows, roles, memory rules, and team conventions
That means a recipe can define more than a prompt. It can define how a whole team works.

​
What you can build with it

With ClawRecipes, you can scaffold things like:
  • a single specialized agent
  • a development team with lead/dev/test roles
  • a marketing team with repeatable workflows
  • a workflow-runner add-on
  • a bundled specialty pack for a specific use case or industry

​
How it relates to ClawKitchen

ClawRecipes is the system that defines and scaffolds the recipes. ClawKitchen is the UI layer that helps people browse, install, inspect, and operate those systems. A simple way to think about it:
  • ClawRecipes = the recipe and scaffolding engine
  • ClawKitchen = the control surface and product experience around it

​
In this section

This section covers the core parts of ClawRecipes:
  • installation and verification
  • commands and daily usage
  • recipe format and architecture
  • team workflow and file-first workflow runs
  • memory and shared-context conventions
  • bundled recipes and related integrations