ClawHub
Skill flagged — suspicious patterns detected

ClawHub Security flagged this skill as suspicious. Review the scan results before using.

Naruto Multi-Agent CN

v1.5.0

Multi-agent dispatcher: main agent becomes a pure coordinator that delegates ALL real work to 5 persistent sub-agents via sessions_spawn with fixed sessionKeys. Round-robin scheduling, speak-before-spawn protocol, session reuse. Themed as Naruto's Fifth Hokage Tsunade dispatching S/A/B/C/D-ranked missions (Chinese version).

⭐ 1· 1.3k·1 current·1 all-time
byCLOUD BOY@be1human
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
VirusTotalVirusTotal
Suspicious
View report →
OpenClawOpenClaw
Benign
medium confidence
✓
Purpose & Capability
The name/description (multi-agent dispatcher) matches the SKILL.md: it instructs the main agent to coordinate and call sessions_spawn for five fixed sub-agents. No unrelated binaries, env vars, or installs are requested. The fields in skill.json are consistent with the claimed purpose.
ℹ
Instruction Scope
The runtime instructions are narrow and explicit: always speak first, then call sessions_spawn with a fixed set of sessionKey values and runTimeoutSeconds=300, and then produce no further output. The SKILL.md explicitly forbids exec/file I/O/search tools. This stays within the stated dispatcher purpose, but the 'stop talking after spawn' rule and multiple invisible tool calls reduce runtime transparency (users won't see intermediate tool calls), so you should confirm how the platform surfaces sub-agent outputs and logs.
✓
Install Mechanism
Instruction-only skill with no install spec and no code files — nothing is written to disk or downloaded during install. This is the lowest-risk install profile.
✓
Credentials
The skill requests no environment variables, no credentials, and no config paths. The declared requirements are proportional to its stated functionality.
ℹ
Persistence & Privilege
The core behavior depends on persistent session reuse via fixed sessionKeys (鸣人/卡卡西/鹿丸/小樱/佐井). That is coherent for a stateful dispatcher, but it means sub-agents can accumulate long-lived memory/state across tasks. Combined with the 'stop output after spawn' practice, this can reduce visibility into what persistent sub-agents store or do. The skill is not always:true and does not request extra privileges, but you should be aware of persistent-session privacy implications.
Assessment
This skill is coherent for a roleplay multi-agent dispatcher and contains only prose instructions (no installs, no requested secrets). Before enabling it, consider: 1) Session persistence: the five fixed sessionKeys create long-lived sub-agents that can accumulate memory—if you care about sensitive data, limit what you send to them. 2) Transparency: the skill instructs the coordinator to 'stop talking after spawn' and perform multiple sessions_spawn calls; check how your platform exposes sub-agent outputs/logs so you can audit what happened. 3) Source and provenance: the skill has no clear homepage/source and is user-contributed; if you need stronger assurance, ask the author for provenance or test in a controlled environment. If you accept those trade-offs, the skill appears to do what it says and doesn't require extra credentials or installs.

Like a lobster shell, security has layers — review code before you run it.

latestvk97egfdeqfcztp1bvmnfby4r75811x3n

License

MIT-0
Free to use, modify, and redistribute. No attribution required.
Termshttps://spdx.org/licenses/MIT-0.html

Comments