Use when setting up, troubleshooting, managing, removing, or checking the health of an Auth0 custom authentication domain (e.g. login.example.com), OR when diagnosing an error (400/403/404/409/429) from the /custom-domains Management API — especially Free-tier 403s (credit card on file, not a plan upgrade), self-managed cert 403s, PATCH-type 400s, `operation_not_supported` on `relying_party_identifier`, and 409 domain-already-exists. Handles CNAME creation in the user's DNS provider (Cloudflare, AWS Route 53, Azure DNS automated; other registrars guided), verification polling, Multiple Custom Domains (MCD), default-domain selection, TLS policy, client-IP header, per-domain passkey relying party identifier, and domain metadata.
94
92%
Does it follow best practices?
Impact
98%
1.71xAverage score across 3 eval scenarios
Advisory
Suggest reviewing before use
Domain metadata GET-merge-PATCH pattern
GET before PATCH
0%
100%
Client-side merge
0%
100%
Key removal by omission
0%
100%
Full merged object in PATCH
60%
100%
Single PATCH per domain
100%
100%
Auth0 CLI passthrough used
0%
100%
metadata_state.txt produced
100%
100%
domain_metadata key used
0%
100%
No constraint violation
100%
100%
No null-as-delete
0%
100%
Free-tier 403 diagnosis and domain setup
403 = credit card, not plan
100%
100%
No upgrade suggestion
100%
100%
Billing fix location
100%
100%
auth0_managed_certs default
100%
100%
Speculative RPID for subdomain
0%
100%
NS-based provider detection
0%
100%
Cloudflare = proxied:false
100%
100%
Exponential backoff polling
10%
100%
Post-verify app checklist
60%
100%
No TLS policy question
42%
42%
Domain health audit with renewal-risk detection
DNS vs expected comparison
100%
100%
HTTPS reachability probe
100%
100%
TLS cert expiry check
100%
100%
Renewal-at-risk flagging
100%
100%
Pass/fail/warn visual markers
30%
100%
External resolver cross-check
20%
100%
No speculative create
100%
100%
Tenant name in report header
100%
100%
Default domain surfaced
0%
100%
cert expiry threshold flagging
100%
100%
bdf0dc2
Table of Contents
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.