← ClaudeAtlas

seo-agenticlisted

Use when auditing whether an AI agent can safely understand and complete a web task through the rendered interface, DOM, accessibility tree, forms, authentication, consent, state changes, and documented protocol capabilities such as UCP, ACP, MCP, or A2A; treat this as task readiness and accessibility, not a ranking factor or guaranteed agent usage.
oegeyilmaz9/seo-aeo-geo-ultimate · ★ 2 · AI & Automation · score 66
Install: claude install-skill oegeyilmaz9/seo-aeo-geo-ultimate
# Agentic Web Readiness Audit whether a permitted agent can perceive, understand, and safely complete a bounded task using the same truthful interface and controls available to users. Read [agent-task-protocol.md](references/agent-task-protocol.md) before a formal audit. ## Procedure 1. Define one user-authorized task, start/end states, account/access assumptions, locale/device, risk class, owner, and success evidence. 2. Capture screenshot, DOM, accessibility tree, accessible names/roles/states, focus order, form labels/errors, dynamic state, network-independent confirmations, and any approved agent trace. 3. Verify semantic controls, stable identifiers/state, keyboard operation, loading/error recovery, consent, authentication, rate limits, and human-readable confirmation. 4. Require explicit confirmation for purchase, publication, deletion, permission, financial, legal, or other consequential actions. Never weaken security, privacy, bot controls, or anti-abuse systems for convenience. 5. Test task completion with bounded safe inputs in an authorized environment. Record partial completion, blocked access, ambiguity, and irreversible steps; do not simulate success. 6. Evaluate UCP, ACP, MCP, A2A, or similar capabilities only against current specifications and a documented consumer. Record discovery location, operations, authentication, version, fallback, owner, and policy boundary. 7. Route crawl/index concerns to `seo-technical`, commerce data to `seo-commerce`, accessib