agentleFS
DevinoSolutionsDevinoSolutions/claude-plugins/skills/connecting-customer-domains/SKILL.md

connecting-customer-domains

Skill0 starsChanged 9 days agoMITView on GitHub

Starts and follows a doDomain connect session that points a customer's own domain at one of the user's apps, returns the DNS records the customer must add, and verifies them. Use when the user asks to 'start a connect session for shop.acme.com on my app', 'connect my customer's custom domain', 'onboard a customer domain', 'what DNS records does my customer need', 'have the records landed yet', or 'verify the domain'. Creating a session uses monthly connection quota and is confirmed first.

The file

We split this skill into the rules it gives an agent

8 rules. About 0 are common, 1 is distinctive, and 7 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 7

    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. If the team has more than one app, ask which one the domain belongs to.

    line 30
  4. Very specific:

    Call dodomain:check_domain for the domain and tell the user which connect tier the customer will get.

    line 31
  5. Distinctive:

    Ask for the DNS records the app needs if the user has not given them.

    line 32
  6. Very specific:

    When the user asks for progress, call dodomain:get_connect_session for the status, then dodomain:verify_connect_session for the per-record …

    line 35
  7. Very specific:

    If a call returns RATE_LIMITED, tell the user the wait in seconds from retryAfterSeconds and stop.

    line 42
  8. Very specific:

    Create at most one session per domain per request.

    line 43

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

Connect a customer domain with doDomain

Walk one domain from a new connect session to verified DNS. Creating a session uses one unit of the plan's monthly connection quota, so confirm before you create 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: the apps on the team with id, name, public widget key, and sandbox flag. Never returns secret keys.
  • dodomain:check_domain: provider, zone, and connect tier for the domain, as a pre-flight.
  • dodomain:create_connect_session: start a session for a domain on an app. Takes the appId, the customer's domain, and the DNS records the app needs; returns a sessionToken and the records to apply. Counts against the monthly connection quota.
  • dodomain:get_connect_session: the current state of a session by token: domain, expected records, and status (pending, detected, authorizing, writing, verifying, verified).
  • dodomain:verify_connect_session: a live check of the session's expected records against authoritative nameservers, with a per-record breakdown of present, propagating, or absent.

Workflow

  1. Call dodomain:list_apps. If the team has more than one app, ask which one the domain belongs to. Point out sandbox apps.
  2. Call dodomain:check_domain for the domain and tell the user which connect tier the customer will get.
  3. Ask for the DNS records the app needs if the user has not given them. Do not invent record targets.
  4. Confirm the app, the domain, and the records, and say that this uses one unit of the monthly connection quota. Then call dodomain:create_connect_session.
  5. Report the sessionToken and list the records the customer must apply, one per line with type, name, and value.
  6. When the user asks for progress, call dodomain:get_connect_session for the status, then dodomain:verify_connect_session for the per-record breakdown.
  7. Present the breakdown record by record. verified is true only when every record matches.

Rules

  • verified: false on a fresh session is a normal answer, not an error. It means the records are not published yet. Name each missing record.
  • propagating means the record is on its way. Suggest checking again in a few minutes rather than calling in a loop.
  • If a call returns RATE_LIMITED, tell the user the wait in seconds from retryAfterSeconds and stop. Do not retry automatically.
  • Create at most one session per domain per request. If the user already has a session token for that domain, use dodomain:get_connect_session instead.

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.