Set up analytics and tracking infrastructure for growth loops. Use when the user says "deploy telemetry", "set up analytics", "tracking", "events", "push to supabase", or "skene push".
Set up analytics infrastructure via the Skene CLI.
uvx skene push — it POSTs skene/engine.yaml, {output_dir}/feature-registry.json when present, and the latest trigger migration to Skene Cloud (it does not generate SQL; run uvx skene build first if artifacts are missing).Discover CLI options
Run uvx skene push --help to see available flags. Use only flags that appear in the output.
Verify prerequisites
skene/engine.yaml must exist; trigger SQL lives under supabase/migrations/ as *_skene_triggers.sql after uvx skene build (older projects may use legacy *skene_trigger* / *skene_telemetry* filenames).skene-context/feature-registry.json (or {output_dir} from config). If missing, push still runs but omits the registry until build creates it.uvx skene build first, then retry deploy.ls supabase/ 2>/dev/null — if missing: "No Supabase directory. Set up Supabase first."Ask user to confirm
Tell the user: "uvx skene push uploads engine, feature-registry.json (if present), and latest *_skene_triggers.sql to upstream. Proceed?"
Wait for confirmation.
Run push
After user confirms, run uvx skene push with appropriate flags from --help output.
Report which migration file was packaged (latest eligible under supabase/migrations/) and that upstream received the deploy.
Report result
Engine path, registry path (if packaged), trigger migration path, next step: apply DB migrations locally if needed (supabase db push), then "Run /skene-status to verify."
Privacy reminder (one line) "Remember GDPR/CCPA consent management before production tracking."
Deploy result (or error), paths used, next step (/skene-status).