engineering / skill

GoLive

An Agent Skill and Node CLI for planning deployments of agent-built apps through your own hosting, database, domain, email and payment accounts.

Repository owner mikehasa

Not rated yet
0 comments

Like 0 Save

Published 11 Oct 2026Listing updated 12 Oct 2026

At a glance

Purpose: An Agent Skill and Node CLI for planning deployments of agent-built apps through your own hosting, database, domain, email and payment accounts.
Runs in: Local agent with shell
Operating systems: Not stated
Needs: Runtime: Node.js 20+, npm/npx and Git; Needs internet: Yes; Needs accounts or API keys beyond your agent: Yes
Files and data: Reads files: Yes; Writes files: Yes; Sends data to other services: Yes
Tool type: Skill
Delivery: From GitHub
Version: Latest on the main branch
Access: Code on GitHub
Compatibility: According to the README: Codex and Claude Code (it says installation has been checked for these, and other clients are unverified), and OpenClaw through ClawHub. It needs Node.js 20 or later. The paths it lists are hosting on Vercel or Netlify, databases on Supabase or Neon, DNS at Porkbun or GoDaddy, email through Resend and test-mode payments through Stripe.
External costs: The repository is MIT-licensed and states no pricing for GoLive itself. The providers it works with, such as Vercel, Netlify, Supabase, Neon, Porkbun, GoDaddy, Resend and Stripe, are used through your own accounts. The README's sample conversation has the agent show resource settings and cost information with the plan before you approve it. Your coding agent or model provider may charge for usage.
Permissions: The skill uses your agent's access and provider logins/API keys. The README describes hosting project, database, DNS, email domain/key, Stripe webhook and Supabase auth/test-account changes. The README says apply needs the approved plan ID and --yes; DNS writes need --confirm-dns, deletions --confirm-destroy and live-mode steps --confirm-live, including the first production deployment. The README warns that the agent passes confirmation flags on your behalf. The README describes teardown deletions and irreversible removal of stored credential entries. The README says removing a stored entry does not end provider access; the token must be revoked at the provider. The README says keys are stored in ~/.config/golive/credentials as plaintext at mode 0600, readable by anything running as your user. The README warns that an agent already logged in to a provider can make changes there without a GoLive plan.
Usage terms: MIT License, as stated in the repository. See its LICENSE file for the exact terms.

Code on GitHub

mikehasa/golive-skill

MIT

TypeScript1,277 stars95 forksLast pushed 11 Oct 2026 UTC

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.

Topics: agent-skill agent-skills ai-agents claude-code cloudflare codex database deployment

Public GitHub data fetched 13 Oct 2026 UTC · 0 days old

Skill folders in this repository (1)

Folders that contain a SKILL.md file, from GitHub's file list on 13 Oct 2026 UTC.

skills/golive

View on GitHub ↗

What it does

GoLive is an Agent Skill with a Node command-line tool for deploying an agent-built app through your own provider accounts. The README describes detecting app requirements, planning changes, requesting approval, applying them with provider logins and running its verify command. The README also describes resource records, on-demand drift checks and teardown with ownership checks and handoffs for resources it cannot remove.

The README lists hosting on Vercel or Netlify, databases on Supabase or Neon, DNS at Porkbun or GoDaddy, Resend email, Stripe test-mode payments and Supabase authentication. The README labels the release early alpha and distinguishes disposable live-run evidence from mock coverage and experimental adapters.

The README says apply requires a plan ID and explicit confirmation, with additional gates for DNS, deletions and live-mode steps including a project's first production deployment. The README warns that an agent already logged in to a provider can write outside GoLive's plan flow. The README says GoLive has no account, hosted backend or product telemetry.

Who it is for

Developers who build apps with a coding agent and want help moving them onto hosting, database, domain, email and payment providers using their own accounts.

Example tasks

Ask your agent to take an app live and keep the providers it already uses.
Ask to see the destination accounts and the plan before any provider change.
Ask your agent to set up Vercel or Netlify hosting with a Supabase or Neon database.
Ask your agent to attach a custom domain, with DNS records written at Porkbun or GoDaddy after you approve them.
Ask your agent to plan the removal of a test project with golive teardown.

Getting started

The README gives three install routes. The main route uses the Skills CLI: npx skills add, pointing at the repository, with --skill golive and --global, and you pick your agent when prompted. It also gives per-agent versions of that command for Codex and Claude Code. The npm route is npx golive@alpha install --agent codex or npx golive@alpha install --agent claude. The ClawHub route for OpenClaw is npx clawhub@latest install golive. The README says installing does not connect accounts or deploy anything. If GoLive does not appear, reload skills or start a new session. Then type $golive in Codex or /golive in Claude Code, followed by a request. The README has the exact commands. The README's main Skills CLI command installs globally; omitting --global installs into one project. The README says npm targets the project or, with --global, ~/.agents/skills/golive or ~/.claude/skills/golive. The README's ClawHub command installs into ./skills and records the installation in .clawhub/lock.json. The README describes golive.yaml, .golive state/reports, GOLIVE_REPORT.md and handover writes. The README says its optional own installer supports whole-bundle updates and local rollback, with automatic replacement off by default; it advises updating between deployment runs, rather than between a plan and its apply.

Limitations

Needs Node.js 20 or later, npm/npx, Git and a coding agent that loads skills and runs commands. The README says installation was checked for Codex and Claude Code; other clients are unverified. The README describes macOS hidden-input key entry and an editor fallback on other platforms. You supply provider accounts and handle signups, browser logins, identity checks and purchases. The README labels the release early alpha and the Supabase Auth configuration, signup, password-recovery, account-isolation and Cloudflare DNS adapters experimental. The README marks PostHog analytics in progress / experimental: host environment writing, consent settings and the app's event flows remain open, and project creation/deletion has mock coverage only. The README says Cloudflare DNS and account isolation lack live validation, and its auth confirmation evidence used the admin API rather than an inbox click; inbox delivery and captcha remain human steps. The README says first-account setup and every framework have not been validated, cross-provider pairings have mock coverage, and other providers receive best-effort guidance. The README limits promotion and rollback to Netlify, describes them as opt-in and not live-validated, and excludes data, DNS, payment and email restoration. The README says teardown leaves Supabase/Neon projects, the Resend sending domain and other unremovable resources as manual handoffs. The repository can change at any time; check its README before you install.

Data practices

According to the README, GoLive has no account, hosted backend or product telemetry. The README describes credential processing in memory, fingerprints in execution records, and plaintext key storage at ~/.config/golive/credentials with mode 0600; the README warns that processes running as your user can read it. The README describes local state, reports and handover files containing account and resource metadata, and warns that this metadata can identify private resources when shared. The README describes provider API operations using your accounts and a synthetic-event check sent to PostHog. Your coding agent, providers and installer have their own data practices. The README says the PostHog ingest check sends one synthetic event and reads it back through PostHog's query API.