Skill flagged — suspicious patterns detected
ClawHub Security flagged this skill as suspicious. Review the scan results before using.
Pilot Map Reduce
v1.0.0Distributed map-reduce over agent swarms for parallel data processing. Use this skill when: 1. You need to process large datasets across multiple workers 2....
⭐ 0· 47·0 current·0 all-time
byCalin Teodor@teoslayer
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
OpenClaw
Suspicious
medium confidencePurpose & Capability
Name/description align with the runtime instructions: all commands use pilotctl to discover peers, send messages, and collect results. The declared required binary (pilotctl) is appropriate. Dependencies list jq and sort which are used in the SKILL.md but are not declared as required binaries in the registry metadata (minor mismatch). The homepage and pilot-protocol dependency are consistent with a distributed agent framework.
Instruction Scope
Instructions instruct the agent to list peers, send messages, and read received messages via pilotctl — all within the stated purpose. However there are problematic gaps: the 'Shuffle and reduce' section reads MAP_RESULTS from /tmp/map-results-$JOB_ID.json but earlier collection uses pilotctl --json received (no step writes the /tmp file). The scripts also construct JSON payloads by embedding shell-expanded jq output which is fragile and may produce invalid JSON or accidentally include sensitive content. The SKILL.md assumes pilotctl daemon is running and accessible but doesn't explain authentication, config paths, or how messages are persisted, which affects security and data flow assumptions.
Install Mechanism
Instruction-only skill with no install spec and no code files — lowest-risk in terms of arbitrary code being written to disk. It does, however, require pilotctl and common CLI tools be present on PATH.
Credentials
No environment variables or credentials are requested by the registry metadata. That is reasonable for a CLI-driven skill, but pilotctl may itself rely on local config, sockets, or credentials (not declared here). The skill also references /tmp for temporary results (local filesystem access) and the agent network via pilotctl; you should verify pilotctl's configuration and any keys it uses before running.
Persistence & Privilege
The skill does not request always:true and does not modify other skills or system-wide settings. It runs commands at invocation time only. No elevated persistence behavior is present in the package itself.
What to consider before installing
This skill appears to implement a legitimate map-reduce pattern for the Pilot protocol, but there are gaps and fragile assumptions you should address before installing or running it:
- Verify pilotctl: install pilotctl from a trusted source (homepage or official releases) and inspect its config/credentials. The skill assumes a running pilotctl daemon but gives no guidance on auth or where credentials live.
- Resolve the /tmp inconsistency: the SKILL.md sometimes reads map results from pilotctl output and sometimes from /tmp/map-results-$JOB_ID.json — clarify which approach to use or add the step that writes the file. Running the provided scripts as-is may fail or silently process incomplete data.
- Test in a sandbox: run the workflow on a small, non-sensitive dataset and with a controlled set of worker peers to confirm message formats and persistence behavior.
- Watch for JSON injection/formatting issues: the scripts embed shell variables and jq output into JSON payloads; malformed payloads can break reducers or leak unexpected fields. Quote and validate JSON payloads before sending.
- Check data exposure risk: messages go to an agent swarm; ensure workers are trusted and that payloads do not contain secrets. Confirm how pilotctl persists or exposes received messages (logs, files, sockets).
- Validate dependencies and license: the SKILL.md names jq and sort as dependencies — ensure these are available. Note the AGPL-3.0 license and evaluate whether code snippets or derived work trigger obligations.
- Confirm provenance: the registry metadata owner and source are unknown; verify the pilotprotocol.network homepage and vulture-labs author identity if provenance matters.
If you cannot confirm pilotctl's configuration and the origin of this skill/tooling, treat it carefully and prefer isolated testing rather than deploying on production systems.Like a lobster shell, security has layers — review code before you run it.
latestvk972na03b8m28qb9xmjvv3c3wn84h19j
License
MIT-0
Free to use, modify, and redistribute. No attribution required.
Runtime requirements
Binspilotctl