Lobster

Executes deterministic multi-step workflow pipelines with resumable human approval checkpoints.

1|Updated Jun 9, 2026
One-click install
npx skills add https://github.com/JEROME-PRAKASH-L/openclaw --skill lobster-jerome-prakash-l
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: Lobster
Source: https://github.com/JEROME-PRAKASH-L/openclaw/tree/main/extensions/lobster
Command: npx skills add https://github.com/JEROME-PRAKASH-L/openclaw --skill lobster-jerome-prakash-l

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires @clawdbot/lobster, typebox.

What problem does it solve? Coordinating multi-step automations like email triage or PR monitoring requires chaining many tool calls, and actions such as sending or deleting data need human approval before execution. Lobster runs typed JSON-first pipelines as one deterministic operation with built-in approval gates and resume tokens. ## Core Features & Use Cases - Deterministic Pipelines: Run typed JSON-first workflow pipelines where the same input always produces the same output, with no LLM variance during execution. - Approval Gates: Insert approve steps that halt execution and return a resume token, letting a human review items before side effects occur. - Resumable Execution: Continue interrupted workflows via the resume action using a resume token or approval ID. - Use Case: Triage your inbox by running gog.gmail.search --query 'newer_than:1d' | email.triage | approve --prompt 'Process these?', review the classified emails, then approve to send draft replies. ## Quick Start Ask the assistant to triage your recent email with a Lobster pipeline and require your approval before sending any replies.

Frequently Asked Questions about Lobster

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I run a multi-step workflow with approval before sending messages?

Run a Lobster pipeline with an approve step, such as a search piped into triage piped into approve. The workflow halts, returns a prompt and resume token, and you continue it with the resume action and approve set to true.

When should I use Lobster instead of calling a tool directly?

Use Lobster for repeatable multi-step automations, stateful monitoring, or actions needing human approval. For single actions like sending one message or simple queries like checking weather, call the tool directly instead.

How do I enable the Lobster plugin in OpenClaw?

Install it with openclaw plugins install @openclaw/lobster, restart the Gateway, then add lobster to the agent's tools allowlist. It is registered as optional because workflows can trigger side effects.

Can Lobster workflows call other OpenClaw tools like Gmail or GitHub?

Yes, pipelines can include an openclaw.invoke step that calls back into OpenClaw tools through the POST /tools/invoke endpoint. The call is gated by gateway auth and tool policy, so a tight allowlist is recommended.

What are the limitations of Lobster workflows?

Lobster is unsuitable for one-off tasks, simple single-action requests, or flows needing LLM interpretation mid-pipeline. It also does not manage OAuth tokens, and input requests mid-workflow are not yet supported by the OpenClaw tool.