agent-ready
Skill1 starsChanged 9 days agoMITView on GitHub
Make a public origin discoverable to AI agents: well-known discovery documents, crawl signals, auth metadata, agent protocol cards, and optional agentic commerce. Use when the user asks about agent-ready, well-known discovery, Auth.md, api-catalog, A2A, MCP server cards, WebMCP, DNS-AID, ACP, UCP, or x402. Stack- and host-agnostic: publish the HTTP contract from whatever already serves the site. For page SEO, crawl audits, and GEO strategy use seo-audit and everything-seo.
10 other projects use a version of this.
Adopted by
Most recently taken up by
- matteobaccan/AgentReadytheir own version, first seen Nov 1, 2026
- dgalarza/agent-skillstheir own version, first seen Nov 1, 2026
- howardchenghuang-dotcom/agent-readytheir own version, first seen Nov 1, 2026
- ora/skillstheir own version, first seen Sep 28, 2026
- mblode/agent-skillstheir own version, first seen Sep 11, 2026
- DamonRabie/agents_librarytheir own version, first seen Aug 22, 2026
Other versions10 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 10
- mblode/agent-skills★ 189same name
- dgalarza/agent-skills★ 72same name
- Owl-Listener/agent-ready★ 10same name
- DamonRabie/agents_library★ 1same name
- hao0401/agent-ready★ 1same name
- matteobaccan/AgentReady★ 1same name
- ora/skills★ 1same name
- duongxthanh/agent-ready★ 0same name
- howardchenghuang-dotcom/agent-ready★ 0same name
- shuvoships/agent-ready★ 0same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository107 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- .cursor/rules/base.mdcCursor rule
- .cursor/rules/changelog.mdcCursor rule
- .cursor/rules/comments.mdcCursor rule
- .cursor/rules/release.mdcCursor rule
- .cursor/rules/seo-ai-search.mdcCursor rule
- .cursor/rules/testing.mdcCursor rule
- agent-readySkill
- authoring-skills-and-rulesSkill
- blinded-evalSkill
- cloakbrowser-fallbackSkill
- deep-deliberationSkill
- design-rationaleSkill
- dissectSkill
- documentation-writerSkill
- everything-seoSkill
- executeSkill
- generating-app-verifySkill
- inceptionSkill
- kit-workflowsSkill
- marketing-psychologySkill
- media-genSkill
- nlm-skillSkill
- opinionSkill
- proving-change-safetySkill
- refreshing-app-verifySkill
- release-deploySkill
- seo-auditSkill
- startup-marketing-brainSkill
- subsystem-walkthroughSkill
- trlSkill
- unmatched-workflowSkill
- agent-readySkill
- authoring-skills-and-rulesSkill
- blinded-evalSkill
- cloakbrowser-fallbackSkill
- deep-deliberationSkill
- design-rationaleSkill
- dissectSkill
- documentation-writerSkill
- everything-seoSkill
- executeSkill
- generating-app-verifySkill
- inceptionSkill
- kit-workflowsSkill
- marketing-psychologySkill
- media-genSkill
- nlm-skillSkill
- opinionSkill
- proving-change-safetySkill
- refreshing-app-verifySkill
- release-deploySkill
- seo-auditSkill
- startup-marketing-brainSkill
- subsystem-walkthroughSkill
- trlSkill
- unmatched-workflowSkill
- authoring-skills-and-rulesSkill
- blinded-evalSkill
- The first 60 shown.
The file
We split this skill into the rules it gives an agent
3 rules. 0 are common, 2 are distinctive, and 1 is very specific to this project.
0
Common
Most of the 9 edited versions we read keep these.
2
Distinctive
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
- Very specific: line 110
Every skip: / n/a: line.
- Distinctive: line 114
No host lock-in: Do not tell the agent to use a specific CDN, DNS dashboard, or edge worker product.
- Distinctive: line 116
No framework lock-in: Do not require Next, Workers, or a named middleware package when the project's stack already has an equivalent.
“Common” is measured: kept by at least 6 in 10 of the 9 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Agent-ready discovery
Leading words: skip unless, well-known discovery, policy match, HTTP contract, stack-agnostic, host-agnostic.
Publish the HTTP contract (URL, status, Content-Type, required fields). Serve it from origin, the static/public dir, or the edge in front of origin — whatever already ships the site. Do not prescribe a host product or a single framework.
Copy this file's phases into the todo list verbatim. Skipped steps stay
with skip: / n/a:.
Phase 1 — Classify
- [ ] Name the origin (scheme + host). No hard-coded example domains.
- [ ] Public content? (HTML pages, blog, marketing)
- [ ] API? (programmatic surface agents might call)
- [ ] Agent product? (this origin hosts A2A, MCP, WebMCP, or outbound bot requests)
- [ ] Commerce? (agents can buy, pay, or check out)🛑 Checkpoint: Write the four yes/no flags. Do not publish discovery documents the classification did not select.
Phase 2 — Crawl surface
Delegate robots.txt + sitemap existence to seo-audit if a page audit
is already in flight. This skill still owns policy match and optional
markdown negotiation.
- [ ] GET /robots.txt is text/plain 200 (RFC 9309). Sitemap: line if a sitemap exists.
- [ ] Content-Signal on robots.txt matches User-agent policy (search / ai-train / ai-input).
- [ ] GET /sitemap.xml is XML 200 listing canonical public URLs, or n/a: no public HTML.
- [ ] Optional: Accept: text/markdown on key pages returns markdown; HTML stays the default.Pull references/well-known-discovery.md
only for Link headers / catalogs. Content-Signal detail lives with
everything-seo technical SEO.
🛑 Checkpoint: Policy is named (what search, train, and input are set to)
and User-agent lines match it. skip: if the origin has no public crawl surface.
Phase 3 — Discovery documents that apply
- [ ] API catalog + Link headers — skip unless API
- [ ] Auth.md + OAuth/OIDC / protected-resource metadata — skip unless API with auth
- [ ] A2A card, agent-skills index, MCP server card, WebMCP — skip unless agent product
- [ ] Web Bot Auth JWKS — skip unless this origin sends bot/agent requests
- [ ] DNS-AID under _agents — skip unless agent product needs DNS discovery
- [ ] ACP / AP2 / MPP / UCP / x402 — skip unless commercePull depth only for selected rows:
| File | When |
| references/well-known-discovery.md | api-catalog, Link, Auth.md, OAuth |
| references/agent-protocols.md | A2A, skills index, MCP, WebMCP, Web Bot Auth, DNS-AID |
| references/agentic-commerce.md | ACP, AP2, MPP, UCP, x402 |
Phase 4 — Verify
- [ ] For each published URL: GET it. Record status, Content-Type, required fields.
- [ ] Do not POST registration or payment endpoints during a passive check.
- [ ] List every skip: / n/a: with the classification reason.Any miss on a selected document → back to Phase 3.
Reply contract
- Classification flags (content / API / agent product / commerce).
- Published URLs that passed, with status + Content-Type.
- Failures (URL + missing field).
- Every
skip:/n/a:line.
What NOT to do
- No host lock-in. Do not tell the agent to use a specific CDN, DNS dashboard, or edge worker product.
- No framework lock-in. Do not require Next, Workers, or a named middleware package when the project's stack already has an equivalent.
- No scanner lock-in. A third-party agent-ready scanner is optional. The proof is the fetched document.
- Do not invent endpoints for a site that is not an API, agent product, or store.
- Do not POST
/agent/auth, checkout, or payment during discovery.
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
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.

