check-agent-readiness
Skill1 starsChanged 32 days agoMITView on GitHub
Check how well AI agents can find, understand and act on a website using the Stunt Double Index (agent readiness, AI visibility, checkout or support by agents), explain the score from real sessions, compare with peers, and re-score after fixes.
In this repository20 other files it gives its agents.
- AGENTS.mdAGENTS.md
- .claude/CLAUDE.mdCLAUDE.md
- check-brandSkill
- check-complianceSkill
- check-continuitySkill
- check-design-systemSkill
- cloudSkill
- create-actor-panelSkill
- design-reviewSkill
- doctorSkill
- maintain-automationsSkill
- openSkill
- run-qa-suiteSkill
- runSkill
- run-user-interviewSkill
- run-ux-validationSkill
- setup-guardrailsSkill
- setupSkill
- triage-feedbackSkill
- verify-changeSkill
The file
Files
Check agent readiness
- Find the site:
search_index_domains(query). If it is not tracked,request_index_score(domain)adds it and runs the light probes in under a minute (signed-in server only; public domains only, opt-outs respected). Passinclude_agent_sessions=trueonly if the person wants live agent sessions too; they may queue for later that day. In a project linked to an Index domain, passproject_idinstead of a domain to the tools below. - Read the report:
get_index_report(domain)gives the score out of 100, band, rank, per-category and per-provider scores, frictions and failing probe checks. A null score comes withunscored_reasonandunscored_note: report that instead of a number. - Explain weak spots from evidence: take the lowest categories and providers, then
list_index_sessions(domain, category=…)orprovider=…to read what agents tried, their rubric evidence and frictions. Quote what they hit; do not guess causes the sessions do not show. - Compare (optional):
search_index_domains(sector=…)for the sector leaderboard, or query named competitors, thenget_index_reporton those. Index data is public, so no access is needed. - Recommend fixes: rank by impact (heavily weighted failing checks, then frictions recurring across providers, then single-provider issues). Tie each to a failing check or session friction.
- Re-score after fixes ship:
request_index_rerun(domain)(domain owner only, once every 10 minutes, expensive, never to refresh a current report) starts fresh probes and about 24 agent sessions. Polllist_index_sessions(domain, run_id)until none are running, thenget_index_report(domain)and report the change per category.
To confirm a fix on a preview before the re-run, use verify-change; to stop regressions, setup-guardrails.
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.

