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 enforces owner consent before sharing persona content. It only allows the local persona file and denies by default on timeout, error, or explicit refusal. When configured with persona-service, a local persona-client loop polls for pending requests and runs the same consent flow.
Use this skill when a requester asks for:
scripts/request_persona.sh first."allowed": true."allowed": false or script errors, reply exactly with author did not authorize.PERSONA_PATH after script path validation passes.Run from this skill directory:
bash "{baseDir}/scripts/request_persona.sh" "<requester_id>" "<reason>"
Interpret response:
{"allowed":true,"persona_md":"..."}persona_md content{"allowed":false,"message":"author did not authorize"}author did not authorizerequester_id: sender/user ID if available, otherwise unknown.reason: short explanation of why persona was requested.When PERSONA_SERVICE_URL and PERSONA_CLIENT_ID are set in this skill's env, a persona-client loop can run (via the provided wrapper or future OpenClaw hook) to poll persona-service and handle pending requests using this same consent flow.
ZIP package — ready to use