AI Readiness Kit

io.github.silverbackmarketingPublished by GitHub account silverbackmarketingv1.0.0Updated Oct 24, 2026

Generate 18 AI readiness files (llms.txt, ai.txt, RAG indexes, schema) for any website.

VerifiedStreamable HTTPWeb executableWeb Search & ScrapingKnowledge & MemoryDeveloper Tools

Overview

AI-generated overview

A hosted MCP server that guides an assistant through researching a website and generating a set of AI readiness files such as llms.txt, ai.txt, schema and RAG.

What you can do
Start and drive the AI readiness workflow: research a site, classify its type and write the output files, or fetch the full skill instructions and classification guide directly. List the 18 output files in generation order with their filenames and purposes. Look up the detailed specification for a single output file, such as llms.txt or ai-entities.json. Convert rag-index.json content into JSONL, one JSON object per line, for embedding pipelines.
When to use it
Useful when you want an assistant to produce generative-engine-optimization files for a website so AI assistants describe the brand accurately, and you prefer a hosted endpoint over installing a local skill.
Requirements
A remote streamable HTTP endpoint; no package, account, API key or header is declared. The README's client setup examples use the hosted URL, and one client path (Perplexity connectors) is noted as needing a paid plan.
Before you install
The workflow researches a site and writes generated files, so review output before deploying anything to a web root. Generated robots.txt and policy files make public statements about crawler access and content use. The README notes that non-Claude install targets write into the current project directory and that --force overwrites existing files.

Installation

In SourceWeft

  1. Open AI Readiness Kit in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/io.github.silverbackmarketing%2Fai-readiness/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config.

{
  "mcpServers": {
    "ai-readiness-kit": {
      "type": "http",
      "url": "https://ai.silverbackmarketing.com/api/mcp"
    }
  }
}

README

[AI Readiness Files — a structured kit of files that tells ChatGPT, Claude, Gemini, and Perplexity exactly who you are before they guess wrong]

AI Readiness Skill

[npm version] [npm downloads] [License: MIT] [MCP compatible] [Claude Skill] [Cursor compatible] [OpenAI Codex compatible] [Perplexity compatible]

[Optimizes for AI search]

Generate a complete suite of AI readiness files (GEO / generative engine optimization) for any website in a single command — llms.txt, ai.txt, schema, RAG indexes, and more. Install it into Claude, Cursor, Windsurf, GitHub Copilot, Gemini, or Codex with one npx command, or connect over MCP with no install.

📖 Live site & full docs: ai.silverbackmarketing.com · ⭐ Star this repo if it helps you get found by AI.

[AI Readiness Kit - The 17 files that make your site understandable to AI | Product Hunt]


What is the AI Readiness Kit?

The AI Readiness Kit is a free, open-source set of 17 structured files you deploy at the root of your website — robots.txt, ai.txt, llms.txt, schema, RAG indexes, and more — that tell ChatGPT, Claude, Gemini, and Perplexity exactly who you are, what you offer, and how to represent you. Generate the whole set, tailored to any site, with a single command. Free forever (MIT); install with npx or run it over MCP with no install.


Why AI readiness

When someone wants a product recommendation, a service provider, or a straight answer, they often ask ChatGPT, Claude, Gemini, or Perplexity before they ever visit a website. If you are not giving those systems clear, current signals, they guess — and they often guess wrong.

AI readiness files are structured files you deploy at the root of your website to tell AI systems exactly who you are, what you offer, and where to send people. They speak a format AI already understands (the llmstxt.org standard, Schema.org, and emerging AI-crawler conventions), so assistants stop guessing about your brand based on stale training data and start representing you accurately in their answers.

This skill researches any site, classifies its industry, and generates all of those files for you — tailored to that business — in one command.


Contents


Install

Quick install (any agent) — npx

bash
# Global skill install → ~/.agents/skills/ AND ~/.claude/skills/ (default)npx @silverbackmarketing/ai-readiness install
# AGENTS.md — the cross-agent standard (Cursor, Codex & others)npx @silverbackmarketing/ai-readiness install --agent agents
# Both at once (recommended)npx @silverbackmarketing/ai-readiness install --all

Primary targets:

TargetInstalls to
skills~/.agents/skills/ai-readiness/ and ~/.claude/skills/ai-readiness/ (full skill — SKILL.md + scripts + references)
agents./AGENTS.md — the standard read by Cursor, Codex, and a growing list of agents (adds a delimited block, keeps your existing content)
claude~/.claude/skills/ai-readiness/ only

For prompt-based agents, AGENTS.md is the default and recommended target — most modern agents now read it. Tool-specific files remain available if you prefer them:

