Lobster Workflows
v1.0.0Transform OpenClaw cron jobs into Lobster workflows. Analyze, inspect, and validate job migrations. Use when converting automations to deterministic, approval-gated workflows with resume capabilities.
⭐ 1· 2.3k·5 current·5 all-time
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
OpenClaw
Suspicious
medium confidencePurpose & 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.
What to consider before installing
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.Like a lobster shell, security has layers — review code before you run it.
latestvk97dmcwhp630b75jpgp5m208d980863x
License
MIT-0
Free to use, modify, and redistribute. No attribution required.
Runtime requirements
🦞 Clawdis
Binsopenclaw, python3