Multi-Agent Create

Create new OpenClaw agents and connect them to messaging channels (Telegram, Discord, Slack, Feishu, WhatsApp, Signal, Google Chat). Includes workspace scaff...

This skill mostly does what it says, but there are gaps and some risky instructions you should consider before installing: - Do not paste bot tokens, app secrets, or service-account JSON contents into a chat with the agent unless you understand and accept that those values may be stored in conversation history or memory. Prefer using the CLI or editing openclaw.json directly with proper file permissions. - The helper script creates workspaces and calls 'openclaw agents add' but does not actually write channel account entries into openclaw.json. Expect to manually update your gateway config (openclaw.json) with channel credentials and bindings, and inspect the backup file the script creates before applying changes. - When asked for a filesystem path to a service account JSON, avoid sending the file contents over chat. If the agent needs the file, ensure the file is accessible only to trusted processes and consider performing configuration locally via the CLI instead of handing paths/contents to the agent. - The skill owner is unknown and there is no homepage; if you plan to use this in production, review the openclaw.json edits you make, verify who will have access to stored tokens, and prefer manual credential provisioning or secure secret storage (vaults) over pasting secrets into chat. If you can get answers to these: where channel credentials are stored after you paste them, whether the agent will persist secrets to disk, and an explicit step-by-step for how openclaw.json is modified, that would raise confidence.

Type: OpenClaw Skill Name: multi-agent-create Version: 1.1.0 The skill 'multi-agent-create' facilitates the setup of new AI agents and the collection of sensitive messaging platform credentials (e.g., Telegram tokens, Slack secrets). It utilizes shell execution via a local script (`scripts/setup-agent.sh`) and the `openclaw` CLI to perform file system operations, such as creating workspaces and backing up configurations. While these actions are directly aligned with the stated purpose and no evidence of intentional malice or data exfiltration was found, the use of shell/file access and the handling of high-value secrets meet the threshold for a 'suspicious' classification under the provided security guidelines.