Persona Channel Builder
PassAudited by ClawScan on May 10, 2026.
Overview
This instruction-only skill is purpose-aligned for creating an autonomous Telegram posting agent, but users should review the generated cron job, bot permissions, and persistent files before enabling public posts.
This looks safe to install if you want an autonomous Telegram channel builder. Before deploying, review the generated SOUL.md, CHANNEL.md, cron prompt, schedule, and channel ID; use a least-privileged Telegram bot; keep the bot token out of chat; and test with the job disabled or in a private channel first.
Findings (4)
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.
If enabled, the agent can publish posts to the selected Telegram channel without per-post human review.
The generated scheduled prompt instructs an agent to publish to Telegram, which is a public/account-impacting action. It is scoped to a user-provided channel and aligned with the skill's purpose.
"Write and publish one post to Telegram channel [channel_id]. Follow all rules in CHANNEL.md. Update memory/published_topics.md with the topic. Do not write to any other chat."
Review the generated prompt, channel ID, and sample posts carefully before enabling; consider testing with a private channel first.
A configured Telegram bot token can allow posting to channels where the bot has permission.
The skill acknowledges that Telegram deployment requires a bot token, but directs users to configure it outside chat rather than disclosing it to the agent.
Never ask the user to paste their bot token in chat. Tell them: "Don't share your bot token here — add it directly to openclaw.json on your server."
Use a dedicated Telegram bot with access only to the intended channel, and never paste the token into chat.
Incorrect or unwanted content in SOUL.md, CHANNEL.md, or the memory file could affect future Telegram posts.
The future cron job relies on persistent workspace files and memory to guide later posts. This is expected, but those files become influential context.
"Read SOUL.md and CHANNEL.md from workspace... Update memory/published_topics.md with the topic."
Review generated files before enabling the cron job and keep secrets or unrelated instructions out of these persistent files.
Once pasted and enabled, the job may continue posting on its schedule until the user disables or edits it.
The generated configuration creates recurring autonomous execution. It is visible and purpose-aligned, but persistent automation deserves user attention.
"enabled": true, "schedule": "[cron expression based on frequency and timezone]", "wakeMode": "now", "delivery": { "mode": "silent" }Set the job to disabled until tested, document how to turn it off, and monitor the first scheduled runs.