← 返回 Skills 市场
kesslerio

Lobster Workflows

作者 kesslerio · GitHub ↗ · v1.0.0
cross-platform ⚠ suspicious
2503
总下载
1
收藏
5
当前安装
1
版本数
在 OpenClaw 中安装
/install lobster-jobs
功能描述
Transform OpenClaw cron jobs into Lobster workflows. Analyze, inspect, and validate job migrations. Use when converting automations to deterministic, approval-gated workflows with resume capabilities.
使用说明 (SKILL.md)

lobster-jobs

Transform OpenClaw cron jobs into Lobster workflows with approval gates and resumable execution.

Purpose

OpenClaw cron jobs are either:

  • systemEvent: Simple shell commands (fully deterministic)
  • agentTurn: Natural language instructions spawning AI agents (flexible but token-heavy)

Lobster workflows offer:

  • Deterministic execution: No LLM re-planning each step
  • Approval gates: Hard stops requiring explicit user approval
  • Stateful execution: Remembers cursors/checkpoints
  • Resumability: Pauses and resumes exactly where left off

This skill helps analyze existing cron jobs and transform them into Lobster workflows.

Commands

Tier 1 (Available Now)

lobster-jobs list

List all cron jobs with their Lobster readiness score.

Output categories:

  • Fully Migratable: Simple shell commands (systemEvent)
  • 🟡 Partial Migration: Mixed deterministic + LLM steps (agentTurn)
  • Not Migratable: Heavy LLM reasoning required

lobster-jobs inspect \x3Cjob-id>

Inspect a specific cron job with detailed migration assessment.

Shows:

  • Job metadata (schedule, target, payload type)
  • Lobster migration status and reason
  • Payload preview
  • Migration recommendation

lobster-jobs validate \x3Cworkflow-file>

Validate a Lobster workflow YAML file against schema.

Checks:

  • Required fields (name, steps)
  • Step structure (id, command)
  • Approval gate syntax
  • Condition syntax

Tier 2 (Available Now)

lobster-jobs convert \x3Cjob-id>

Transform a cron job into a Lobster workflow.

lobster-jobs convert 17fe68ca
lobster-jobs convert 17fe68ca --output-dir ~/workflows
lobster-jobs convert 17fe68ca --force  # Overwrite existing

Generates:

  • .lobster workflow file in ~/.lobster/workflows/
  • Extracts commands from systemEvent or agentTurn payloads
  • Auto-validates generated workflow

Options:

  • --output-dir, -o: Custom output directory
  • --force, -f: Overwrite existing workflow
  • --keep-on-error: Keep file even if validation fails

lobster-jobs new \x3Cname>

Create a new Lobster workflow from scratch using templates.

lobster-jobs new my-workflow
lobster-jobs new my-workflow --template with-approval
lobster-jobs new my-workflow --template stateful

Templates:

  • simple-shell: Basic command execution
  • with-approval: Approval gate workflow
  • stateful: Workflow with cursor/state tracking

Installation

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

# Or create symlink
ln -s /home/art/niemand/skills/lobster-jobs/bin/lobster-jobs ~/.local/bin/

Quick Start

# See all your cron jobs and their migration status
lobster-jobs list

# Inspect a specific job
lobster-jobs inspect 17fe68ca

# Convert a job to Lobster workflow
lobster-jobs convert 17fe68ca

# Create a new workflow from template
lobster-jobs new my-workflow --template with-approval

# Validate a workflow file
lobster-jobs validate ~/.lobster/workflows/my-workflow.lobster

Workflow File Format

name: my-workflow
description: Optional description

steps:
  - id: fetch_data
    command: some-cli fetch --json
    
  - id: process
    command: some-cli process
    stdin: $fetch_data.stdout
    
  - id: approve_send
    command: approve --prompt "Send notification?"
    approval: required
    
  - id: send
    command: message.send --channel telegram --text "Done!"
    condition: $approve_send.approved

Migration Strategy

Wrapper Approach (Recommended)

Keep cron as scheduler, change payload to call Lobster:

{
  "payload": {
    "kind": "systemEvent",
    "text": "lobster run ~/.lobster/workflows/my-workflow.lobster"
  }
}

Benefits:

  • Rollback is trivial (revert payload)
  • Incremental migration
  • Cron scheduling already works

Handling LLM Judgment

For jobs needing both deterministic steps and LLM reasoning:

steps:
  - id: gather
    command: gh issue list --json title,body
    
  - id: triage
    command: clawd.invoke
    prompt: "Classify these issues by urgency"
    
  - id: notify
    command: telegram-send

The workflow is deterministic; the LLM is a black-box step.

Edge Cases

Issue Handling
Idempotency Workflows track step completion; restart-safe
Approval timeouts Configurable timeout with default action
Secret handling Environment variables or 1Password refs
Partial failures convert validates before writing

References

