사용 방법
- 설치 명령을 복사하고 자신의 에이전트 환경에 설치하기 전에 소스 패키지를 확인하세요.
- 필요한 도구, 인증 정보, 지원 환경은 원본 문서에서 확인하세요.
- 입력과 원하는 산출물을 설명하고 출처와 결과를 대조하세요.
npx skills add https://github.com/get-convex/agent-skills --skill convex-domains시작 전 확인
- 설치에는 모델 구독, API 한도, 파일 접근 권한이 포함되지 않습니다.
- 별점 수와 설치 수는 활동 지표이며 독립적인 품질·보안 검증이 아닙니다.
원본 Skill 문서
원본 저장소의 제목, 예시, 코드, 표, 링크, 이미지를 유지해 표시합니다.
<!-- 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.
