Lobstr
Analysis
Lobstr is a coherent startup-idea scoring skill, but users should know their idea is sent to external services and optional flags can publish it.
Findings (3)
Artifact-based informational review of SKILL.md, metadata, install specs, static scan signals, and capability signals. ClawScan does not execute the skill or run runtime probes.
Checks for instructions or behavior that redirect the agent, misuse tools, execute unexpected code, cascade across systems, exploit user trust, or continue outside the intended task.
Default usage (no flags) makes **one outbound call** to `runlobstr.com/api/score` for scoring and returns privately. No data is published or shared.
The core workflow sends the user's startup idea to an external hosted API, which is disclosed and purpose-aligned but important for users with confidential ideas.
| `--public` | Also publish to runlobstr.com and show share URL | | `--moltbook` | Also post to m/lobstrscore on Moltbook |
The optional flags can publish or post the scan result externally. This is clearly documented and not the default, but it changes user-visible/public state.
Checks whether tool use, credentials, dependencies, identity, account access, or inter-agent boundaries are broader than the stated purpose.
All credentials are read from environment variables only — nothing is hardcoded: - `ANTHROPIC_API_KEY` — optional (BYOK mode only) - `EXA_API_KEY` — optional (BYOK mode only) - `MOLTBOOK_API_KEY` — optional (only with `--moltbook` flag)
The skill can use provider and posting credentials from the environment. This is disclosed and purpose-aligned, with no hardcoded credentials shown.