安全使用建议
This package is an instruction-only skill that documents a 'lobster-jobs' CLI but provides no code, no install bundle, and no source repository or homepage. Before installing or running anything: 1) Ask the publisher for the canonical source (GitHub repo, release archive) and verify checksums/signatures; do not add or execute binaries from unknown local paths like /home/art/niemand/.... 2) Confirm where the 'lobster-jobs' binary comes from — the skill metadata does not supply it. 3) Backup your cron configuration and any existing ~/.lobster workflows before using convert/--force. 4) Inspect any generated workflow files for embedded secrets or unexpected external endpoints (telegram, webhooks, etc.). 5) Prefer vendor-distributed packages (official repo or release) over ad-hoc symlink instructions. If the author can provide a legitimate repository or an installable package and the binary's source matches the docs, this assessment could be upgraded to benign.
功能分析
Type: OpenClaw Skill Name: lobster-jobs Version: 1.0.0 The OpenClaw AgentSkills skill bundle appears benign. The `SKILL.md` clearly outlines the purpose of transforming cron jobs into Lobster workflows, requiring standard binaries like `openclaw` and `python3`. File operations (reading cron job definitions, writing workflow YAMLs) are consistent with the stated purpose, targeting expected locations or user-specified directories. There is no evidence of prompt injection against the OpenClaw agent, data exfiltration, malicious execution, or persistence mechanisms. The example of `clawd.invoke` within a workflow is a feature of the workflow itself, not a malicious instruction to the agent executing the skill.
能力评估
Purpose & Capability
The skill's stated purpose (convert OpenClaw cron jobs to Lobster workflows) is plausible and the declared required binaries (openclaw, python3) partly match that purpose. However the SKILL.md presents a 'lobster-jobs' CLI and uses 'lobster run' and other commands but the skill bundle contains no code, no install spec, and does not declare the 'lobster-jobs' or 'lobster' binaries as required. The lack of source/homepage and the presence of a hard-coded developer path (/home/art/niemand/skills/...) are additional mismatches.
Instruction Scope
The instructions describe actions that touch scheduler payloads and write workflow files to ~/.lobster/workflows/, and give examples for changing cron payloads to call Lobster. As an instruction-only skill this is mostly guidance, but it implies the operator or binaries will read cron job metadata and write files under the user's home. The SKILL.md also contains example steps invoking external CLIs (gh, telegram-send, 1Password refs, a 'clawd.invoke' step) that are not authorized/declared—this expands the implied scope without justification. There is no explicit instruction to read unrelated system files, but the guidance expects manipulation of cron/job payloads which is sensitive.
Install Mechanism
There is no install spec and no code files; the SKILL.md asks users to add a developer-local path or symlink a binary. That developer-local path is specific to an individual environment (user 'art/niemand'), which looks like a leftover example rather than a vetted install procedure. Because no binary or source is provided, it's unclear what 'lobster-jobs' actually is or where to obtain a trustworthy build.
Credentials
The skill requests no environment variables, credentials, or config paths. The documentation mentions that workflows may use env vars or 1Password refs, but the skill itself does not request or require secrets. That is proportionate — however, users should be aware that actual runtime (the CLI) may prompt for or require credentials for external services referenced in workflow steps.
Persistence & Privilege
The skill is not forced-always, and does not request or claim elevated platform privileges. It does instruct writing workflow files to ~/.lobster/workflows/ and suggests altering cron payloads; these are normal for a migration tool but are potentially impactful operations and should be done with backups/consent. Autonomous invocation is allowed by default but not unusual; it does not combine with 'always:true' or large declared credential sets.
如何使用
  1. 确保已安装 OpenClaw(本地或 Docker 部署)
  2. 在对话框中输入安装命令:/install lobster-jobs
  3. 安装完成后,直接呼叫该 Skill 的名称或使用 /lobster-jobs 触发
  4. 根据 Skill 的参数说明提供必要输入,即可获得结构化输出
版本历史
v1.0.0
Initial ClawHub release
元数据
Slug lobster-jobs
版本 1.0.0
许可证
累计安装 5
当前安装数 5
历史版本数 1
常见问题

Lobster Workflows 是什么?

Transform OpenClaw cron jobs into Lobster workflows. Analyze, inspect, and validate job migrations. Use when converting automations to deterministic, approval-gated workflows with resume capabilities. 它是一个面向 Claude Code / OpenClaw 的 AI Agent Skill 插件,目前累计下载 2503 次。

如何安装 Lobster Workflows?

在 OpenClaw 或 Claude Code 对话框中运行命令「/install lobster-jobs」即可一键安装,无需额外配置。

Lobster Workflows 是免费的吗?

是的,Lobster Workflows 完全免费(开源免费),可自由下载、安装和使用。

Lobster Workflows 支持哪些平台?

Lobster Workflows 跨平台运行,可在任意部署了 OpenClaw / Claude Code 的环境中使用(cross-platform)。

谁开发了 Lobster Workflows?

由 kesslerio(@kesslerio)开发并维护,当前版本 v1.0.0。

💬 留言讨论