Parallel Responder

并行回复助手 - 让 AI 回复不再等待。支持任务分类、时间预估、并行执行、进度汇报。 简单任务直接回复，中等任务执行 + 汇报，复杂任务启动子 agent 并行处理。 Parallel Responder - Zero-wait AI responses. Task classification, time e...

This skill appears to be a reasonable orchestrator conceptually, but there are important mismatches between what the docs promise and what the code actually does. Before installing or enabling it: 1) Ask the author to explain and show the exact implementation for spawning sub‑agents and for progress reporting (what platform APIs are called and what permissions are required). 2) Confirm where results are stored (the README example shows /root/openclaw/… — that implies filesystem writes and elevated access). 3) Require the skill to declare any required env vars/credentials or platform capabilities (sessions_spawn, sessions_send) and provide safe defaults or opt-in consent for persistent storage and learning. 4) If you run it, do so in a sandboxed environment first because the documented behavior (starting child agents, saving files) could enable broader access than the in‑memory stubs suggest. If the author provides a clarified integration plan showing no external or privileged side effects, the inconsistencies would be resolved; until then treat the skill with caution.

Type: OpenClaw Skill Name: parallel-responder Version: 1.0.0 The skill is classified as suspicious due to its reliance on the OpenClaw platform's `sessions_spawn` mechanism, as described in `SKILL.md` and implemented in `scripts/parallel-executor.js`. This feature allows the skill to launch 'sub-agents' and pass user messages to them for 'complex tasks'. While `sessions_spawn` is an intended platform capability, passing user-controlled input to dynamically spawned agents without explicit sanitization or strict sandboxing creates a significant attack surface, potentially leading to Remote Code Execution (RCE) if the sub-agents are vulnerable to prompt or command injection. There is no direct evidence of intentional malicious behavior within the provided files, but the high-risk delegation mechanism warrants a 'suspicious' classification.