Persona Consent Telegram (Hub)

Gates persona sharing behind explicit Telegram owner approval and connects to persona-service for external chatbots. Use when a user asks for persona, profil...

This skill appears to do what it says: it sends an approval request via a Telegram bot and only returns the persona file when you approve. Before installing, verify and do the following: 1) You must set TELEGRAM_BOT_TOKEN and TELEGRAM_OWNER_CHAT_ID (use a separate approval bot token as recommended), and set PERSONA_PATH and ALLOWED_PERSONA_PATH to the exact persona file you intend to allow; the registry metadata omits these—do not assume none are required. 2) If you enable persona-service mode, PERSONA_SERVICE_URL and PERSONA_CLIENT_ID (and optional shared secret) will cause the local persona-client to poll an external service and POST persona content after approval—ensure the service URL is trusted. 3) Inspect and understand scripts/request_persona.sh and scripts/persona_client.sh (they are small and included) and confirm TELEGRAM_API_BASE and PERSONA_SERVICE_URL are not set to untrusted hosts. 4) Prefer running the persona-client in the foreground for initial testing so you can observe behavior and logs; consider not using the wrapper until you trust its behavior. 5) Keep bot tokens private and rotate them if you publish any logs/screenshots. If you want stronger assurance, run the scripts in a restricted account or sandbox and review openclaw.json contents before the wrapper is allowed to read it.

Type: OpenClaw Skill Name: persona-consent-telegram-hub Version: 1.0.1 The skill implements a consent-based gateway for sharing persona files, requiring explicit approval via Telegram. It includes a background polling client (persona_client.sh) to handle requests from an external service and a validation script (request_persona.sh) that interacts with the Telegram Bot API. The code contains robust security controls, such as strict path validation in request_persona.sh (ensuring the requested file matches a pre-configured ALLOWED_PERSONA_PATH) and defensive instructions in SKILL.md to prevent the AI agent from bypassing the consent mechanism. All high-risk behaviors, such as background execution and external network communication, are transparently documented and directly aligned with the skill's stated purpose.