OpenClaw Agent Creator
AdvisoryAudited by Static analysis on Apr 30, 2026.
Overview
No suspicious patterns detected.
Findings (0)
Artifact-based informational review of SKILL.md, metadata, install specs, static scan signals, and capability signals. ClawScan does not execute the skill or run runtime probes.
A mistaken edit or restart could break routing, cron jobs, or agent availability.
The skill instructs local service control and direct edits to core OpenClaw configuration. This is expected for an agent-creation skill, and it includes backup/stop guidance, but misuse could disrupt the live agent system.
`openclaw gateway stop` ... `MANDATORY before editing openclaw.json or cron/jobs.json` ... `openclaw gateway start`
Use only after an explicit request, keep the backup step, review config diffs before restart, and verify logs after changes.
Scheduled agents may keep posting or consuming model/API resources until the cron jobs are disabled.
The skill can create scheduled autonomous agent tasks that continue running and can send Telegram messages. This is disclosed and central to the stated purpose, but it is persistent behavior.
Create Cron Jobs (if needed) ... Edit `cron/jobs.json`. Every cron job prompt MUST include ... Delivery instructions: use `target='<AGENT_GROUP_ID>'`
Create cron jobs only when explicitly requested, document their schedules, use clear timeouts, and know how to disable or remove them.
Private notes or bad instructions saved in memory could influence future agent behavior.
The generated agent template uses persistent memory files and instructs agents to reuse that context across sessions. This is purpose-aligned, but stored memories can contain sensitive or behavior-shaping information.
Read `memory/YYYY-MM-DD.md` ... Also read `MEMORY.md` ... Capture what matters. Decisions, context, things to remember. Skip the secrets unless asked to keep them.
Keep memory files scoped to each agent, avoid storing secrets, and periodically review or clean persistent memories.
Wrong bindings or group settings could make the wrong agent handle Telegram messages.
The skill changes routing for a shared Telegram bot, which effectively grants selected agents authority to read/respond in configured chats. This matches the purpose but crosses a permission boundary.
One Telegram bot shared across all agents — routing determines which agent handles which chat
Only add groups and bindings the user has approved, keep `requireMention` behavior intentional, and test routing after restart.
The skill may fail or behave unexpectedly if the expected local OpenClaw environment is not present.
The registry metadata under-declares the local environment needs relative to the instructions, which use OpenClaw CLI commands, `jq`, and files under `~/.openclaw/`. This is a metadata completeness issue, not evidence of malicious behavior.
Required binaries (all must exist): none ... Required config paths: none
Before use, confirm `openclaw`, `jq`, and the intended `~/.openclaw/` configuration exist and belong to the expected user.