Skip to content

mikehasa/golive-skill / skills/golive

golive

Flagged

Take an agent-written app from repo to live production on the user's OWN accounts, with providers they choose (hosting, database, auth, payments, email, domain/DNS). The human connects accounts and approves changes; supported wiring operations run through a local CLI and produce verification evidence with explicit limits. Use when the user wants to ship, deploy, go live, launch, publish, or put their app online, or asks to wire up env vars, webhooks, auth settings (signup, email confirmation, password policy), a real signup → confirmation email → login journey, password recovery, account isolation between two users, auth redirects, email DNS or a custom domain.

FileKindSize
LICENSEother1.0 KB
SKILL.mdskill md50.0 KB
THIRD_PARTY_NOTICES.mdmarkdown817 B
references/cloudflare-dns.mdmarkdown7.9 KB
references/godaddy.mdmarkdown3.9 KB
references/guided.mdmarkdown9.2 KB
references/neon.mdmarkdown4.4 KB
references/netlify.mdmarkdown6.9 KB
references/plan-and-verify.mdmarkdown47.4 KB
references/porkbun.mdmarkdown3.4 KB
references/posthog.mdmarkdown10.2 KB
references/resend.mdmarkdown8.6 KB
references/sentry.mdmarkdown10.7 KB
references/stripe.mdmarkdown13.1 KB
references/supabase.mdmarkdown49.7 KB
references/troubleshooting.mdmarkdown5.2 KB
references/updates.mdmarkdown5.0 KB
references/uptimerobot.mdmarkdown12.3 KB
references/vercel.mdmarkdown13.2 KB
release.jsonconfig2.4 KB
scripts/golive.mjsscript1.2 MB
scripts/install-cli.mjsscript5.0 KB
scripts/install-lib.mjsscript24.4 KB

references/godaddy.md

View on GitHub
# GoDaddy DNS

Automated DNS-record adapter with two transports — same endpoints and safety rules either way: the
official GoDaddy CLI (`gddy`, the default when installed and logged in) and a scoped REST Personal
Access Token (the fallback). The Vercel-attached custom-domain journey passed disposable live runs
on both transports: the CLI path created both records through `gddy api call` with the user's OAuth
session, and the v3 update-by-ID (PUT) endpoint was separately validated through that same session.
golive's owned-record update flows (SPF merge, singleton replace, TTL drift) and the REST
update-by-ID path remain mock-covered. The GoDaddy MCP cannot modify DNS.

1. Use `dns=godaddy` only when the domain's **authoritative DNS** is hosted at GoDaddy. Buying a
   domain there is not enough if its nameservers point elsewhere. golive checks public delegation and
   zone access, including subdomain delegations; it never changes nameservers.
2. Preferred sign-in: install the official CLI and log in once. That installer is GoDaddy's own,
   published on their release page —
   `curl -fsSL https://github.com/godaddy/cli/releases/latest/download/install.sh | bash` — and the
   **human runs it in their own terminal**: never pipe a vendor script into a shell on their behalf.
   They may install `gddy` by their own route instead (download and inspect that script, or a package
   manager), because golive only needs it on PATH. Then
   `gddy auth login -s domains.dns:update` in the human's terminal (browser OAuth; the session stays
   in the CLI's own store, never in chat, arguments or golive's files). Include `domains.dns:update`
   from the start: in a non-interactive run gddy does not prompt for the scope, and a write without
   it fails with HTTP 403 (whose message names this command).
3. Fallback when the CLI is unavailable (headless hosts, no extra binary): have the human create a
   Personal Access Token at `developer.godaddy.com` with `domains.domain:read` and
   `domains.dns:update` only. No purchase or nameserver permissions.
4. PAT path only: on macOS run `credentials --prompt GODADDY_API_TOKEN --json` for private native
   entry. Their own editor is the fallback if unavailable, unsupported, or preferred; follow
   [How the human connects accounts](../SKILL.md#how-the-human-connects-accounts) for fallback,
   replacement and cancellation. Never put the value in chat or arguments. Classic key/secret pairs are not used.
5. Run `doctor`. Current GoDaddy documentation allows domain management when the account holds at
   least one domain, or has a qualifying plan; a 403 may indicate missing scope or account eligibility.
6. Show the complete plan and obtain explicit DNS approval before `apply --confirm-dns`.

golive preserves unrelated records. It can change records it created only while their stored
fingerprints still match; existing matching records are accepted without taking ownership. An
unmanaged conflicting record, duplicate SPF or a delegated child zone stops the write. Ask the human
to resolve the specified record in the dashboard or choose a fresh subdomain, then re-plan. Existing
SPF policies requiring an added sender need manual review unless golive created the policy.

GoDaddy requires TTL 600–86400 and does not support an apex CNAME. Use the host's apex A/AAAA
instructions or a subdomain. Domain purchases, renewals, transfers and nameserver changes are outside
this adapter. `golive teardown` removes fingerprint-matched records after plan approval and
`--confirm-destroy`; manual dashboard removal should likewise use the record IDs tracked under
`godaddy.recordFingerprint:<zone>:<recordId>` and confirm their current state first.

Official references: [DNS API](https://developer.godaddy.com/en/docs/api-users/domains/manage/dns),
[PAT setup](https://developer.godaddy.com/en/docs/api-users/auth),
[MCP limits](https://developer.godaddy.com/en/docs/api-users/mcp).
writing-skillsobra/superpowersUse when creating new skills, editing existing skills, or verifying skills work before deploymentStars: 322kUpdated Claude CodeCodexVerifiedInstall
xlsxanthropics/skillsUse this skill any time a spreadsheet file is the primary input or output. This means any task where the user wants to: open, read, edit, or fix an existing .xlsx, .xlsm, .xltx, .csv, or .tsv file (e.g., adding columns, computing formulas, formatting, charting, cleaning messy data); create a new spreadsheet from scratch or from other data sources; or convert between tabular file formats. Trigger especially when the user references a spreadsheet file by name or path — even casually (like "the xlsx in my downloads") — and wants something done to it or produced from it. Also trigger for cleaning or restructuring messy tabular data files (malformed rows, misplaced headers, junk data) into proper spreadsheets. The deliverable must be a spreadsheet file. Do NOT trigger when the primary deliverable is a Word document, HTML report, standalone Python script, database pipeline, or Google Sheets API integration, even if tabular data is involved.Stars: 198kUpdated Claude CodeCodexVerifiedInstall
shipping-and-launchaddyosmani/agent-skillsPrepares production launches. Use when preparing to deploy to production, or when asking what needs to be in place before shipping. Use when you need a pre-launch checklist, when setting up monitoring, when planning a staged rollout, or when you need a rollback strategy.Stars: 119kUpdated Claude CodeCodexVerifiedInstall
childhoodthedotmack/claude-memBabysit a shipped release after merge, publication, or deployment. Verify published packages, production behavior, installed plugins, and late CI or user reports until the observation window is clean; use babysit for PR readiness before release.Stars: 118kUpdated Claude CodeCodexVerifiedInstall