mission-control-cloudlisted

Add a cloud data layer and a hosted, login-protected dashboard to an existing or planned Mission Control so it's reachable from a phone or any device with the laptop closed. This is an OPTIONAL add-on layer that sits on top of `mission-control-blueprint` (which builds the local-first system) — use it only when you or a client specifically wants MOBILE / phone / remote / always-on access, since many builds are perfectly fine local-only. Triggers: "make the mission control mobile", "access it on my phone", "the client wants it on their phone", "put the dashboard in the cloud", "reach it when the laptop is off", "always-on dashboard", "host the mission control dashboard", "remote access to mission control". Produces a cloud add-on packet: the Supabase table + RLS migration, a configured Supabase-backed dashboard, the Cowork write-step that mirrors each refresh to Supabase, and a free static-host deploy checklist — plus a short client-facing privacy note. Use even if they don't say "skill" or "cloud" explicitly.
mikeleewoodai/mission-control · ★ 0 · DevOps & Infrastructure · score 70

Install: claude install-skill mikeleewoodai/mission-control

# Mission Control — Cloud Add-on Layer a **cloud data layer + hosted dashboard** onto a Mission Control so it's reachable from a phone or any device **with the laptop closed**. This is an **optional add-on** to `mission-control-blueprint`, not a replacement: the base skill builds the local-first system; this one makes it remotely accessible when that's actually wanted. **Use this only when mobile / always-on access is a real requirement.** Many clients are happy local- only. And if "from my phone" just means "while my machine is on," the lighter answer is a **Cloudflare Tunnel or Tailscale** over the existing local server — no re-architecture, free, nothing to host. Reach for this skill when the dashboard must be live **independent of the laptop**. ## What changes (and what doesn't) The **data schemas are identical** to the base build — only *where* the data lives and *how* the dashboard reads it change. | | Base (local) | With this add-on (cloud) | |---|---|---| | Data layer | local JSON/MD files | rows in Supabase `mc_documents` (key = filename, payload = the JSON) | | Dashboard | served folder (`dashboard.html`) | hosted `dashboard-cloud.html`, Supabase login | | Reads | `fetch()` relative paths | Supabase REST, `authenticated` only (RLS) | | Writes | refresh writes local files | refresh ALSO upserts to Supabase (local stays primary) | | Hosting | `python -m http.server` | Vercel / Cloudflare Pages (free static, HTTPS) | | Cost | none | Supabase free tier + free stati