Analyzed Aug 4, 2026
get-convex/agent-skills
convex-domains
Point a domain you already own at your Convex app (DNS records, custom-domain attach, auth-origin rebind).
Installation
npx skills add get-convex/agent-skills --skill convex-domains
Similar popular skills
Related neighbors and high-traction skills in the same topics — useful to compare before installing.
Helps users discover and install agent skills when they ask questions like "how do I do X", "fi…
18.6K installsBrowser automation CLI for AI agents. Use when the user needs to interact with websites, includ…
11.9K installsReact and Next.js performance optimization guidelines from Vercel Engineering. This skill shoul…
3.7K installsReview UI code for Web Interface Guidelines compliance. Use when asked to "review my UI", "chec…
4.7K installsBuild, deploy, evaluate, optimize, fine-tune, and manage Microsoft Foundry agents, models, and …
1.7K installsPrepare azd-based Azure projects for deployment: generates azure.yaml, infrastructure (Bicep/Te…
1.5K installsSecurity audits
Partner security reviews for this skill.
Analyzed Aug 4, 2026
Analyzed Aug 4, 2026
0 alerts
Also in this package
Other skills from get-convex/agent-skills · top by installs.
npx skills add get-convex/agent-skills
More details
Agent compatibility
Declared targets from SKILL.md / docs. Unmarked agents are not listed — the skill may still install via the CLI.
Repository health
main
Package contents
Files included with this skill beyond the listing page.
-
skill md
SKILL.md2,444 B -
docs
SUMMARY.md128 B
History
- First seen on skills.sh
- First recorded snapshot · 18,614 installs
SKILL.md
<!-- GENERATED from convex-agents content/capabilities/domains.json — do not edit by hand. -->
Set up a custom domain with your own provider
Walk the user's own registrar through pointing their domain at the Convex app: identify the target (hosting or deployment URL), create the DNS records, attach the custom domain, and rebind the auth origin if the app uses auth.
Workflow
- Identify the target: the published site host (for
*.convex.appstatic hosting) or the deployment's HTTP actions URL. - Detect an ALREADY-AUTHENTICATED DNS CLI for the user's provider and OFFER to create the records automatically: Cloudflare →
flarectl dns create(note:wrangleritself doesn't manage DNS records) or the CF API via their token env; Route53 →aws route53 change-resource-record-sets; Google Cloud DNS →gcloud dns record-sets create; DigitalOcean →doctl compute domain records create; Vercel DNS →vercel dns add. Check auth read-only first (flarectl user info/aws sts get-caller-identity/doctl account get); show the exact commands and get a yes before running. - If no authed CLI (or the user declines), tell the user exactly which records to create at THEIR registrar: the CNAME (or A/ALIAS at the apex) plus the TXT verification record — with concrete host/value strings, not placeholders.
- Attach the domain as a Convex custom domain (dashboard or CLI) and wait for verification; note DNS propagation can take minutes to hours. Verify records landed with
dig +short. - If the app uses auth (passkeys/OAuth), rebind the auth origin (SITEURL / RPID / ORIGIN env vars) to the new domain and re-deploy/re-publish.
- Verify: the domain serves the app over HTTPS, including the apex → www redirect if configured.
Rules
- Never ask for or handle registrar credentials. A CLI already authenticated on the user's machine is fine — the credential stays in the tool; never install a CLI or run its login/auth flow for this, and never echo tokens.
- DNS changes on a live domain are user-visible: show the exact commands and confirm before running them; verify afterwards with dig.
- Always include the TXT verification record, not just the CNAME.
- Rebinding the domain changes the auth origin — re-publish after, or sign-in breaks.