# AI use cases for Golive Skill (mikehasa/golive-skill) Repo: [mikehasa/golive-skill](https://github.com/mikehasa/golive-skill) | Use cases: 4 | Page: https://dedupedai.com/use-cases/mikehasa-golive-skill/ GoLive is an open-source Agent Skill and zero-dependency Node CLI that takes an agent-built app live on the user's own hosting, database, domain, email and payment accounts, with approval steps before any change. This file holds every use case of this repo. Each one starts with a "## " heading and ends with its URL. - Take an agent-built app live on your own accounts: https://dedupedai.com/use-cases/mikehasa-golive-skill/take-agent-app-live-on-own-accounts/ - Tear down a test launch and list what remains: https://dedupedai.com/use-cases/mikehasa-golive-skill/hand-over-or-tear-down-test-launch/ - Connect a custom domain and transactional email: https://dedupedai.com/use-cases/mikehasa-golive-skill/connect-custom-domain-and-transactional-email/ - Install GoLive into an OpenClaw workspace: https://dedupedai.com/use-cases/mikehasa-golive-skill/install-golive-into-openclaw-workspace/ ## How to take an agent-built app live on your own accounts with Golive Skill Repo: [mikehasa/golive-skill](https://github.com/mikehasa/golive-skill) | Difficulty: Intermediate | Time: 60 minutes | Basis: From the README Detect what the app needs, approve a plan, and deploy it to your Vercel and Supabase accounts. **Who it is for:** A developer whose coding agent has finished an app repo and who needs it on real hosting and a database without setting up each service by hand. **The problem:** Getting an agent-built app to real users still means creating accounts, hosting, databases, secrets and connected services, and it is easy to skip an approval or leave something misconfigured. **The outcome:** The app runs on hosting and a database in the user's own accounts, with a recorded plan the user approved and a verification report of what works. ### Steps 1. Install the skill for all projects: `npx skills add https://github.com/mikehasa/golive-skill --skill golive --global` 2. Open the app repository in your coding agent and reload skills or start a new session if golive does not appear. 3. Ask in chat: `Use the golive skill to take this app live. Keep the providers it already uses.` Choose Vercel when asked for hosting. 4. Log in to each provider in a separate terminal with `vercel login` and `supabase login`, then tell the agent you are done. 5. Read the plan the agent shows, including destination accounts, names and cost information, and approve it only if it matches what you expect. ### Prompt to paste into your agent ```text Use the golive skill in the repo to detect what this app needs, then present the destination accounts and plan for Vercel hosting with Supabase before changing anything. After approval, report the live URL and the verification result, and confirm that the Vercel team and Supabase organization shown in the plan match the accounts I named. ``` ### Caveat The README marks this as early alpha, and Vercel has no rollback, so production fixes on Vercel are made in its dashboard. Risk, credentials: The agent works through your provider logins, and golive stores credential values in a plaintext file at mode 0600 outside your repo, not in a keychain. Disclaimer: Third-party repos we don't own or vouch for. AI-generated use cases can be wrong: review everything and run at your own risk. Full text: https://dedupedai.com/disclaimer/ URL: https://dedupedai.com/use-cases/mikehasa-golive-skill/take-agent-app-live-on-own-accounts/ ## How to tear down a test launch and list what remains with Golive Skill Repo: [mikehasa/golive-skill](https://github.com/mikehasa/golive-skill) | Difficulty: Intermediate | Time: 30 minutes | Basis: From the README Remove the resources golive created, then get a handoff for anything it cannot delete. **Who it is for:** A developer who finished a test run with disposable provider resources and does not want leftover hosting, databases or DNS records billing them. **The problem:** Test resources are easy to forget, and an agent can leave some behind when a provider does not allow automatic removal. **The outcome:** Resources golive can prove it created are removed, and a clear list names each leftover with steps to remove it by hand. ### Steps 1. Ask the agent in chat to tear down the golive resources from this app, and review the plan it shows before approving. 2. Run `npx golive@alpha teardown` from the installed skill to start the removal path. (inferred, check the README) 3. Read the handoff list for Supabase and Neon projects, the Resend sending domain, and any zone or host project golive could not read. 4. Remove each listed leftover by hand in its provider dashboard. 5. Run `npx golive@alpha status` to confirm the baseline is clear of golive-created drift. (inferred, check the README) ### Prompt to paste into your agent ```text Use the golive skill in the repo to tear down only the resources golive created for this app, and show the plan before any deletion. Report the handoff list of leftovers that golive could not remove, and confirm the removal of the test host project. ``` ### Caveat Teardown does not remove Supabase and Neon projects or the Resend sending domain automatically, so those must be deleted by hand from the handoff list. Disclaimer: Third-party repos we don't own or vouch for. AI-generated use cases can be wrong: review everything and run at your own risk. Full text: https://dedupedai.com/disclaimer/ URL: https://dedupedai.com/use-cases/mikehasa-golive-skill/hand-over-or-tear-down-test-launch/ ## How to connect a custom domain and transactional email with Golive Skill Repo: [mikehasa/golive-skill](https://github.com/mikehasa/golive-skill) | Difficulty: Advanced | Time: 90 minutes | Basis: From the README Point a domain you own at the live app and set up sending through Resend. **Who it is for:** A founder whose app already runs on a test URL and who needs a real domain and email that the user's own DNS provider controls. **The problem:** DNS and email settings are easy to get wrong by hand, and a DNS change can affect other services on the domain. **The outcome:** The domain resolves to the live app, transactional email is sent through Resend, and the agent reports what was changed and what still needs a human. ### Steps 1. Confirm the domain is registered with Porkbun or GoDaddy, the two DNS providers this project lists for custom-domain DNS. 2. Ask the agent in chat to add the domain and Resend email, and review the DNS changes in the plan. 3. Approve the DNS writes only after the plan names the zone and records you expect, since DNS writes need explicit confirmation. 4. Send a test transactional email from the app and check that it arrives. 5. Ask the agent to report anything golive could not verify, so you can finish those steps yourself. ### Prompt to paste into your agent ```text Use the golive skill in the repo to plan a custom domain DNS change through Porkbun or GoDaddy and transactional email through Resend. Show the zone and each record in the plan before any write, then report what was applied and what remains manual. ``` ### Caveat The README names Porkbun, GoDaddy and Resend as covered in disposable live tests, and the broader roadmap is direction, not a claim that everything is built. Risk, credentials: The agent needs your DNS and email provider credentials, which golive reads in-process and stores in a plaintext file at mode 0600 outside your repo. Disclaimer: Third-party repos we don't own or vouch for. AI-generated use cases can be wrong: review everything and run at your own risk. Full text: https://dedupedai.com/disclaimer/ URL: https://dedupedai.com/use-cases/mikehasa-golive-skill/connect-custom-domain-and-transactional-email/ ## How to install GoLive into an OpenClaw workspace with Golive Skill Repo: [mikehasa/golive-skill](https://github.com/mikehasa/golive-skill) | Difficulty: Beginner | Time: 15 minutes | Basis: From the README Add the skill to a project's skills folder through ClawHub and keep it updated there. **Who it is for:** An OpenClaw user who keeps projects in a workspace and wants GoLive managed by the ClawHub registry. **The problem:** Installing into a global agent folder is the wrong fit when the workspace should carry its own copy of the skill. **The outcome:** The golive skill sits in the workspace's skills folder, recorded in the ClawHub lock file, and later updates come from ClawHub. ### Steps 1. Open the OpenClaw workspace directory in a terminal. 2. Run `npx clawhub@latest install golive` to install into ./skills. 3. Check that the install is recorded in .clawhub/lock.json. 4. Run `npx clawhub@latest update golive` when you want later updates. 5. Start a new agent session so the skill loads, then ask it to take an app live. ### Prompt to paste into your agent ```text In the workspace , install the golive skill from ClawHub and confirm that .clawhub/lock.json records it. Report the installed skill path and stop before connecting any provider account. ``` ### Caveat ClawHub installs into ./skills rather than an agent's global folder, and the README verifies only Codex and Claude Code through the other two channels. Disclaimer: Third-party repos we don't own or vouch for. AI-generated use cases can be wrong: review everything and run at your own risk. Full text: https://dedupedai.com/disclaimer/ URL: https://dedupedai.com/use-cases/mikehasa-golive-skill/install-golive-into-openclaw-workspace/