agentleFS
Sign inStart free
ImYourBoyRoyImYourBoyRoy/Portable_Web_toolkit/skills/discovery-doctor/SKILL.md

discovery-doctor

Skill2 starsChanged 4 months agoMITView on GitHub

Run Portable Web Toolkit discovery-doctor to verify robots, sitemap, llms, humans, security.txt, content APIs, and JSON-LD for toolkit-managed sites. Use before deploy on dist output and after production deploy on the live URL.

The file

We split this skill into the rules it gives an agent

1 rule. About 0 are common, 0 are distinctive, and 1 is 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.

  • 1

    Very specific

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

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

    Prefer toolkit discovery generators — never @astrojs/sitemap / @astrojs/robots.

    line 25

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

Discovery Doctor

# Workers SSR output
node ./Web_Toolkit/discovery_doctor/bin/discovery-doctor.mjs ./dist/client
# Pages static
node ./Web_Toolkit/discovery_doctor/bin/discovery-doctor.mjs ./dist
# Live
node ./Web_Toolkit/discovery_doctor/bin/discovery-doctor.mjs https://example.com
# Site-specific contract and public API/MCP checks
node ./Web_Toolkit/discovery_doctor/bin/discovery-doctor.mjs https://example.com --site-profile ./site.site-profile.json
# One-off gates
node ./Web_Toolkit/discovery_doctor/bin/discovery-doctor.mjs ./dist --require-llms --skip-link-checks

Rules

  1. Failures before production deploy are blockers for the active policy.
  2. The default toolkit contract requires robots, sitemap, llms.txt, llms-full.txt, humans.txt, security.txt, the structured content API, headers, and JSON-LD. Explicitly relaxed or runtime-only resources are INFO when absent; present-but-invalid resources are failures.
  3. Prefer toolkit discovery generators — never @astrojs/sitemap / @astrojs/robots.
  4. Environment-aware: preview/dev should noindex and does not require sitemap or security.txt by default; production allows indexing and requires the full core contract.
  5. Pass --site-profile so diagnostics.discovery can declare required public APIs and MCP endpoints without hardcoding a client into the toolkit.
  6. Live MCP checks use modern 2026-07-28 discovery with legacy 2025-11-25 fallback; they never call tools or send credentials.
  7. PageSpeed Insights measures performance; it is not an llms.txt conformance authority.

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