← ClaudeAtlas

agent-readylisted

Audit any website for AI and LLM readiness. Analyses structure, content, and technical signals across 60+ criteria. Generates curated llms.txt, JSON-LD structured data, robots.txt patches, Content-Signal headers, and platform-specific deployment code. Works across WordPress, Shopify, Webflow, Next.js, Vite, Astro, static HTML, and any other platform.
kmrzzmaan/agent-ready · ★ 0 · AI & Automation · score 73
Install: claude install-skill kmrzzmaan/agent-ready
# Agent Ready — AI Readiness Audit Skill ## Execution Mode Determine mode before doing anything else. Mode governs how you access site data and how you deploy outputs. ``` IF working directory is open: Run: find . -maxdepth 3 \( -name "*.config.*" -o -name "wp-config.php" \ -o -name "theme.liquid" -o -name "composer.json" \ -o -name "package.json" -o -name "*.gemspec" \ -o -name "_config.yml" -o -name "eleventy.config.*" \) \ 2>/dev/null | head -30 Read: references/platform-detection.md before continuing Set execution_mode = SOURCE IF URL also provided: Set execution_mode = HYBRID ELSE: Set execution_mode = URL IF no URL provided: Ask "What is the URL of the website you want to audit?" Do not ask if URL was already in the invocation message ``` Mode capabilities: - SOURCE: Read files directly. Place generated files. Validate source JSON-LD. Recommend build pipeline. - URL: Fetch deployed site only. Output standalone files for manual deployment. - HYBRID: Use source for generation and file placement. Use URL for validation and header checking. Prefer this when both are available. --- ## Step 1 — Onboarding Questions Ask all questions in one message. Do not split across multiple turns. ``` Q1 [only if URL not yet known]: What is the website URL? Q2: What is the primary purpose of this site? Options: blog/content | ecommerce | saas/software | docs/developer | portfolio | business/marketing | other Q3: Who is t