← ClaudeAtlas

verify-ef-synclisted

Read-only audit of all WorldCup 2026 Edge Functions, pg_cron jobs, and DB triggers. Verifies the data-sync + scheduling + notification pipeline is correctly wired for the real tournament and flags gaps (unmapped WC games, missing sync crons, leftover test data, stale EF versions). Use when the user says "verify EF", "check the sync", "audit edge functions", "are the crons ready for the World Cup", or before go-live.
ItayAvioz/2026-World-Cup-Social-Predicting-App · ★ 0 · AI & Automation · score 75
Install: claude install-skill ItayAvioz/2026-World-Cup-Social-Predicting-App
# Verify EF Sync — WorldCup 2026 Read-only audit of the backend pipeline: **5 Edge Functions + all pg_cron jobs + all DB triggers**. The goal is to confirm everything is wired for the *real* 2026 World Cup and report what must be added / fixed / cleaned before go-live. **This skill NEVER modifies anything.** No `apply_migration`, no `deploy_edge_function`, no `execute_sql` that writes, no `cron.schedule`/`cron.unschedule`. Inspect only, then write a report. Fixes are a separate, user-approved step. Project id: `ftryuvfdihmhlzvbpfeu` ## What to audit (go EF by EF) 1. **football-api-sync** — game scores, team/player stats, odds, fixture mapping 2. **sync-odds** — champion outright odds (TheOddsAPI) 3. **nightly-summary** — per-group AI roast (5-agent judge LLM) 4. **notify-admin** — admin email alerts + daily digest 5. **send-push** — Web Push delivery 6. **Crons + triggers** — every scheduling fn + AFTER-INSERT trigger that drives the EFs For the intended design, modes, triggers, and crons of each, read [ef-reference.md](ef-reference.md). ## Procedure 1. **Inventory live state** — `list_edge_functions` (capture deployed versions), then run the cron inventory + games-state queries from [checks.md](checks.md). 2. **Dispatch the diff agents** — for the deployed-vs-local comparison, run the 4 parallel subagents defined in [agents.md](agents.md) (football-api-sync, nightly-summary, the 3 small EFs, the DB trigger/cron layer). They keep the large deployed code out o