What problem does it solve? Deploying Supabase Edge Functions and database migrations to Lovable projects requires choosing between MCP, browser, and manual transports while respecting authorization rules, credit costs, and verification steps. This Skill encodes that decision logic so agents deploy backend work correctly without wasting Lovable credits or skipping confirmations. ## Core Features & Use Cases - Transport selection: Chooses between browser automation, the official Lovable MCP server, or a manual prompt based on deploy.mode configuration. - YOLO authorization policy: Reads deploy.yolo_mode from .lovable-agent/config.json to determine whether Lovable prompts can be submitted without repeated user confirmation. - Deployment verification: Distinguishes accepted from verified deployments, classifies MCP failures, and falls back to browser inspection instead of charged status prompts. - Use Case: After writing a Supabase Edge Function locally, ask your agent to deploy it; the Skill checks GitHub sync, scans for missing secret names, consolidates operations into one prompt, submits it through the configured transport, and verifies the result. ## Quick Start Deploy my Supabase Edge Function and pending database migrations to my Lovable project using the configured transport.