Skip to main content
This page is organized by the jobs humans actually need to do.

1) Browse recipes

List all recipes

Show one recipe

Check recipe status / missing skills


2) Install recipes and skills

Install a marketplace recipe into your workspace

Optional:
  • --registry-base <url>
  • --overwrite
Alias:

Install a skill from ClawHub

Options:
  • --yes
  • --global
  • --agent-id <id>
  • --team-id <id>

3) Scaffold agents and teams

Scaffold a single agent

Useful options:
  • --agent-id <id>
  • --name <name>
  • --recipe-id <recipeId>
  • --auto-increment
  • --overwrite-recipe
  • --overwrite
  • --apply-config
What it writes:
  • ~/.openclaw/workspace-<agentId>/...
  • workspace recipe file under ~/.openclaw/workspace/recipes/

Scaffold a team

Useful options:
  • --team-id <teamId>
  • --recipe-id <recipeId>
  • --auto-increment
  • --overwrite-recipe
  • --overwrite
  • --apply-config
What it writes:
  • ~/.openclaw/workspace-<teamId>/...
  • role folders under roles/
  • ticket lanes under work/
  • workspace recipe file under ~/.openclaw/workspace/recipes/

Add a role to an existing team

Useful options:
  • --team-id <teamId>
  • --role <role>
  • --recipe <recipeId>
  • --agent-id <agentId>
  • --apply-config
  • --overwrite
  • --no-cron

4) Work the file-first ticket flow

The normal lane flow is:

Turn a request into a ticket

Options:
  • --team-id <teamId>
  • --request <text>
  • --owner dev|devops|lead|test
  • --yes

List tickets

Move a ticket between lanes

Options:
  • --team-id <teamId>
  • --ticket <ticket>
  • --to backlog|in-progress|testing|done
  • --completed
  • --yes

Assign a ticket

Options:
  • --team-id <teamId>
  • --ticket <ticket>
  • --owner dev|devops|lead|test
  • --overwrite
  • --yes

Take a ticket

Shortcut for assign + move to in-progress.

Handoff to testing

Complete a ticket

Clean up stale assignment stubs for done work


5) Workflows

Use these when you are running file-first workflows from shared-context/workflows/.

See workflow command help

Run one workflow manually

Runner commands

Worker commands

Media driver commands

List registered media generation drivers (and whether required API keys are present):
This is what ClawKitchen uses to populate the media provider dropdown. More: MEDIA_DRIVERS.md

Approval commands

Important workflow note

After installing ClawRecipes, workflows may still need optional pieces turned on. Examples:
  • LLM workflows may require the built-in llm-task plugin to be enabled
  • publishing workflows may require outbound.post config or a local posting patch to be reapplied
So if you install the plugin and then say “the workflow exists but does not fully work,” check the optional workflow dependencies next. More:

6) Bindings

Bindings route messages/traffic to the right agent.

Show bindings

Add a binding

Remove a binding


7) Migrate / remove / clean up

Migrate a legacy team layout

Remove a team safely

Clean up temporary workspaces


Fastest useful command set

If you only want the high-value commands: