DEDUPED Hot AI repos, turned into use cases Get 5 a day

How to install GoLive into an OpenClaw workspace with Golive Skill

Add the skill to a project's skills folder through ClawHub and keep it updated there.

Who it is forAn OpenClaw user who keeps projects in a workspace and wants GoLive managed by the ClawHub registry.

The problemInstalling into a global agent folder is the wrong fit when the workspace should carry its own copy of the skill.

The outcomeThe golive skill sits in the workspace's skills folder, recorded in the ClawHub lock file, and later updates come from ClawHub.

What you need first

  • Node.js 20+, npm/npx and Git installed
  • A coding agent that can load skills and run commands (README checks Codex and Claude Code)
  • Accounts you own with the providers you plan to use, such as Vercel, Supabase, Netlify, Neon, Porkbun, GoDaddy, Resend or Stripe
  • Logins for those providers in a terminal you control, since the agent relies on them

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 for your agent

In the workspace <workspace-path>, 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.

Share: X LinkedIn Hacker News Email Copy link

Disclaimer

Deduped lists open-source repositories that belong to other people. We do not own, maintain, audit, or vouch for any of them, and a repo appearing here is not an endorsement or a safety check. The use cases, steps, and prompts are written by AI and may be incomplete, outdated, or just wrong. Where a use case is marked "Seen in the wild", we link to public posts where someone described something similar, but we have not verified those posts and the use case itself is still our AI's own write-up. Use all of this at your own risk. Only run code, commands, or agents on systems and accounts you are authorized to use, and read the code and every command before you run it, especially anything that touches credentials, files, or the network. Nothing here is professional, security, legal, or financial advice. All trademarks and project names belong to their respective owners, and their use here does not imply affiliation. Content is provided as is, without warranties of any kind. Found a mistake, a safety problem, or something you want removed? Email [email protected] and we will look at it promptly. Full disclaimer page