checking-domain-connections
Skill0 starsChanged 9 days agoMITView on GitHub
Reviews the DNS health of existing doDomain connections and queues rechecks after confirmation. Use when the user asks 'which of my connected domains are broken', 'is this customer's domain still connected', 'when was this connection last checked', 'recheck the DNS on this connection', 'find domains with DNS drift', or wants a custom domain health report.
In this repository66 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- adding-uptime-monitorsSkill
- analyzing-page-performanceSkill
- booking-meetingsSkill
- building-onboarding-workflowsSkill
- building-study-guidesSkill
- capturing-tasksSkill
- capturing-web-pagesSkill
- chasing-unpaid-invoicesSkill
- checking-email-deliverabilitySkill
- checking-notification-deliverySkill
- checking-uptime-statusSkill
- cleaning-up-bookkeepingSkill
- connecting-customer-domainsSkill
- discussing-buildsSkill
- drafting-invoicesSkill
- drafting-social-postsSkill
- editing-demosSkill
- editing-page-draftsSkill
- extracting-document-textSkill
- finding-meeting-timesSkill
- handling-flaky-changesSkill
- investigating-tasksSkill
- making-demo-videosSkill
- managing-bookingsSkill
- managing-content-calendarSkill
- managing-demosSkill
- managing-voice-librarySkill
- planning-revisionSkill
- preflighting-domainsSkill
- publishing-pagesSkill
- reading-financial-reportsSkill
- reading-text-aloudSkill
- reading-web-pagesSkill
- reporting-snapvisor-usageSkill
- researching-course-materialSkill
- researching-summary-librarySkill
- responding-to-incidentsSkill
- reviewing-email-performanceSkill
- reviewing-notification-workflowsSkill
- reviewing-social-performanceSkill
- reviewing-visual-buildsSkill
- reviewing-workloadSkill
- searching-getitdone-api-docsSkill
- sending-email-campaignsSkill
- sending-notificationsSkill
- setup-bioflowSkill
- setup-calySkill
- setup-demofySkill
- setup-dodomainSkill
- setup-getitdoneSkill
- setup-notiflySkill
- setup-postifySkill
- setup-sendlySkill
- setup-shortySkill
- setup-snapvisorSkill
- setup-superbooksSkill
- setup-unotesSkill
- setup-upapiSkill
- setup-uptimelySkill
- The first 60 shown.
The file
We split this skill into the rules it gives an agent
4 rules. About 0 are common, 0 are distinctive, and 4 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈0
Distinctive · estimate
This author's own choices. Worth a look.
4
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 13
Every tool in this skill comes from the dodomain MCP server, the doDomain connector, and is written here as dodomain:<tool>.
- Very specific: line 15
Tools listed by name: call them directly, for example dodomain:check_domain.
- Very specific: line 29
Call dodomain:list_apps, then dodomain:list_connections for the app the user named, or for every app when they asked about the whole team.
- Very specific: line 32
If the user asks for a recheck, confirm which connection, then call dodomain:reverify_connection once.
≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
<!-- Generated from plugins/dodomain/skills/checking-domain-connections/SKILL.md by scripts/sync-skills.mjs. Edit the plugin copy, then run the script. -->doDomain connection health
Report which of the team's domain connections are healthy, which are broken, and queue a DNS recheck where the user asks for one.
Connecting and calling the tools
Every tool in this skill comes from the dodomain MCP server, the doDomain connector, and is written here as dodomain:<tool>.
- Tools listed by name: call them directly, for example
dodomain:check_domain. - Only
dodomain:search_toolsanddodomain:execute_typescriptlisted (Code Mode, the default): calldodomain:search_toolsfirst, then call each tool insidedodomain:execute_typescriptasexternal_<tool>(for exampleexternal_check_domain); the program mustreturnits result. Scopes, confirmations and gates are identical on both surfaces. - "Tool not found": switch to the Code Mode route instead of retrying the direct call. If
dodomain:search_toolsdoes not return the tool either, its OAuth scope was not granted; the user reconnects doDomain and approves that scope. - No
dodomaintools at all: doDomain is not connected yet. Follow thesetup-dodomainskill.
Tools you will use
dodomain:list_apps: app ids and names, so connections can be grouped by app.dodomain:list_connections: connections withstatus,fqdn, and theverifiedAt,lastCheckedAt, andbrokenAttimestamps. Filter by app or domain. Paginated.dodomain:reverify_connection: queue an on-demand DNS recheck of one connection. Returns{ accepted: true }; the check runs asynchronously and does not return a verdict.dodomain:check_domain: provider and zone for a broken domain, so the user knows which DNS provider the customer uses.
Workflow
- Call
dodomain:list_apps, thendodomain:list_connectionsfor the app the user named, or for every app when they asked about the whole team. Follow pagination until you have the full set. - Group the results by status. List broken connections first with
fqdn,brokenAt, andlastCheckedAt, then healthy ones withverifiedAt. - For each broken connection the user cares about, call
dodomain:check_domainto name the DNS provider behind it. - If the user asks for a recheck, confirm which connection, then call
dodomain:reverify_connectiononce. - Tell the user the recheck is queued and runs in the background. Offer to read the result back later with
dodomain:list_connections.
Rules
dodomain:reverify_connectionanswers{ accepted: true }and nothing else. Never report that as the domain being verified.- Rechecks are rate limited. On
RATE_LIMITED, reportretryAfterSecondsand stop. Never loop on rechecks. - An unknown connection id returns
NOT_FOUND. Say the connection is not on this team and offerdodomain:list_connections. - Report timestamps in the user's timezone and say which timezone you used.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

