ClawRecipes is an OpenClaw plugin that provides CLI-first recipes for scaffolding specialist agents and teams from Markdown.
If you like durable workflows: ClawRecipes is built around a file-first team workspace (inbox/backlog/in-progress/testing/done) that plays nicely with git.
When published on npm:
openclaw plugins install @jiggai/recipes
# If you use a plugin allowlist (plugins.allow), you must explicitly trust it:
openclaw config get plugins.allow --json
# then add "recipes" and set it back, e.g.
openclaw config set plugins.allow --json '["memory-core","telegram","recipes"]'
openclaw gateway restart
openclaw plugins listgit clone https://github.com/JIGGAI/ClawRecipes.git ~/clawrecipes
openclaw plugins install --link ~/clawrecipes
openclaw gateway restart
openclaw plugins listopenclaw recipes listopenclaw recipes scaffold-team development-team \
--team-id development-team-team \
--overwrite \
--apply-configopenclaw recipes dispatch \
--team-id development-team-team \
--request "Add a new recipe for a customer-support team" \
--owner leadClawRecipes is licensed under Apache-2.0.
Attribution requirement (practical): if you redistribute ClawRecipes (or a derivative work), you must retain the license and attribution notices (see LICENSE and NOTICE).
Branding note: the license does not grant permission to use JIGGAI trademarks except as required for reasonable and customary attribution. See TRADEMARK.md.
Contributions: we welcome PRs. By contributing, you agree that your contributions are licensed under the project’s Apache-2.0 license.
openclaw recipes list|show|statusopenclaw recipes scaffold(agent →workspace-<agentId>+ writes workspace recipe~/.openclaw/workspace/recipes/<agentId>.mdby default)openclaw recipes scaffold-team(team →workspace-<teamId>+roles/<role>/+ writes workspace recipe~/.openclaw/workspace/recipes/<teamId>.mdby default)openclaw recipes install-skill <idOrSlug> [--yes] [--global|--agent-id <id>|--team-id <id>](skills: global or scoped)openclaw recipes install <slug>(marketplace recipe)openclaw recipes bind|unbind|bindings(multi-agent routing)openclaw recipes dispatch ...(request → inbox + ticket + assignment)openclaw recipes tickets|move-ticket|assign|take|handoff|complete(file-first ticket workflow)openclaw recipes cleanup-workspaces(safe cleanup of temporary test/scaffold workspaces)
For full details, see docs/COMMANDS.md.
The plugin supports these config keys (with defaults):
workspaceRecipesDir(default:recipes)workspaceAgentsDir(default:agents)workspaceSkillsDir(default:skills)workspaceTeamsDir(default:teams)autoInstallMissingSkills(default:false)confirmAutoInstall(default:true)cronInstallation(default:prompt; values:off|prompt|on)
Config schema is defined in openclaw.plugin.json.
For users:
- Installation — install the plugin
- Agents & skills — mental model, tool policies
- Tutorial — create your first recipe
- Commands — full command reference
- Team workflow — file-first workflow
For contributors:
- Architecture — codebase structure
- Contributing — setup, tests, PR workflow
Run:
npm testnpm run test:coverage— coverage with CI thresholds (seevitest.config.ts)npm run smell-check— quality checks (ESLint, jscpd, pattern grep)
Husky runs on commit. Run npm ci first to install hooks.
A lightweight smoke check validates scaffold-team output contains the required testing workflow docs (ticket 0004).
Run:
npm run test:smoke(ornpm run scaffold:smoke)
Notes:
- Creates a temporary
workspace-smoke-<timestamp>-teamunder~/.openclaw/and then deletes it. - Exits non-zero on mismatch.
- Requires OpenClaw and workspace config.
- docs/ARCHITECTURE.md — codebase structure
- CONTRIBUTING.md — setup, commands, pre-commit, CI
Reference:
- Commands:
docs/COMMANDS.md - Recipe format:
docs/RECIPE_FORMAT.md - Bundled recipes:
docs/BUNDLED_RECIPES.md - Team workflow:
docs/TEAM_WORKFLOW.md - ClawRecipes Kitchen (UI):
docs/CLAWCIPES_KITCHEN.md
(Also see: GitHub repo https://github.com/JIGGAI/ClawRecipes)
- Workspaces:
- Standalone agents:
~/.openclaw/workspace-<agentId>/ - Teams:
~/.openclaw/workspace-<teamId>/withroles/<role>/...
- Standalone agents:
- Skills:
- Global (shared):
~/.openclaw/skills/<skill> - Scoped (agent/team):
~/.openclaw/workspace-*/skills/<skill>
- Global (shared):
- Team IDs end with
-team; agent IDs are namespaced:<teamId>-<role>. - Recipe template rendering is intentionally simple:
{{var}}replacement only.
ClawRecipes includes a safe uninstall command:
openclaw recipes remove-team --team-id <teamId> --plan --json
openclaw recipes remove-team --team-id <teamId> --yes
openclaw gateway restartNotes:
- The command is confirmation-gated by default (use
--yesto apply). - Cron cleanup is conservative: it removes only cron jobs that are explicitly stamped with
recipes.teamId=<teamId>. - If you need a manual fallback, you can still delete
~/.openclaw/workspace-<teamId>and remove<teamId>-*agents fromagents.list[]in~/.openclaw/openclaw.json.
- GitHub: https://github.com/JIGGAI/ClawRecipes
- Docs:
- Installation:
docs/INSTALLATION.md - Commands:
docs/COMMANDS.md - Recipe format:
docs/RECIPE_FORMAT.md - Team workflow:
docs/TEAM_WORKFLOW.md - Agents & Skills:
docs/AGENTS_AND_SKILLS.md - Architecture:
docs/ARCHITECTURE.md - Bundled:
docs/BUNDLED_RECIPES.md - Create Recipe Tutorial:
docs/TUTORIAL_CREATE_RECIPE.md - Contributing:
CONTRIBUTING.md
- Installation:
ClawRecipes is meant to be installed and then used to build agents + teams.
Most users should focus on:
- authoring recipes in their OpenClaw workspace (
<workspace>/recipes/*.md) - scaffolding teams (
openclaw recipes scaffold-team ...) - running the file-first workflow (dispatch → backlog → in-progress → testing → done)
- Release Clawmarket, https://github.com/JIGGAI/ClawMarket, public url https://clawkitchen.ai
- Release ClawKitchen, https://github.com/JIGGAI/ClawKitchen
- Merge at least 1 community pull request
- Daily shipping/pull requests of ClawRecipes features
- Improve recipes with more detailed agent files
- Add ability to install skills for agents through ClawKitchen
