Run any Skill in Manus with one click

domains

Stars0

Forks0

UpdatedJuly 22, 2026 at 00:42

Wire a domain the user ALREADY OWNS (GoDaddy/Namecheap/Cloudflare/…) to their Convex app: exact DNS records, custom-domain attachment, auth-origin rebind. TRIGGER when the user owns a domain and wants it pointing at their app ('point my domain at this', 'use my own domain', 'set up example.com'). Never asks for registrar credentials.

Installation

Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.

Run Skill in Manus

Source

get-convex

get-convex/convex-kimi-plugin

View GitHub Repository View Creator Repositories

Download

Run Skill in Manus

Related occupationsSOC

Based on SOC occupation classification

Network and Computer Systems AdministratorsComputer and Mathematical Occupations·SOC 15-1244

SKILL.md

readonly

name	domains
description	Wire a domain the user ALREADY OWNS (GoDaddy/Namecheap/Cloudflare/…) to their Convex app: exact DNS records, custom-domain attachment, auth-origin rebind. TRIGGER when the user owns a domain and wants it pointing at their app ('point my domain at this', 'use my own domain', 'set up example.com'). Never asks for registrar credentials.
license	Apache-2.0

Custom domain with your own provider ($domains)

Point a domain the user already owns at their Convex app. No purchase, no registrar credentials — you give the user the exact records to create themselves.

Procedure

Identify the target: the published site host (for static hosting) or the deployment's HTTP actions URL (npx convex env get CONVEX_SITE_URL or the dashboard).
Give the exact DNS records to create at THEIR registrar: the CNAME (or A/ALIAS at the apex) plus the TXT verification record — concrete host/value strings, not placeholders.
Attach the custom domain on Convex (dashboard → deployment → Custom Domains, or the CLI) and wait for verification. DNS propagation can take minutes to hours — tell the user, don't poll forever.
If the app uses auth (passkeys/OAuth), rebind the auth origin (SITE_URL / RP_ID / ORIGIN env vars) to the new domain and re-deploy — otherwise sign-in breaks on the new domain.
Verify: the domain serves the app over HTTPS, including the apex → www redirect if configured.

Rules

Never ask for registrar credentials — the user creates the records.
Always include the TXT verification record, not just the CNAME.
Rebinding the domain changes the auth origin — re-deploy after, or sign-in breaks.

More from this repository

same repository

check-updates

get-convex/convex-kimi-plugin

Check the CURRENT Convex app's pinned components against the latest recommended versions and offer to upgrade them — e.g. the passkey auth component's new email-first sign-in. TRIGGER when the user runs /check-updates or $check-updates, asks 'are my components up to date', 'any updates', 'upgrade auth', 'upgrade my components', or wants the newest features after a quickstart. Applies each upgrade behind a build gate (verify-or-revert) with the user's consent.

2026-07-221

convex-expert

get-convex/convex-kimi-plugin

Convex backend rules — consult this whenever writing or editing any code inside a convex/ directory (schemas, queries, mutations, actions, HTTP endpoints, crons, file storage, auth, component installation). TRIGGER before touching convex/ functions, so the code uses the object-form syntax, validators, indexes, and component patterns that generic models get wrong.

2026-07-221

convex-reviewer

get-convex/convex-kimi-plugin

Review Convex code for security, auth, validators, performance, and best practices. TRIGGER when the user asks to review/audit Convex code, or after writing convex/ functions you want checked. Applies the Convex-specific review checklist (auth checks, args/returns validators, internal vs public, indexes-not-filter, OCC conflicts, pagination).

2026-07-221

name	domains
description	Wire a domain the user ALREADY OWNS (GoDaddy/Namecheap/Cloudflare/…) to their Convex app: exact DNS records, custom-domain attachment, auth-origin rebind. TRIGGER when the user owns a domain and wants it pointing at their app ('point my domain at this', 'use my own domain', 'set up example.com'). Never asks for registrar credentials.
license	Apache-2.0

Custom domain with your own provider ($domains)

Point a domain the user already owns at their Convex app. No purchase, no registrar credentials — you give the user the exact records to create themselves.

Procedure

Identify the target: the published site host (for static hosting) or the deployment's HTTP actions URL (npx convex env get CONVEX_SITE_URL or the dashboard).
Give the exact DNS records to create at THEIR registrar: the CNAME (or A/ALIAS at the apex) plus the TXT verification record — concrete host/value strings, not placeholders.
Attach the custom domain on Convex (dashboard → deployment → Custom Domains, or the CLI) and wait for verification. DNS propagation can take minutes to hours — tell the user, don't poll forever.
If the app uses auth (passkeys/OAuth), rebind the auth origin (SITE_URL / RP_ID / ORIGIN env vars) to the new domain and re-deploy — otherwise sign-in breaks on the new domain.
Verify: the domain serves the app over HTTPS, including the apex → www redirect if configured.

Rules

Never ask for registrar credentials — the user creates the records.
Always include the TXT verification record, not just the CNAME.
Rebinding the domain changes the auth origin — re-deploy after, or sign-in breaks.