The Claw Kitchen

The ultimate mission control for your OpenClaw/Clawd. Deploy a team of agents or a fleet of swarms using custom workflows.

[The Claw Kitchen @theclawkitchen]

🍽️ Introducing ClawKitchen ~ the ClawRecipes UI🚀

Tired of wasting weeks configuring agents?

Spin up your ARMY OF AGENTS in minutes!!

Build faster. Scale harder.

Easy Install: openclaw plugins install @jiggai/kitchen

[ClawRecipes @clawrecipes]

New Release!! We've tested and pushed new packages for CR and CK. Both now support @openclaw 2026.5.x

The best way to install is:
openclaw plugins install @jiggai/recipes --force
openclaw plugins install @jiggai/kitchen --force

Force is required on recipes because clawhub is broken, they still have the older package.

[The Claw Kitchen @theclawkitchen]

We keep adding features to the kitchen!

No more waiting for runs - Workflows have been updated to indicate which node it’s processing and the status

[ClawRecipes @clawrecipes]

MCP’s are great tools. They empower agents to accomplish so much more. But where are they not as useful as a structured integration?

When there are multiple steps that require steps like approval, the use of additional agents for compliance, research, and another refinement tasks Auditable tasks and rollbacks.

MCP’s are great tools, but they do not replace structure and good process design.

When an MCP is not enough, use ClawRecipes combined with ClawKitchen as your operation layer. It’s what we’re built for. @openclaw

[ClawRecipes @clawrecipes]

Not all models are made the same. We know this. You know this. Now we've enabled you to select a specific model for all our workflow nodes! Enjoy

[ClawRecipes @clawrecipes]

Creating awesome videos with AI has just got easier!

We've launched new image and video nodes to our workflows (use ClawKitchen to visualize.) You can select from your already installed SKILLS and providers; doesn't get much easier.

Don't have a skill, we included some defaults that ClawKitchen will install for you.

[The Claw Kitchen @theclawkitchen]

Want to go viral?

Here are some good tips

[Corey Ganim @coreyganim]

https://t.co/3zmy8gtoWY

[The Claw Kitchen @theclawkitchen]

@VadimStrizheus You never used ClawRecipes to create your teams. Would have solved a lot of your OC problems

[The Claw Kitchen @theclawkitchen]

@VadimStrizheus You never used ClawRecipes to create your teams. Would have solved a lot of your OC problems

[RJxDetroit @rjxdetroit]

The future of AI is not Agents. It’s infrastructure.

The Rise of Agents as Infrastructure (AaI) is coming! Read all about it on my Substack

https://t.co/8lsNRAfMhV

[The Claw Kitchen @theclawkitchen]

For those who love SEO

[Sarvesh Shrivastava @bloggersarvesh]

https://t.co/BPMJXHnL8m

[The Claw Kitchen @theclawkitchen]

@mchulet https://t.co/MdJNZcNJ5h

[Vadim @VadimStrizheus]

OpenClaw has finally reached the corporate world. 🦞

99% of people are going to be jobless in the next 3 years.

[ClawRecipes @clawrecipes]

Think of agents as roles and skills as capabilities.

Example:

• Agent: copywriter
• Skill: write an X thread
• Agent: QA
• Skill: verify workflow run artifacts
• Agent: lead
• Skill: triage backlog and assign next task

Why this matters:

1. agents should have a job
2. skills should be reusable
3. prompts should not contain your whole operating system

Small example:

Instead of:

• “You are a marketing genius, QA expert, coder, PM, and writer…”

Do:

• agent = marketing-copywriter
• skill = draft-social-posts
• files = brand rules + campaign brief + examples

Cleaner inputs.
Better outputs.
Less chaos.

[ClawRecipes @clawrecipes]

Think of agents as roles and skills as capabilities.

Example:

• Agent: copywriter
• Skill: write an X thread
• Agent: QA
• Skill: verify workflow run artifacts
• Agent: lead
• Skill: triage backlog and assign next task

Why this matters:

1. agents should have a job
2. skills should be reusable
3. prompts should not contain your whole operating system

Small example:

Instead of:

• “You are a marketing genius, QA expert, coder, PM, and writer…”

Do:

• agent = marketing-copywriter
• skill = draft-social-posts
• files = brand rules + campaign brief + examples

Cleaner inputs.
Better outputs.
Less chaos.

[ClawRecipes @clawrecipes]

A team workflow should look like work moving through roles, not one giant prompt.

Simple version:

1. Lead scopes the task
• defines the ask
• sets constraints
• points to files/tickets

2. Specialist executes
• dev writes code
• writer drafts copy
• analyst researches
• QA verifies

3. Artifacts get written
• ticket updates
• logs
• run outputs
• screenshots
• PR links

4. Approval gate happens if needed
• publish / deploy / merge / send

Small example:

• Lead creates ticket 0209
• Dev updates src/app/...
• QA checks UI + screenshots
• Lead opens PR
• Human approves merge

That’s a workflow.
“Agent, do everything” isn’t.

Try @clawrecipes for your @openclaw. You won’t regret it.

https://t.co/9eaJkCHk5D

[The Claw Kitchen @theclawkitchen]

@revgen__ Can’t see it. Increase the size dramatically

[The Claw Kitchen @theclawkitchen]

@suni_code Two projects that support File-first agent teams in @openclaw. It doesn’t get any better than this

https://t.co/kirNuatwcJ

[ClawRecipes @clawrecipes]

Skills are great when agents use them.

What if they don’t? What if they ignore the skill file?

You can’t protect your OpenClaw with skills. You can’t guarantee behavior with skills.

Same applies to agent files. This is why you need workflows. Workflows create a structure your agents can’t ignore.

Start creating workflows in ClawKitchen, https://t.co/6WdjLbGCQh

[ClawRecipes @clawrecipes]

Most AI systems fail because they treat all memory like one bucket.

ClawRecipes uses a better model that splits memory into layers:

1. Assistant continuity
• personal preferences
• tone
• repeated user habits

2. Team coordination
• what’s in progress
• blockers
• handoffs
• status notes

3. Shared team knowledge
• docs
• policies
• decisions
• reusable references

4. Role working memory
• what a specific agent needs right now
• current ticket
• current plan
• temporary notes

Small example:

• MEMORY .md → “Daniel prefers ClawRecipes before OpenClaw”
• notes/status.md → “PR #143 opened, waiting review”
• shared-context/priorities.md → “Focus on workflow reliability this week”
• ticket comments → “QA failed because runId didn’t match canonical folder”

One blob of memory becomes noise.
Layered memory becomes usable.

https://t.co/UHqW7jEAgQ

[The Claw Kitchen @theclawkitchen]

@hridoyreh Feel free to test and share @clawrecipes. The only way to create a standardized team in openclaw.