agentleFS
DevinoSolutionsDevinoSolutions/claude-plugins/skills/checking-domain-connections/SKILL.md

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.

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
  1. Very specific:

    Every tool in this skill comes from the dodomain MCP server, the doDomain connector, and is written here as dodomain:<tool>.

    line 13
  2. Very specific:

    Tools listed by name: call them directly, for example dodomain:check_domain.

    line 15
  3. Very specific:

    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.

    line 29
  4. Very specific:

    If the user asks for a recheck, confirm which connection, then call dodomain:reverify_connection once.

    line 32

≈ “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.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md
<!-- 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_tools and dodomain:execute_typescript listed (Code Mode, the default): call dodomain:search_tools first, then call each tool inside dodomain:execute_typescript as external_<tool> (for example external_check_domain); the program must return its 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_tools does not return the tool either, its OAuth scope was not granted; the user reconnects doDomain and approves that scope.
  • No dodomain tools at all: doDomain is not connected yet. Follow the setup-dodomain skill.

Tools you will use

  • dodomain:list_apps: app ids and names, so connections can be grouped by app.
  • dodomain:list_connections: connections with status, fqdn, and the verifiedAt, lastCheckedAt, and brokenAt timestamps. 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

  1. 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. Follow pagination until you have the full set.
  2. Group the results by status. List broken connections first with fqdn, brokenAt, and lastCheckedAt, then healthy ones with verifiedAt.
  3. For each broken connection the user cares about, call dodomain:check_domain to name the DNS provider behind it.
  4. If the user asks for a recheck, confirm which connection, then call dodomain:reverify_connection once.
  5. 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_connection answers { accepted: true } and nothing else. Never report that as the domain being verified.
  • Rechecks are rate limited. On RATE_LIMITED, report retryAfterSeconds and stop. Never loop on rechecks.
  • An unknown connection id returns NOT_FOUND. Say the connection is not on this team and offer dodomain:list_connections.
  • Report timestamps in the user's timezone and say which timezone you used.

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.