golive-skill: GoLive: Open‑Source Agent Skill for Deploying Agent‑Built Apps
GoLive is an open‑source Node CLI that detects, plans, approves, applies, and verifies deployment steps for agent‑built applications, supporting hosting, databases, domains, email, and payments on the user’s own accounts. 1,183 GitHub stars in 9 days since mikehasa/golive-skill was created (128.1/day). 1 source acros
30Fact cited ·Analysis our interpretation ·Estimate forward-looking · [n] links to the source
3 claims drafted by openai/gpt-oss-20b were kept because each quote was found verbatim in its source; 4 unverifiable claims were discarded. Statements marked AI await human review.
What happened
- Fact It supports hosting on Vercel and Netlify[1]AI
hosting (Vercel, Netlify)
- Fact It supports databases on Supabase and Neon[1]AI
database (Supabase, Neon)
- Fact The GitHub repository mikehasa/golive-skill was created on 23 Sept 2026 and had 1,183 stars on 2 Oct 2026.[1]
- Fact Its description reads: “Take your agent-built product live: hosting, database, domain, email, payments — on your own accounts. Open-source Agent Skill + zero-dependency Node CLI: detect → plan → approve → apply → verify. No GoLive account, backend or telemetry.”[1]
- Fact That is 1,183 stars in 9 days, an average of 128.1 per day.[1]
Why it matters
- Analysis Use GoLive to detect required infrastructure, generate a plan, review and approve it, then apply the plan to provision resources on their own accounts, and verify the deploymentAI
- Analysis Automatically detected from public activity data. Not yet reviewed by an analyst.
Should I care?
What changed?
Who is affected?
- Analysis Developers building applications with coding agents who need to deploy to real cloud servicesAI
What can developers do with it?
- Analysis Use GoLive to detect required infrastructure, generate a plan, review and approve it, then apply the plan to provision resources on their own accounts, and verify the deploymentAI
Is it production-ready?
Insufficient evidence
Analysis Not assessed.
What would make it important?
Not yet assessed.
What could prevent adoption?
Not yet assessed.
Technical change
- Fact It supports hosting on Vercel and Netlify[1]AI
hosting (Vercel, Netlify)
- Fact It supports databases on Supabase and Neon[1]AI
database (Supabase, Neon)
Architecture
No architecture has been documented for this signal.
Developer impact
Developer implications have not been assessed yet.
Difficulty has not been estimated yet.
Adoption & momentum
No adoption indicators recorded.
Timeline
First seen by the Astrava pipeline[1]
Limitations & risks
- Fact Users must manually approve every write and provide confirmation flags for DNS, destroy, and live steps[1]AI
You still approve every write. Nothing reaches a real account without a plan you have seen and approved
- Analysis Generated from activity metrics only; verify the linked sources before acting on it.
Competing approaches
No competing approaches documented yet.
Who is building on it
No independent projects or organisations are documented as building on this yet.
Evidence & sources
Primary source (1)
Published by the people who built it: release notes, repositories, papers, official docs.
- [1]mikehasa/golive-skill repository(opens in a new tab)
Take your agent-built product live: hosting, database, domain, email, payments — on your own accounts. Open-source Agent Skill + zero-dependency Node CLI: detect → plan → approve → apply → verify. No GoLive account, backend or telemetry.
Secondary source (0)
Independent reporting, third-party benchmarks, integrations by other projects.
None recorded.
Community signal (0)
Discussion threads and social posts. Evidence of attention, not of correctness.
None recorded.
How the score of 30 was calculated
| Factor | Share of maximum | Points |
|---|---|---|
| NoveltyRubric level 2/4 (Moderate). Heuristic (automated): first published 9 days ago. | 7.5/15 | |
| Technical significanceNot yet assessed. Requires analyst review; not assessed automatically. | 0/15 | |
| Developer relevanceRubric level 1/4 (Low). Heuristic (automated): no installable package detected; developer-facing topic. | 3.8/15 | |
| Adoption velocityIndependent integrations: unknown (0 pts). GitHub stars: 128.1 per day since creation; full marks at 1000/day, log-scaled (3.5/5). | 3.5/10 | |
| Community momentumFewer than three periods of activity data, or no baseline activity to compare against. | 0/10 | |
| Source credibilityPrimary source present; mean source-tier weight 1.00 (primary 1.0, secondary 0.7, community 0.35). | 10/10 | |
| Cross-source confirmationNo independent publisher has confirmed this yet. | 0/10 | |
| Evidence strengthMet 2/4: primary source ✓, runnable artifact (code, weights or package) ✓, reproducible or independent benchmark ?, technical documentation or paper ✗. 1 unknown (scored 0). | 5/10 | |
| Time to impactNo time-to-impact estimate yet. | 0/5 | |
| Hype penaltyNo hype indicators detected. | 0 | |
| Breakout Score | 30 |
Low confidence (0.48) — 60% of measured factors have data. 0 independent non-community publishers. At least one primary source. Evidence strength 5/10. Capped at Low: no independent, non-community source yet.
An analytical ranking derived from observable signals using model breakout-v1.2. It is not a prediction and not a measure of quality. How it works