agentleFS
DevinoSolutionsDevinoSolutions/claude-plugins/skills/preflighting-domains/SKILL.md

preflighting-domains

Skill0 starsChanged 9 days agoMITView on GitHub

Pre-flights a domain in doDomain before anyone touches DNS: finds who runs DNS, the DNS provider and registrable zone, and whether the domain qualifies for one-click connect. Use when the user asks 'who runs DNS for shop.acme.com', 'can this domain do one-click connect', 'which DNS provider does this domain use', 'check this domain', 'how hard is it to connect this custom domain', or wants a DNS lookup before onboarding a customer domain. Read-only.

The file

We split this skill into the rules it gives an agent

7 rules. About 0 are common, 2 are distinctive, and 5 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈2

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 5

    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:check_domain for that hostname.

    line 28
  4. Very specific:

    Call dodomain:list_connections filtered to the domain to see whether the team already has a connection for it.

    line 29
  5. Distinctive:

    If the tier is 3 (guided manual), summarize the provider-specific setup guide the tool returned so the user can pass it on.

    line 31
  6. Very specific:

    Never call dodomain:create_connect_session, dodomain:verify_connect_session, or dodomain:reverify_connection from this skill.

    line 36
  7. Distinctive:

    Only report fields the tool returned.

    line 38

≈ “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/preflighting-domains/SKILL.md by scripts/sync-skills.mjs. Edit the plugin copy, then run the script. -->

doDomain domain pre-flight

Tell the user what connecting a domain will involve before a connect session is created. This skill only reads public DNS and team state; it creates nothing and uses no quota.

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:check_domain: the DNS provider managing the domain, the registrable zone, the connect tier it qualifies for (1 one-click OAuth, 2 Domain Connect, 3 guided manual), detection confidence, nameservers, and a provider-specific setup guide.
  • dodomain:list_connections: existing connections on the team, filterable by domain. Use it to see whether the domain is already connected.

Workflow

  1. Take the exact hostname the user gave (for example shop.acme.com). If they gave a URL, strip the scheme and path.
  2. Call dodomain:check_domain for that hostname.
  3. Call dodomain:list_connections filtered to the domain to see whether the team already has a connection for it.
  4. Report in this order: DNS provider, registrable zone, connect tier in plain words, what the customer will have to do for that tier, and whether a connection already exists.
  5. If the tier is 3 (guided manual), summarize the provider-specific setup guide the tool returned so the user can pass it on.
  6. Offer the connecting-customer-domains skill as the next step. Do not start a session from here.

Rules

  • Never call dodomain:create_connect_session, dodomain:verify_connect_session, or dodomain:reverify_connection from this skill. Pre-flight is read only.
  • Results come from the live DNS system and can change between calls. Say so if the user compares two runs.
  • Only report fields the tool returned. If detection confidence is low, say so instead of presenting the provider as certain.

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.