SKILLEMALL.ai
GitHub ↗ RU Sign in

FF three-shrimp-collab

(no description)

Not recommendedcritical or high security findings · low grade F
ClawHub Agent Skills author: 张洋 v1.0.0 MIT-0 17 files · 5 scripts body ≈ 1 143 tokens Open the sourceclawhub.ai↗ analyzed 3 d ago

As a process F 33/100 · Will not run — References files that are not bundled: scripts/com.openclaw.heartbeat.plist

ProcedureInfrastructuretype and topics are labelled automatically from the skill text
Runs in: OpenClaw Claude / Claude Code ChatGPT / Codex Gemini CLI Cursor GitHub Copilot / VS Code Qwen Code Kimi Code CLI Z.ai (GLM) DeepSeek (Deep Code) Mistral Vibe LangChain (deepagents) Goose OpenCode
JSON
Technical rating
F
0/100
safety, quality, tests
Safety 60%
0
Quality 40%
0
Run on models
none yet
Process rating
F
33/100
Will not run
References files that are not bundled: scripts/com.openclaw.heartbeat.plist
Tools and files w 18
0
Result and completion w 14
0
When it triggers w 12
0
the three weakest of ten parameters · all ten

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.

Dangerous commands
If you install

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.

For the author

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.

How to improve

  1. 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.
  2. Add a description to the frontmatter: without it the skill never triggers.
  3. The text references files that are not there: add them or drop the references.
For the model run — optional
  • 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 · 18

  • high Dangerous commands cmd-persistence docs/shrimp-heartbeat-config.md:39
    Persistence mechanism (cron / launchd / scheduled task / autorun registry)
    cat > ~/Library/LaunchAgents/com.openclaw.heartbeat.plist << 'EOF'
  • high Dangerous commands cmd-persistence docs/shrimp-heartbeat-config.md:94
    Persistence mechanism (cron / launchd / scheduled task / autorun registry)
    launchctl load ~/Library/LaunchAgents/com.openclaw.heartbeat.plist
  • high Dangerous commands cmd-persistence docs/shrimp-heartbeat-config.md:100
    Persistence mechanism (cron / launchd / scheduled task / autorun registry)
    launchctl unload ~/Library/LaunchAgents/com.openclaw.heartbeat.plist
  • high Dangerous commands cmd-persistence docs/shrimp-heartbeat-quickstart.md:180
    Persistence mechanism (cron / launchd / scheduled task / autorun registry)
    launchctl unload ~/Library/LaunchAgents/com.openclaw.heartbeat.plist
  • high Dangerous commands cmd-persistence docs/shrimp-heartbeat-quickstart.md:183
    Persistence mechanism (cron / launchd / scheduled task / autorun registry)
    launchctl load ~/Library/LaunchAgents/com.openclaw.heartbeat.plist
  • high Dangerous commands cmd-persistence install.sh:66
    Persistence mechanism (cron / launchd / scheduled task / autorun registry)
    launchctl load "$LAUNCH_AGENTS_DIR/com.openclaw.heartbeat.plist"
  • high Dangerous commands cmd-persistence install.sh:67
    Persistence mechanism (cron / launchd / scheduled task / autorun registry)
    launchctl load "$LAUNCH_AGENTS_DIR/com.openclaw.fswatch.plist"
  • high Dangerous commands cmd-persistence README.md:256
    Persistence mechanism (cron / launchd / scheduled task / autorun registry)
    launchctl unload ~/Library/LaunchAgents/com.openclaw.fswatch.plist
  • high Dangerous commands cmd-persistence README.md:257
    Persistence mechanism (cron / launchd / scheduled task / autorun registry)
    launchctl load ~/Library/LaunchAgents/com.openclaw.fswatch.plist
  • high Dangerous commands cmd-persistence scripts/setup-heartbeat.sh:40
    Persistence mechanism (cron / launchd / scheduled task / autorun registry)
    launchctl load "$LAUNCH_AGENTS_DIR/com.openclaw.heartbeat.plist"
  • high Dangerous commands cmd-persistence SKILL.md:43
    Persistence mechanism (cron / launchd / scheduled task / autorun registry)
    cp scripts/com.openclaw.heartbeat.plist ~/Library/LaunchAgents/
  • high Dangerous commands cmd-persistence SKILL.md:44
    Persistence mechanism (cron / launchd / scheduled task / autorun registry)
    launchctl load ~/Library/LaunchAgents/com.openclaw.heartbeat.plist
  • high Dangerous commands cmd-persistence SKILL.md:47
    Persistence mechanism (cron / launchd / scheduled task / autorun registry)
    cp scripts/com.openclaw.fswatch.plist ~/Library/LaunchAgents/
  • high Dangerous commands cmd-persistence SKILL.md:48
    Persistence mechanism (cron / launchd / scheduled task / autorun registry)
    launchctl load ~/Library/LaunchAgents/com.openclaw.fswatch.plist
  • high Dangerous commands cmd-persistence SKILL.md:277
    Persistence mechanism (cron / launchd / scheduled task / autorun registry)
    launchctl unload ~/Library/LaunchAgents/com.openclaw.fswatch.plist
Medium and low: 3
  • medium Dangerous commands cmd-persistence scripts/setup-heartbeat.sh:66
    Persistence mechanism (cron / launchd / scheduled task / autorun registry) (string literal in code, not executed)
    echo "  卸载服务：launchctl unload ~/Library/LaunchAgents/com.openclaw.heartbeat.plist"
    code literal
  • low Dangerous commands cmd-cron-mention docs/shrimp-heartbeat-config.md:111
    Mentions editing / listing crontab
    crontab -e
  • low Dangerous commands cmd-cron-mention docs/shrimp-heartbeat-config.md:174
    Mentions editing / listing crontab
    crontab -l

Files scanned: 17. Evidence is masked. Grey chips explain why severity was lowered.

Against the Agent Skills spec

  • error frontmatter SKILL.md: no YAML frontmatter block found
  • error name-missing SKILL.md: frontmatter has no `name`
  • error description-missing SKILL.md: no `description` — the skill can never trigger
  • warning missing-ref reference to a missing file: scripts/com.openclaw.heartbeat.plist

Process rating: all ten parameters 33/100

Will not run. References files that are not bundled: scripts/com.openclaw.heartbeat.plist
  • 0Tools and files. 1 referenced file(s) missing: scripts/com.openclaw.heartbeat.plist
  • 0Result and completion. Does not say what the result is
  • 0When it triggers. No condition that starts the skill
  • 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
  • 100Steps. 28 steps
  • 100Consistency. Name and required fields are in place
  • 100Execution cost. Instruction body is 1143 tokens
  • 100Running it twice. No mutating operations
  • low 13 top-level sections: this looks like several domains in one skill

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)
  • +3Description length 0: 120–800 characters recommended
  • +3Output format is not stated: the model decides each time
  • -226 emoji in the instructions: noise for the model
  • -49 reference files, but SKILL.md never points to them: the model will not open them
  • +1No license
  • +2Single-language instructions
  • +4Structure: 35 headings
  • +3Step-by-step instructions: 28 items
  • +4Has examples (17 code blocks)
  • +3All 4 scripts are documented

Quality base 70; lint remarks subtract, signals add up to 100. Result: 0.

External checks

ClawHub: suspicious
The skill’s collaboration automation is mostly coherent, but it asks users to enable persistent background monitoring and external task notifications with weak scoping and hard-coded local/recipient details.
LLM: suspicious (high) · VirusTotal: · 29 May 2026