lobster-jobs

What This Skill Does

The lobster-jobs skill is a specialized utility designed for OpenClaw users aiming to transition from volatile, LLM-heavy cron-based automations to robust, deterministic Lobster workflows. By providing a suite of tools for analysis, validation, and conversion, this skill acts as a bridge between spontaneous agent tasks and structured enterprise-grade process management. It evaluates existing cron jobs based on their inherent logic, categorizing them by migration readiness: Fully Migratable (systemEvent), Partial Migration (agentTurn), or Not Migratable (LLM-dependent). By shifting to Lobster workflows, you gain the ability to insert approval gates, manage state, and utilize resumable execution—features essential for reliable long-term operations.

Installation

To install this skill, use the ClawKit CLI utility within your OpenClaw environment:

clawhub install openclaw/skills/skills/kesslerio/lobster-jobs

After installation, ensure the binary is accessible in your shell environment. You can add it to your PATH by updating your .bashrc or .zshrc file:

export PATH="$PATH:/home/art/niemand/skills/lobster-jobs/bin"

Alternatively, create a symbolic link to your local bin directory:

ln -s /home/art/niemand/skills/lobster-jobs/bin/lobster-jobs ~/.local/bin/

Use Cases

• Production Automation: Converting critical shell scripts that run on cron into stateful workflows that require manual oversight before executing destructive actions.
• Migration Projects: Auditing an entire suite of existing agent tasks to identify which are suitable for hard-coded workflow logic, thereby reducing token costs and improving reliability.
• Compliance and Auditing: Implementing approval-gated workflows for sensitive operations, ensuring a human-in-the-loop audit trail is created for every execution.
• Error Recovery: Moving from flaky agent turns to resumable Lobster workflows that can pick up exactly where they failed during network or service interruptions.

Example Prompts

1. "lobster-jobs list and tell me which of my current cron jobs are the best candidates for a full conversion to Lobster workflows."
2. "Inspect job 17fe68ca and let me know why it is marked as partial migration; can I force a conversion?"
3. "Create a new workflow named 'cleanup-logs' using the with-approval template, then validate the file for me."

Tips & Limitations

• Deterministic vs. LLM: Always prioritize converting systemEvent jobs first. If a job relies heavily on LLM reasoning to interpret input, it may not be suitable for deterministic translation.
• Validation First: Always run lobster-jobs validate on any manually modified workflow files before deploying them to production to prevent syntax runtime failures.
• State Management: When using stateful templates, ensure your workflow environment has persistent storage configured, or your state markers will be lost upon container recycling.