Verify your domain
Domain verification promotes you from unverified → verified tier. Every skill you publish after verifying inherits that signal.
Why bother
- Discoverability. SDK consumers can set
trustFloor: 'verified'to filter out anonymous publishers entirely. Below that floor, your skills don't surface. - Reputation. A green VERIFIED badge on your skills says "this publisher proved they own a domain associated with a real project."
- A path to
official. The official tier is manually awarded; verified is the prerequisite.
What it doesn't do
- Doesn't grant any extra permissions on the platform.
- Doesn't automatically mark previously published skills as verified — only future ones. (Backfill is a one-shot SQL update; we run it on request for now.)
- Doesn't vouch for the content of your skills. The judge LLM still scores them.
How it works
It's the same DNS TXT challenge pattern Vercel, Cloudflare, and Google Search Console use:
- You claim a domain.
- We mint a one-time token.
- You publish a TXT record at
_amitte.<your-domain>containing the token. - We resolve the record and confirm the token matches.
- Your tier is promoted.
Step-by-step
1. Sign in
skills login
Or sign in via the portal at the top-right "Sign in" button.
2. Open the verification page
3. Claim a domain
Type the domain you want to verify (e.g. example.com) and click Create challenge.
You'll get a card with three values:
- Host —
_amitte.<your-domain> - Type —
TXT - Value —
amitte-verify=<a-40-char-hex-token>
4. Add the TXT record at your DNS provider
The exact UI varies by provider; the values are the same.
Cloudflare:
Type: TXT
Name: _amitte ← just the subdomain part
Content: amitte-verify=<token>
Proxy status: DNS only ← TXT records can't be proxied; default is fine
TTL: Auto
Other providers (Namecheap, Gandi, Squarespace, etc.) follow the same pattern: add a TXT record at _amitte. with the value the portal showed you.
5. Wait ~30 seconds, then click Check
DNS propagation is usually under a minute on modern providers. If the first check fails with dns lookup failed (ENODATA), give it another 30 seconds and retry.
# To verify the record manually:
dig +short TXT _amitte.example.com
# → "amitte-verify=<token>"
6. Confirm tier promotion
Look at /me — your trust tier badge should now say verified (teal). Any new publish will inherit this.
Multiple domains
Claim as many as you control. Your tier is "verified" if you have at least one verified domain. Removing your last verified domain demotes you back to unverified (existing skills keep their snapshot, never retroactively demoted).
Troubleshooting
| Message | Cause |
|---|---|
dns lookup failed (ENODATA) | Record hasn't propagated yet. Retry in 30 seconds. |
no matching TXT record at _amitte.<domain> (found N) | DNS resolved, but the value didn't match. Check for typos and whitespace. |
domain is already claimed by another publisher | Someone else already verified it. If that's a mistake, file a takedown request. |
invalid domain | The string isn't a valid hostname. We strip schemes and paths but the rest must be RFC-1123. |
Removing a domain
Go to /me/verify, find the row, click the trash icon, confirm. If it was your only verified domain, your tier drops to unverified — but already-published skills keep their snapshot tier.
The signing path for content is separate: see Manifest spec for Sigstore signing details (currently scaffolded; verification ships in a future release).