Skill flagged — suspicious patterns detected
ClawHub Security flagged this skill as suspicious. Review the scan results before using.
三只虾协作系统
v1.0.0三只虾协作系统是基于多agent的任务分配、实时监控和自动通知框架，支持角色分工和心跳检测，实现任务高效协同。
⭐ 0· 209·0 current·0 all-time
by张洋@ayangai
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 purpose (multi-agent task monitoring + notifications) matches the included scripts (fswatch monitor, heartbeat check, notify). However the package omits expected declarations: it requires fswatch and macOS launchctl usage but the registry metadata lists no required binaries or an OS restriction. Several files and plist templates hardcode paths under /Users/zhangyang, which is unrelated to a generic 'skill' installation and is unlikely to be correct for most users.
Instruction Scope
SKILL.md instructs copying and loading launchd plist files and running background monitors; the shipped scripts read and write workspace files (tasks/queue.md, MEMORY.md, logs/pending-notifications-*.md) and optionally post notifications to an external Feishu webhook. The runtime instructions and scripts are mostly within the stated purpose, but they instruct persistent system changes (adding LaunchAgents) and refer to files under a hardcoded /Users/zhangyang path — instructions do not tell the installer to update those paths to their environment.
Install Mechanism
There is no formal install spec in the registry (instruction-only), but the bundle includes install.sh and setup scripts that will modify the system: install.sh and setup-heartbeat.sh copy plist files into ~/Library/LaunchAgents and load them with launchctl. The plist templates themselves reference absolute /Users/zhangyang paths. Using these scripts will create persistent launchd services; that is coherent with the feature but the hardcoded paths and unconditional loading of launch agents are risky if run without inspection.
Credentials
The SKILL.md and scripts expect environment variables for Feishu notifications (FEISHU_WEBHOOK, FEISHU_USER_ID) and mention configuring them, but the skill metadata declares no required env. The notify script has a default hardcoded FEISHU_USER_ID and will POST to FEISHU_WEBHOOK if set — an external webhook endpoint that could receive notification content. The absence of explicit env declarations and the presence of a hardcoded user id are disproportionate and deserve attention.
Persistence & Privilege
The skill installs launchd agents (persistent background services) to run hourly and respond to fswatch events. Persistence is consistent with a heartbeat/monitoring feature, but the implementation will enable system-level background services and load them immediately. The package does not declare an OS restriction (it is macOS-specific) and uses hardcoded user paths, increasing the chance of accidental misconfiguration.
What to consider before installing
This package mostly does what its docs say (file-watching, hourly 'heartbeat', and auto-notify), but there are multiple red flags you should address before running install scripts: 1) Hardcoded paths: many scripts and the plist templates use /Users/zhangyang/.openclaw/... — change these to use $HOME or your own paths before installing. 2) Platform assumption: the code uses brew, fswatch, and macOS launchd; only install on macOS and ensure the OS field is appropriate. 3) Environment variables: the notify script may POST messages to FEISHU_WEBHOOK if set; confirm the webhook URL is correct and trusted. 4) Persistence: the installer copies plist files and loads them with launchctl (creating persistent background services). Inspect the plist ProgramArguments/WorkingDirectory/StdOut/StdErr entries before loading. 5) Minimal checks: the registry metadata does not list required binaries or env vars — treat that as incomplete documentation. Recommended steps: (a) review and edit all scripts (replace hardcoded user paths with $HOME), (b) inspect the plist files and adjust paths, (c) run scripts manually (dry-run) rather than running install.sh unmodified, (d) if you need to test, run in a disposable macOS account or VM, and (e) if you plan to enable notifications, use a dedicated webhook / test channel. If any of these items are surprising, ask the author to supply a macOS-specific install guide, or a version that parameterizes HOME and documents required env vars and binaries.Like a lobster shell, security has layers — review code before you run it.
agentvk97end079c4aq760jkpy2verjn82z8k0automationvk97end079c4aq760jkpy2verjn82z8k0collaborationvk97end079c4aq760jkpy2verjn82z8k0latestvk97end079c4aq760jkpy2verjn82z8k0pmovk97end079c4aq760jkpy2verjn82z8k0
License
MIT-0
Free to use, modify, and redistribute. No attribution required.