Opt-in targetInstalls to
cursor./.cursor/rules/ai-readiness.mdc
windsurf./.windsurf/rules/ai-readiness.md
copilot./.github/copilot-instructions.md (delimited block)
gemini./GEMINI.md (delimited block)
generic./ai-readiness.SKILL.md (paste into any system prompt)

Non-Claude targets install into the current directory, so run the command from your project root. --all installs Claude + AGENTS.md. Add --force to overwrite, or --dir <path> to change the target. Shared-file installs insert a marked block and update it in place on re-run, so they never clobber your other instructions.

Other install options

  • Claude Cowork one-click: download and open ai-readiness.skill.
  • Any AI, manually: copy SKILL.md into the assistant's system prompt or custom instructions.

After installing, trigger it with /ai-readiness yoursite.com in Claude, or just ask any agent: "create AI readiness files for yoursite.com."

Use via MCP (no install)

Connect your coding agent to the hosted MCP server instead of installing the skill locally. Same workflow — research a site and generate all the files.

Production: https://ai.silverbackmarketing.com/api/mcp

Example prompts once connected:

Generate AI readiness files for example.comUse ai-readiness to list all output filesGet the file spec for llms.txt from ai-readiness

Cursor — add to .cursor/mcp.json:

json
{  "mcpServers": {    "ai-readiness": {      "url": "https://ai.silverbackmarketing.com/api/mcp"    }  }}

Refresh MCP servers, then ask: "Use ai-readiness to generate files for example.com"

Claude Code — add .mcp.json to your project root:

json
{  "mcpServers": {    "ai-readiness": {      "type": "http",      "url": "https://ai.silverbackmarketing.com/api/mcp"    }  }}

Or run:

bash
claude mcp add --transport http ai-readiness https://ai.silverbackmarketing.com/api/mcp

Restart the session, run /mcp, then ask: "Generate AI readiness files for mysite.com using ai-readiness"

VS Code / Copilot — add to .vscode/mcp.json:

json
{  "servers": {    "ai-readiness": {      "type": "http",      "url": "https://ai.silverbackmarketing.com/api/mcp"    }  }}

Open MCP: List Servers, confirm ai-readiness is running, then use agent mode in Copilot Chat.

Claude Desktop — use mcp-remote in ~/Library/Application Support/Claude/claude_desktop_config.json (macOS):

json
{  "mcpServers": {    "ai-readiness": {      "command": "npx",      "args": ["-y", "mcp-remote", "https://ai.silverbackmarketing.com/api/mcp"]    }  }}

Fully quit and reopen Claude Desktop after saving.

OpenAI Codex — add to ~/.codex/config.toml:

toml
[mcp_servers.ai-readiness]url = "https://ai.silverbackmarketing.com/api/mcp"enabled = true

Or run codex mcp add ai-readiness --url https://ai.silverbackmarketing.com/api/mcp, then /mcp in a session.

Antigravity — Agent panel → … → MCP Servers → Manage → View raw config:

json
{  "mcpServers": {    "ai-readiness": {      "serverUrl": "https://ai.silverbackmarketing.com/api/mcp"    }  }}

Antigravity uses serverUrl (not url). Save, refresh, then try in agent mode.

