FF proactive-amcp
Proactive immortal — behavior ontology (learn remember stuck) hooks kick in · IPFS soul · Solvr · self-heals on boot · disk check · watchdog 🏴☠️
Proactive immortal — behavior ontology (learn remember stuck) hooks kick in · IPFS soul · Solvr · self-heals on boot · disk check · watchdog 🏴☠️
As a process F 41/100 · Will not run — References files that are not bundled: docs/WATCHDOG-RECOVERY.md
What is at stake
The skill contains fragments that, in the wrong hands, cost money or data. Below: what the installer risks and what the author should do.
The skill contains commands that delete files, rewrite disks or execute code fetched from the network. The agent may run them without asking if it believes the instructions require it.
Replace destructive commands with safe equivalents that ask for confirmation, scope them to one folder, and stop piping curl into a shell: pin a version and a checksum.
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
- Address the high-severity findings: each costs 18 safety points. If one is a false positive, add the rule id to guard.allow in spec.yaml.
- 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 · 26
-
high Dangerous commands
cmd-persistencescripts/init-services.sh:93Persistence mechanism (cron / launchd / scheduled task / autorun registry){ crontab -l 2>/dev/null || true; echo "$cron_line"; } | crontab - -
high Dangerous commands
cmd-persistencescripts/init-services.sh:208Persistence mechanism (cron / launchd / scheduled task / autorun registry){ crontab -l 2>/dev/null || true; echo "$cron_line"; } | crontab - -
high Dangerous commands
cmd-persistencescripts/install.sh:309Persistence mechanism (cron / launchd / scheduled task / autorun registry){ crontab -l 2>/dev/null || true; echo "$cron_line"; } | crontab - -
high Dangerous commands
cmd-persistencescripts/install.sh:391Persistence mechanism (cron / launchd / scheduled task / autorun registry){ crontab -l 2>/dev/null || true; echo "$cron_line"; } | crontab -
Medium and low: 22
-
medium Exfiltration
net-redirectable-api-keyscripts/generate-problem-summary.py:95Helper sends the API key to a host configured by an environment variable — the key can be redirected to another serverAPI key + configurable base URL from environment
-
medium Dangerous commands
cmd-persistencescripts/init-services.sh:90Persistence mechanism (cron / launchd / scheduled task / autorun registry) (detector / deny-list definition)crontab -l 2>/dev/null | grep -v "# amcp-watchdog" | { cat; echo "$cron_line"; } | crontab -detector -
medium Dangerous commands
cmd-persistencescripts/init-services.sh:206Persistence mechanism (cron / launchd / scheduled task / autorun registry) (detector / deny-list definition)crontab -l 2>/dev/null | grep -v "# amcp-checkpoint" | { cat; echo "$cron_line"; } | crontab -detector -
medium Dangerous commands
cmd-persistencescripts/install.sh:307Persistence mechanism (cron / launchd / scheduled task / autorun registry) (detector / deny-list definition)crontab -l 2>/dev/null | grep -v "# amcp-watchdog" | { cat; echo "$cron_line"; } | crontab -detector -
medium Dangerous commands
cmd-persistencescripts/install.sh:389Persistence mechanism (cron / launchd / scheduled task / autorun registry) (detector / deny-list definition)crontab -l 2>/dev/null | grep -v "# amcp-checkpoint" | { cat; echo "$cron_line"; } | crontab -detector -
medium Dangerous commands
cmd-pipe-to-shellscripts/install.sh:443Downloads and executes remote code from an unrecognised host (pipe to shell) (the skill's own vendor host)if curl -sL --connect-timeout 10 --max-time 30 "https://solvr.dev/install.sh" | bash 2>/dev/null; then
vendor-host -
medium Dangerous commands
cmd-pipe-to-shellscripts/install.sh:472Downloads and executes remote code from an unrecognised host (pipe to shell) (the skill's own vendor host)if curl -sL --connect-timeout 10 --max-time 60 "https://solvr.dev/install.sh" | bash 2>/dev/null; then
vendor-host -
low Dangerous commands
cmd-background-processscripts/_config-fix.sh:101Starts a background / autostarted processnohup openclaw gateway start > /tmp/openclaw-gateway.log 2>&1 &
-
low Secrets in code
secret-anthropic-keyscripts/_diagnose-claude.sh:134Anthropic API key (placeholder value)log_error " proactive-amcp config set anthropic.apiKey sk-a…KEY"
placeholder -
low Dangerous commands
cmd-cron-mentionscripts/init-services.sh:87Mentions editing / listing crontabif crontab -l 2>/dev/null | grep -q "# amcp-watchdog"; then
-
low Dangerous commands
cmd-cron-mentionscripts/init-services.sh:90Mentions editing / listing crontabcrontab -l 2>/dev/null | grep -v "# amcp-watchdog" | { cat; echo "$cron_line"; } | crontab - -
low Dangerous commands
cmd-cron-mentionscripts/init-services.sh:93Mentions editing / listing crontab{ crontab -l 2>/dev/null || true; echo "$cron_line"; } | crontab - -
low Dangerous commands
cmd-cron-mentionscripts/init-services.sh:97Mentions editing / listing crontab (detector / deny-list definition; string literal in code, not executed)info "View: crontab -l | grep amcp"
detectorcode literal -
low Dangerous commands
cmd-cron-mentionscripts/init-services.sh:204Mentions editing / listing crontabif crontab -l 2>/dev/null | grep -q "# amcp-checkpoint"; then
-
low Dangerous commands
cmd-cron-mentionscripts/install.sh:306Mentions editing / listing crontabif crontab -l 2>/dev/null | grep -q "# amcp-watchdog"; then
-
low Dangerous commands
cmd-cron-mentionscripts/install.sh:307Mentions editing / listing crontabcrontab -l 2>/dev/null | grep -v "# amcp-watchdog" | { cat; echo "$cron_line"; } | crontab - -
low Dangerous commands
cmd-cron-mentionscripts/install.sh:309Mentions editing / listing crontab{ crontab -l 2>/dev/null || true; echo "$cron_line"; } | crontab - -
low Dangerous commands
cmd-cron-mentionscripts/install.sh:388Mentions editing / listing crontabif crontab -l 2>/dev/null | grep -q "# amcp-checkpoint"; then
-
low Dangerous commands
cmd-cron-mentionscripts/install.sh:389Mentions editing / listing crontabcrontab -l 2>/dev/null | grep -v "# amcp-checkpoint" | { cat; echo "$cron_line"; } | crontab - -
low Dangerous commands
cmd-background-processscripts/restore-agent.sh:394Starts a background / autostarted processnohup openclaw gateway start > /tmp/openclaw-gateway.log 2>&1 &
-
low Dangerous commands
cmd-cron-mentionSECURITY.md:184Mentions editing / listing crontab (documentation of a security skill)crontab -l | grep -v 'amcp\|checkpoint\|watchdog' | crontab -
security skill
A further 1 matches are quotations in this security skill's documentation and are not counted as findings.
Files scanned: 58. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
description-no-whendescription does not say WHEN to use the skill (no "use when") - warning
missing-refreference to a missing file: docs/WATCHDOG-RECOVERY.md - note
frontmatter-keyunknown frontmatter key "displayName" - note
frontmatter-keyunknown frontmatter key "triggers"
Process rating: all ten parameters 41/100
- 0Tools and files. 1 referenced file(s) missing: docs/WATCHDOG-RECOVERY.md
- 0Result and completion. Does not say what the result is
- 0Progress reporting. Says nothing while it works
- 20When it triggers. No condition that starts the skill
- 30Running it twice. 10 mutating operations with no state check
- 50Failures and branches. 0 branches, has a failure section
- 70Inputs and preconditions. Inputs and preconditions are listed
- 70Execution cost. Instruction body is 4372 tokens
- 85Steps. 30 steps, 1 vague phrases
- 100Consistency. Name and required fields are in place
- low 18 top-level sections: this looks like several domains in one skill
- low The response is described with custom markup (3 tags): a typed call is more reliable
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)
- +3Output format is not stated: the model decides each time
- -351 of 55 scripts are never mentioned in SKILL.md
- +1No license
- +2Single-language instructions
- +3Description length 146: enough signal without eating the budget
- +4Structure: 49 headings
- +3Step-by-step instructions: 30 items
- +4Has examples (29 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 61.