BF moltbook-cli
Moltbook CLI Pro: Full self-contained CLI for OpenClaw agents. Handles feed/search/post/like/comment/reply/delete/follow/auto-reply/notify. Quick agent setup via INSTALL.md + .env.example (no keys bundled).</description>
As a process F 19/100 · Will not run — References files that are not bundled: scripts/.env
What is at stake
Medium-severity findings: the skill is probably honest, but read what alarmed the scanner.
Below is the worst case for this category. The finding here is medium: the guard saw a sign, not a proof.
The instructions or scripts send data out: environment variables, keys, file contents, chat history. You may never notice, because the agent performs the upload as "part of the task".
If the upload is not needed for the task, remove it: catalogs flag such skills and delist them. If it is needed, name the destination explicitly, say what leaves the machine, and give the user a switch.
How to improve
- Say in the description WHEN to use the skill ("use when…", example requests): that is the agent's main cue.
- The text references files that are not there: add them or drop the references.
- Your own cases (evals/evals.json, 4–6 real requests with expected answers): the full check would then run those instead of a model-drafted suite.
- A spec.yaml with trigger phrases and assertions — a behaviour contract for CI; `skilltest init` writes a template.
Guard findings · 2
✓ No critical or high findings
Medium and low: 2
-
medium Exfiltration
net-credential-usescripts/notify.sh:17Credential used in a network call (verify the destination is the intended service)curl -s -X POST "https://api.telegram.org/bot${TELEGRAM_NOTIFY_TOKEN}/sendMessage" \ -
low Exfiltration
exfil-webhook-urlscripts/notify.sh:17Webhook / callback URL commonly used for exfiltration (verify the destination) (placeholder value)curl -s -X POST "https://api.telegram.org/bot${TELEGRAM_NOTIFY_TOKEN}/sendMessage" \placeholder
Files scanned: 7. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
frontmatter-yamlSKILL.md: the frontmatter is not valid YAML (YAML parse error: Nested mappings are not allowed in compact mappings at line 2, column 14: description: Moltbook CLI Pro: Full self-contained CLI for OpenClaw agents. Han… ^ ); fields were read line by line. The usual cause is a colon inside an unquoted value - warning
description-no-whendescription does not say WHEN to use the skill (no "use when") - warning
missing-refreference to a missing file: scripts/.env
Process rating: all ten parameters 19/100
- 0Tools and files. 1 referenced file(s) missing: scripts/.env
- 0Result and completion. Does not say what the result is
- 0Inputs and preconditions. Does not say what the process needs to start
- 0Failures and branches. Linear process with no failure handling
- 0Progress reporting. Says nothing while it works
- 20When it triggers. No condition that starts the skill
- 30Running it twice. 1 mutating operations with no state check
- 40Consistency. Frontmatter name (moltbook-cli) differs from the folder (drones-moltbook-cli)
- 43Steps. 2 steps, 1 vague phrases
- 100Execution cost. Instruction body is 378 tokens
Everything here is measured from the skill text rather than judged by a model, so the numbers are checkable. A parameter weighs more when it is a more common reason for the process to stall.
Quality signals
- +5Description has no quoted example phrases that should trigger the skill
- +4Description does not say when NOT to use the skill (false activations)
- +3No numbered steps or checklist
- +3Output format is not stated: the model decides each time
- +1No license
- +2Single-language instructions
- +3Description length 220: enough signal without eating the budget
- +4Structure: 7 headings
- +4Has examples (2 code blocks)
- +4Reference files are cited in the instructions (1 of 2)
- +3All 3 scripts are documented
Quality base 70; lint remarks subtract, signals add up to 100. Result: 60.