by JIGGAI
Save 120+ Hours of Setup Pain (I did it for you) – Launch Your OpenClaw Agent Teams with 1 Command (15+ Recipes)
# Add to your Claude Code skills
git clone https://github.com/JIGGAI/ClawRecipesClawRecipes is an OpenClaw plugin for scaffolding agents, teams, and file-first workflows from Markdown recipes.
If you want the short version:
ClawRecipes is CLI-first. It works without a UI.
ClawRecipes gives you:
openclaw recipes scaffold)openclaw recipes scaffold-team)dispatch → backlog → in-progress → testing → done)It is built for people who want durable artifacts on disk, not hidden app state.
OpenClaw plugin install (recommended)
openclaw plugins install @jiggai/recipes
openclaw plugins enable recipes
openclaw gateway restart
openclaw plugins list
If you see
plugins.allow is empty; discovered non-bundled plugins may auto-load, run to explicitly allowlist the plugin and suppress the warning.
No comments yet. Be the first to share your thoughts!
openclaw plugins enable recipesNote: The OpenClaw plugin installer enforces
pluginApiversion checks. If you see a version mismatch error, use the npm install method below instead.
During install you may see:
Plugin "recipes" has 2 suspicious code pattern(s). This is expected — ClawRecipes reads API keys from your OpenClaw config and passes them to media generation scripts (e.g., DALL-E, Kling). This is required for workflow execution and is not a security concern.
npm install
npm install @jiggai/recipes --prefix ~/.openclaw/plugins
openclaw gateway restart
openclaw plugins list
From a local checkout (development)
git clone https://github.com/JIGGAI/ClawRecipes.git ~/ClawRecipes
openclaw plugins install --link ~/ClawRecipes
openclaw gateway restart
openclaw plugins list
Then verify the commands exist:
openclaw recipes list
More install details: docs/INSTALLATION.md
openclaw recipes list
openclaw recipes show development-team
openclaw recipes status development-team
openclaw recipes scaffold-team development-team \
--team-id development-team \
--apply-config \
--overwrite
This creates:
~/.openclaw/workspace-development-team/roles/work/--apply-config is used)openclaw recipes dispatch \
--team-id development-team \
--owner lead \
--request "Add a new clinic-team recipe"
Then work the ticket flow:
openclaw recipes tickets --team-id development-team
openclaw recipes take --team-id development-team --ticket 0001 --owner dev
openclaw recipes handoff --team-id development-team --ticket 0001
openclaw recipes complete --team-id development-team --ticket 0001
ClawRecipes supports file-first workflows with:
shared-context/workflows/shared-context/workflow-runs/# Run one workflow manually
openclaw recipes workflows run \
--team-id development-team \
--workflow-file marketing.workflow.json
# Scheduler / runner
openclaw recipes workflows runner-once --team-id development-team
openclaw recipes workflows runner-tick --team-id development-team --concurrency 2
# Worker / executor
openclaw recipes workflows worker-tick \
--team-id development-team \
--agent-id development-team-lead
# approve
openclaw recipes workflows approve \
--team-id development-team \
--run-id <runId> \
--approved true
# reject with note
openclaw recipes workflows approve \
--team-id development-team \
--run-id <runId> \
--approved false \
--note "Tighten the X post hook"
# resume an awaiting run
openclaw recipes workflows resume \
--team-id development-team \
--run-id <runId>
Four ready-to-run workflow examples ship under
examples/workflows/:
marketing-cadence-v1 — text-only marketing cadencemarketing-image-generation-handoff — image generation + handoff to social publishmarketing-video-generation-handoff — video generation cadencesocial-media-publish — handoff target that publishes via kitchen-plugin-marketing + PostizEach example directory contains the workflow JSON, a cron-jobs.example.json,
an install-crons.sh helper, and a per-example README with prerequisites
and install steps. See docs/WORKFLOW_EXAMPLES_BUNDLED.md
for the catalog, required cron jobs, and a recommendation on
agents.defaults.maxConcurrent sizing.
See also:
This is the part most people trip over.
Published ClawRecipes builds are intentionally conservative:
marketing.post_all posting path is not something users should assume is active after installIf you want workflows that actually publish content:
Recommended path
outbound.postLocal-controller / patched path
In plain English:
If you are using RJ's local controller flow, document and keep your patch handy.
openclaw recipes list
openclaw recipes show development-team
openclaw recipes install clinic-team
# single agent
openclaw recipes scaffold project-manager --agent-id pm --apply-config
# team
openclaw recipes scaffold-team development-team --team-id development-team --apply-config
# add a role into an existing team
openclaw recipes add-role \
--team-id development-team \
--role workflow-runner \
--recipe workflow-runner-addon \
--apply-config
openclaw recipes tickets --team-id development-team
openclaw recipes move-ticket --team-id development-team --ticket 0007 --to in-progress
openclaw recipes assign --team-id development-team --ticket 0007 --owner dev
openclaw recipes take --team-id development-team --ticket 0007 --owner dev
openclaw recipes handoff --team-id development-team --ticket 0007 --tester test
openclaw recipes complete --team-id development-team --ticket 0007
openclaw recipes bindings
openclaw recipes bind --agent-id dev --channel telegram --peer-kind dm --peer-id 6477250615
openclaw recipes unbind --agent-id dev --channel telegram --peer-kind dm --peer-id 6477250615
openclaw recipes cleanup-workspaces
openclaw recipes cleanup-workspaces --prefix smoke- --yes
openclaw recipes remove-team --team-id development-team --plan --json
openclaw recipes remove-team --team-id development-team --yes
Full reference: docs/COMMANDS.md
If you are new, read these in order: