agentleFS
Sign inStart free
ModernMustardSeedModernMustardSeed/local-growth-crew/skills/domain-checkup/SKILL.md

domain-checkup

Skill0 starsChanged 34 days agoMITView on GitHub

Check a business's domain end to end: whether its email will land, whether its website is safe, whether the domain is owned well, and who controls each layer (registrar, DNS, email, website platform). Use for "is our email going to spam", "who owns our domain", "is our site secure", or before switching web vendors.

The file

We split this skill into the rules it gives an agent

2 rules. About 0 are common, 0 are distinctive, and 2 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.

  • 2

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Run the Domain Health full_domain_report tool on the domain.

    line 10
  2. Very specific:

    Run the Own It audit_ownership tool on the same domain, adding the business name and any profile URLs the user gave.

    line 11

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 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

Domain checkup

Domain: $ARGUMENTS

  1. Run the Domain Health full_domain_report tool on the domain.
  2. Run the Own It audit_ownership tool on the same domain, adding the business name and any profile URLs the user gave.
  3. Report in plain words, in this order:
    • Will email land? SPF, DKIM and DMARC findings, and the exact record to publish for anything failing.
    • Is the website safe? Certificate expiry, TLS versions and security headers.
    • Is the domain owned well? Expiry date, transfer lock and DNSSEC.
    • Who controls what? Registrar, DNS host, email provider and website platform, and how hard each would be to move.
  4. End with the three most urgent actions, each with who can do it and where: the registrar, the DNS host, or the website platform.

Report only what the tools measured. When a record could not be read, say so rather than calling it missing. No em dashes.

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.

Check your setup, free