What problem does it solve? Setting up a personal briefing assistant that reads private habit and schedule data and delivers recurring summaries requires careful handling of credentials, user identity binding, and delivery authorization. This Skill guides the safe design and launch of such an assistant without leaking tokens or trusting unverified user identities. ## Core Features & Use Cases - Channel Bot Setup: Walks through Telegram BotFather or Discord Developer Portal bot creation with least-privilege permissions and secure token storage. - Private Data Model: Provides an idempotent Supabase schema with row-level security policies for channel bindings, habits, and briefings. - Authorization Boundary: Enforces server-side channel-to-user binding resolution so incoming messages can never spoof a user_id. - Briefing Contract & Scheduling: Defines an approved briefing contract, dry-run testing, idempotent scheduling, and an off switch. - Use Case: A user wants a daily Telegram briefing summarizing their habits and schedule. The Skill guides bot creation, database setup with RLS, contract approval, dry-run testing, and safe scheduled delivery. ## Quick Start Use the life-engine-setup skill to set up a recurring personal briefing assistant delivered to my Telegram account.