Perplexity — two ways to use the kit:

  • Via remote MCP connector — requires a paid Perplexity plan; an org admin may first need to enable "Allow members to add custom connectors." Go to Account settings → Connectors → click + Custom connector (top-right) → select Remote, then fill in:

    FieldValue
    NameAI Readiness
    MCP Server URLhttps://ai.silverbackmarketing.com/api/mcp
    AuthenticationNone
    TransportStreamable HTTP

    Check the acknowledgement box, click Add, then click the connector card to enable it. Ask: "Use ai-readiness to generate files for example.com." (Full steps: Perplexity's Adding Custom Remote Connectors guide.)

  • Manual — free, works on any plan: paste SKILL.md into a thread (or attach it), then ask: "Using these AI readiness instructions, generate AI readiness files for example.com."

Quick test:

bash
curl -X POST 'https://ai.silverbackmarketing.com/api/mcp' \  -H 'Content-Type: application/json' \  -H 'Accept: application/json, text/event-stream' \  -d '{"jsonrpc":"2.0","method":"tools/list","params":{},"id":1}'

More client configs: ai.silverbackmarketing.com/#mcp


What It Does

Run /ai-readiness yoursite.com and the AI will research the site, classify its industry, and generate production-ready files that tell AI systems (ChatGPT, Claude, Gemini, Perplexity, and others) exactly what the site is, what it offers, and where to send users.

When deployed to a web root, these files improve how a site appears in AI-generated answers, summaries, and recommendations — a must-have for any business that wants to show up in the AI-driven web.


The Files

The skill generates 18 files. Of these, 17 deploy to your web root across 7 categories (16 if you omit the optional .well-known/ai-plugin.json); the 18th, README.md, is project documentation for your team. This matches the 17-file kit described on the live site.

#FilePurposeDeployed
1ai.txtPrimary AI identity declaration✅
2llms.txtConcise LLM-readable site summary✅
3llms-full.txtComprehensive LLM knowledge base✅
4ai-sitemap.xmlAI-optimized sitemap✅
5sitemap.mdHuman-readable sitemap for AI context✅
6ai-entities.jsonStructured entity definitions✅
7ai-intent.jsonUser intent and query mappings✅
8ai-schema.jsonSchema.org structured data✅
9rag-index.jsonRAG retrieval knowledge base✅
10rag-index.jsonlJSONL format for embedding pipelines✅
11ai-disclosure.txtAI content transparency statement✅
12training-data-policy.txtData usage and training policy✅
13.well-known/ai-plugin.jsonPlugin manifest for AI agents (optional)➖
14structured-data-guide.mdImplementation guide for developers✅
15manifest.jsonWeb app manifest✅
16deployment-checklist.mdStep-by-step deployment guide✅
17robots.txtAI crawler directives✅
18README.mdProject documentation (not deployed)➖

Usage

In Claude Cowork, type:

/ai-readiness yoursite.com

Or use natural language:

create AI readiness files for acmecorp.commake my site AI-ready: hubspot.comgenerate llms.txt for shopify.com

Claude will:

  1. Run 10+ targeted searches to research the site
  2. Classify the site type (SaaS, e-commerce, education, healthcare, etc.)
  3. Generate all files tailored to that industry
  4. Save everything to a folder named after the domain in your workspace

FAQ

Getting Started

What are AI Readiness Files? They are structured files you deploy at the root of your website to tell AI systems exactly who you are, what you offer, and where to send people. They speak a format AI already understands, so assistants stop guessing about your brand based on old training data.

Why does AI readiness matter now? When someone wants a product recommendation, a service provider, or a straight answer, they often ask ChatGPT, Claude, Gemini, or Perplexity before they visit a website. If you are not giving those systems clear, current signals, they guess. And they often guess wrong.

How many files are in the kit? The kit includes 17 purpose-built files across 7 categories: Identity & Permissions, Content Files, Map & Navigation, Intelligence Files, Research Files, Policy Files, and Operations Files. Each one helps AI understand and represent your site more accurately. (The skill generates 18 files total — the extra one is this README.md for your project.)

Where should I start? Start with the critical files: robots.txt, ai.txt, llms.txt, and llms-full.txt. They deliver the biggest immediate impact and are what most AI systems look for first. Then add sitemaps, intelligence JSON files, policies, and operational files using the deployment checklist.

Identity & Permissions

What does robots.txt do for AI? robots.txt sits at the front door of your website and tells automated visitors (search engines, AI bots, and scrapers) which sections they can access. For AI readiness, it includes instructions for major crawlers like GPTBot, OAI-SearchBot, ClaudeBot, Claude-SearchBot, PerplexityBot, and Bingbot, pointing them toward your llms.txt and ai-sitemap.xml while keeping checkout, login, and admin pages off limits.

What is ai.txt? ai.txt is your brand's introduction to every AI system on the internet. Where robots.txt controls access, ai.txt goes further. It covers what you sell, what you are known for, your authoritative topics, and the rules for what AI systems can and cannot do with your content.

How is ai.txt different from robots.txt? robots.txt controls access: which pages bots can crawl. ai.txt controls identity: who you are, what you offer, and your ground rules for AI use of your content. Think of robots.txt as the doorman and ai.txt as the briefing document you hand a journalist before an interview.

Content & Navigation

What is llms.txt? llms.txt is a structured text file built for large language models. It gives AI a quick map of your website: company name, description, organized sections with direct links, and the most common questions your site answers. It follows the llmstxt.org standard used by ChatGPT, Claude, Gemini, and Perplexity.

What's the difference between llms.txt and llms-full.txt? llms.txt is the cheat sheet: a quick summary an AI can scan in seconds. llms-full.txt is the deep dive with rich descriptions, detailed Q&A, and full category explanations. If llms.txt is a Wikipedia summary, llms-full.txt is the full article.

Why do I need an ai-sitemap.xml? A regular sitemap lists pages and timestamps. The ai-sitemap adds what each page is about, its content type, and a plain-English summary. It is the difference between a paper road map and GPS with points of interest. AI crawlers can understand pages without fetching and parsing each one individually.

Intelligence & Research

What is ai-intent.json? ai-intent.json maps real user questions (the things people type into AI assistants) to the best page on your website to answer each one. Without it, AI guesses which page to recommend. With it, you give AI a direct URL for every common query.

What are ai-entities.json and ai-schema.json for? ai-entities.json is a structured catalog of the important parts of your site: products, categories, services, and key concepts. It powers AI knowledge graphs. ai-schema.json uses the Schema.org standard to describe your organization in machine-readable format so search engines and AI systems can identify you without ambiguity.

What are the RAG index files? rag-index.json and rag-index.jsonl are ready-made indexes of your site built for AI research and retrieval pipelines. When a user asks a question, AI first pulls the most relevant documents from this index before generating an answer, which keeps responses grounded in your actual content.

Policies & Maintenance

What is a training data policy? training-data-policy.txt sets formal rules for how AI companies can use your content, including model training, RAG indexing, and commercial use. It answers a practical question every brand should decide upfront: what are others allowed to do with your work?

What is ai-disclosure.txt? ai-disclosure.txt is a public transparency report explaining how your organization uses AI, whether for content generation, recommendations, or customer interactions. It builds trust by answering those questions before someone has to ask.

How often should I update my AI readiness files? It depends on the file. Update llms.txt and sitemaps monthly or when your site structure changes. Refresh ai.txt and llms-full.txt quarterly or when products change. Review policy files annually. The manifest.json file lists recommended update frequencies for every file in the kit.


Reference Documentation

The references/file-specs.md file contains the detailed specification for each file — required structure, key fields, and condensed examples. It is loaded automatically when the skill runs.

The scripts/gen_jsonl.py utility converts rag-index.json to rag-index.jsonl format for use with embedding pipelines:

bash
python3 scripts/gen_jsonl.py rag-index.json rag-index.jsonl

PDF Guides

The docs/ folder contains PDF reference guides explaining each file in plain English and technical detail:

GuideAudienceFiles Covered
AI Readiness Guide — With PluginGeneral / Non-technicalAll 17 files incl. ai-plugin.json
AI Readiness Guide — No PluginGeneral / Non-technical16 files excl. ai-plugin.json
Developer Reference — With PluginWeb DevelopersAll 17 files, compact technical format
Developer Reference — No PluginWeb Developers16 files, compact technical format

Skill File Structure

ai-readiness/├── ai-readiness.skill          ← Claude Cowork installable skill (download & open)├── SKILL.md                    ← Raw skill definition — works in any AI assistant├── README.md                   ← This file├── references/│   └── file-specs.md           ← Detailed specs for all output files├── scripts/│   └── gen_jsonl.py            ← JSONL generator utility└── docs/    ├── ai-readiness-guide-with-plugin.pdf    ├── ai-readiness-guide-no-plugin.pdf    ├── ai-readiness-guide-dev-with-plugin.pdf    └── ai-readiness-guide-dev-no-plugin.pdf

Author & Company

Russ Wittmann — SVP of Technology, Silverback Marketing LinkedIn · X / Twitter

Silverback Marketing of Queen Creek, Arizona is an ROI-focused digital marketing agency (founded 2007) helping businesses grow through strategy, content, and technology. This skill was built as part of Silverback's AI-readiness service offering: helping clients get found in the age of AI search.

🔗 ai.silverbackmarketing.com · silverbackmarketing.com


License

MIT — free to use, modify, and distribute with attribution. See LICENSE.

Source: README.md at commit 8abb78d

Tools

6

generate_ai_readiness_files

Start generating the 18 AI Readiness Kit files for a website. Returns the full workflow for the connected agent to execute (research, classify, write files).

Parametersurlrequired

list_output_files

List all 18 AI readiness files in generation order with filenames and purposes

Takes no parameters.

get_file_spec

Get the detailed specification for one AI readiness output file (e.g. llms.txt, ai-entities.json)

Parametersfilenamerequired

get_skill_instructions

Return the full AI Readiness skill workflow (research, classification, file generation)

Takes no parameters.

get_site_classification_guide

Return the site-type classification table used before generating files

Takes no parameters.

generate_rag_jsonl

Convert rag-index.json content (JSON array) to rag-index.jsonl (one JSON object per line)

Parametersrag_index_jsonrequired

Version history

1
  1. v1.0.0LatestSep 16, 2026

Score

90% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listedRequired15 pts
  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts

    Declare a license in the repository or the registry entry.