Code Pluginsource linked

ClawRecipesv0.4.50

ClawRecipes plugin for OpenClaw (markdown recipes -> scaffold agents/teams)

@jiggai/recipes·runtime recipes·by @rjdjohnston

Community code plugin. Review compatibility and verification before install.

openclaw plugins install clawhub:@jiggai/recipes

Latest release: v0.4.50Download zip

Capabilities

Compatibility

Built With Open Claw Version

2026.3.28

Plugin Api Range

2026.4.9

Security Scan

VirusTotal

Benign

View report →

OpenClaw

Benign

high confidence

✓

Purpose & Capability

Name/description (scaffold recipes → teams/agents/workflows) match the code, docs, and CLI instructions. The project includes scaffold, team, ticket, workflow, and media-driver subsystems that are expected for this purpose. No environment variables or unrelated binaries are declared as required.

ℹ

Instruction Scope

SKILL.md instructs the user to install the plugin (openclaw plugins install, or npm into ~/.openclaw/plugins) and then run CLI commands to scaffold workspaces. It also calls out optional steps (apply-config, enable posting, apply controller-specific patches). These are reasonable for a scaffolding plugin, but they do grant the plugin the ability to write workspace files (~/.openclaw/workspace-*) and to apply OpenClaw agent config when --apply-config is used. Users should review generated files before applying config or enabling auto-install/cron.

✓

Install Mechanism

Registry has no automated download/install spec (the SKILL.md documents standard openclaw/npm install steps). The package includes source files and a normal package.json with small, well-known dependencies. There are no opaque external download URLs or extraction steps in the registry metadata.

ℹ

Credentials

The plugin declares no required environment variables or primary credential, which is appropriate for a scaffolding tool. The codebase contains a media-driver subsystem that can use provider-specific env vars at runtime (e.g., image/video providers). Those provider credentials are not required for basic scaffolding, but will be needed if you run media drivers or outbound posting. This is proportionate provided users only enable/use those features and supply credentials intentionally.

✓

Persistence & Privilege

The skill is not always-enabled (always:false) and uses the normal model-invocation behavior. It performs workspace-level file writes and can apply OpenClaw agent config when the user asks (e.g., --apply-config), which is expected for a scaffolder. No indication it modifies other skills' configs or demands system-wide privileges.

Assessment

This plugin appears to do exactly what it says: it scaffolds file-first teams/agents, manages tickets/workflows, and includes optional media-driver and outbound-posting features. Before installing: 1) Review the bundled recipes you’ll scaffold (they write into ~/.openclaw/workspace-<id>/). 2) Don’t use --apply-config until you’ve inspected generated agent TOOLs.md and AGENTS.md (apply-config will write agent config). 3) Leave autoInstallMissingSkills and cronInstallation at their safe defaults (auto-install=false, cron=prompt) unless you understand and permit the plugin to install other skills or register scheduled runs. 4) Media/video/image features may require provider keys (OpenAI/Runway/etc.) — supply those only when you intend to use them. 5) If you want extra safety, run scaffold into a temporary test team id and inspect files before wider deployment.

Verification

Tier

source linked

Scope

artifact only

Summary

Validated package structure and linked the release to source metadata.

Source

github.com/JIGGAI/ClawRecipes

Commit

https://gith

Tag

v0.4.50

Provenance

Scan status

clean

ClawRecipes

ClawRecipes is an OpenClaw plugin for scaffolding agents, teams, and file-first workflows from Markdown recipes.

If you want the short version:

install the plugin
scaffold a team or agent
dispatch work into tickets
run the file-first workflow
optionally use ClawKitchen for a UI on top

ClawRecipes is CLI-first. It works without a UI.

What ClawRecipes does

ClawRecipes gives you:

recipes written in Markdown
agent scaffolding (openclaw recipes scaffold)
team scaffolding (openclaw recipes scaffold-team)
file-first ticket workflow (dispatch → backlog → in-progress → testing → done)
workflow runner utilities for scheduled / approval-gated workflows
workspace recipe installs from the marketplace
ClawHub skill installs for agents or teams

It is built for people who want durable artifacts on disk, not hidden app state.

Quickstart

1) Install the plugin

OpenClaw plugin install (recommended)

openclaw plugins install @jiggai/recipes
openclaw gateway restart
openclaw plugins list

Note: The OpenClaw plugin installer enforces pluginApi version checks. If you see a version mismatch error, use the npm install method below instead.

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

2) See what recipes you have

openclaw recipes list
openclaw recipes show development-team
openclaw recipes status development-team

3) Scaffold a team

openclaw recipes scaffold-team development-team \
  --team-id development-team \
  --apply-config \
  --overwrite

This creates:

~/.openclaw/workspace-development-team/
team roles under roles/
ticket lanes under work/
optional OpenClaw agent config entries (when --apply-config is used)

4) Put work into the system

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

Workflow support

ClawRecipes supports file-first workflows with:

workflow JSON files under shared-context/workflows/
workflow runs under shared-context/workflow-runs/
runner / worker execution model
approval-gated steps
tool nodes
LLM nodes

Basic workflow commands

# 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

Approval flow commands

# 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>

Important workflow posting note

This is the part most people trip over.

What ships by default

Published ClawRecipes builds are intentionally conservative:

workflow posting side effects are not automatically turned on for every install
the old local marketing.post_all posting path is not something users should assume is active after install

What you should do after installing

If you want workflows that actually publish content:

Recommended path

use outbound.post
configure an outbound posting service
keep approval gates in the workflow

Local-controller / patched path

if you are using a local controller-specific patch for workflow posting, you must apply that patch after install/update
and you may need to explicitly tell your assistant to turn workflow posting back on for your local environment

In plain English:

installing ClawRecipes does not mean "workflow posting is live"
you must either:
1. configure the supported outbound posting path, or
2. reapply your local posting patch after install/update

If you are using RJ's local controller flow, document and keep your patch handy.

Common commands

Recipes

openclaw recipes list
openclaw recipes show development-team
openclaw recipes install clinic-team

Agents and teams

# 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

Ticket workflow

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 cleanup-closed-assignments --team-id development-team

Bindings

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

Cleanup / removal

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

Recommended docs order for humans

If you are new, read these in order:

If you are building recipes:

If you are contributing to the codebase:

ClawKitchen

If you want a UI for teams, workflows, goals, approvals, and management, use:

ClawKitchen: https://github.com/JIGGAI/ClawKitchen

ClawKitchen is optional. ClawRecipes works without it.

More: docs/CLAWCIPES_KITCHEN.md

Development

npm test
npm run test:coverage
npm run smell-check

License

ClawRecipes is licensed under Apache-2.0.