Frontend · Skill

Add an llms.txt file

add-llms-txt-file

Writes an llms.txt file for a website or repo following the llmstxt.org format - a title, a one-line summary, short context and grouped links to the pages that matter - so AI assistants and AI search tools can find your key content. Use when the user wants an llms.txt, wants their docs readable by AI, or asks how AI tools should read their site.

Works with: Any AI Not yet model-tested; testing Jan 2027

Paste it into ChatGPT, Claude, Gemini or any AI chat, then tell it about your project. How it works

Install in Claude Code, Cursor or Codex (optional)

Only for AI coding tools that read skill folders. Run one line in a terminal, in your project folder. It downloads this skill's text files from TheSkillVault and nothing else; you can read them first with “View raw SKILL.md”.

Claude Code (all your projects)

curl -fsSL --create-dirs 'https://theskillvault.ai/api/skills/add-llms-txt-file/raw' -o ~/'.claude/skills/add-llms-txt-file/SKILL.md' && curl -fsSL --create-dirs 'https://theskillvault.ai/api/skills/add-llms-txt-file/files/LICENSE.txt' -o ~/'.claude/skills/add-llms-txt-file/LICENSE.txt'

Cursor (this project)

curl -fsSL --create-dirs 'https://theskillvault.ai/api/skills/add-llms-txt-file/raw' -o '.cursor/skills/add-llms-txt-file/SKILL.md' && curl -fsSL --create-dirs 'https://theskillvault.ai/api/skills/add-llms-txt-file/files/LICENSE.txt' -o '.cursor/skills/add-llms-txt-file/LICENSE.txt'

Codex and other Agent Skills tools (this project)

curl -fsSL --create-dirs 'https://theskillvault.ai/api/skills/add-llms-txt-file/raw' -o '.agents/skills/add-llms-txt-file/SKILL.md' && curl -fsSL --create-dirs 'https://theskillvault.ai/api/skills/add-llms-txt-file/files/LICENSE.txt' -o '.agents/skills/add-llms-txt-file/LICENSE.txt'

Or connect the whole library over MCP

Add TheSkillVault to Cursor or add this to your app's MCP settings (read-only; help):

{
  "mcpServers": {
    "theskillvault": {
      "url": "https://theskillvault.ai/mcp"
    }
  }
}

llms.txt is a short Markdown file at the root of your site that points AI tools at your most useful pages. It is a proposal at llmstxt.org, not a ranking signal, so treat it as cheap, helpful extra.

When to use

  • You run docs, an API or a product site that people ask AI tools about.
  • You want AI assistants to read your pricing, docs and guides first.
  • A repo needs a quick map for coding agents.

When not to use

  • You want Google rankings. Use add-seo-metadata-and-sitemap; llms.txt does not replace a sitemap.

Steps

  1. List the 10-30 pages that best explain what you offer: overview, getting started, docs, API, pricing, FAQ.
  2. Start the file with # Name as the only H1.
  3. Add a one-line summary as a > blockquote.
  4. Add a short paragraph of context: who it is for and anything an AI often gets wrong.
  5. Group links under ## headings, one per line: - Title: what it covers.
  6. Put lower-priority links under ## Optional, which tools may skip.
  7. Save it as /llms.txt at the site root (in public/ for most frameworks) and check it loads as plain text.
  8. Optionally add /llms-full.txt with the full text of key pages.
  9. Add a reminder to update it when pages move.
# Acme Invoices

> Simple invoicing for freelancers: create, send and track invoices.

Acme is a web app. It has no desktop version. Prices are in AUD.

## Docs
- [Getting started](https://acme.example/docs/start): create your first invoice
- [API](https://acme.example/docs/api): REST endpoints and auth

## Optional
- [Changelog](https://acme.example/changelog): release notes

Gotchas

  • Every link must work. Broken links teach AI tools wrong things.
  • Do not list private, admin or paid-only pages, or anything with tokens in the URL.
  • Keep it short. A list of every page is a sitemap, not an llms.txt.
  • Claims you would not put on your homepage do not belong here either.

Portability

Works with any site or framework: it is a static text file. If you use a docs tool such as Mintlify or Docusaurus, check for a plugin that generates it instead of writing it by hand.

Example prompt

"Write an llms.txt for my SaaS site with links to the docs, pricing and API pages, and put it where my Next.js app will serve it."

Done when

  • /llms.txt loads as plain text with one H1, a summary and grouped links.
  • Every link resolves and none point at private pages.

---

Adapted from "create-llms" in github/awesome-copilot (MIT, Copyright GitHub, Inc.). See LICENSE.txt.

Bundled files

Licence

Adapted from GitHub awesome-copilot contributors (create-llms) (Copyright GitHub, Inc.), MIT License. Adapted by TheSkillVault: shortened from a repository-analysis procedure to a site-owner workflow with an original example file; added honesty about what llms.txt does and does not do, privacy notes, gotchas and done-when.

Licence: MIT License. Attribution when you reuse it: Based on work by GitHub awesome-copilot contributors (create-llms) (Copyright GitHub, Inc., MIT License), https://github.com/github/awesome-copilot/tree/5269f7ea2d6c3a9bfda5ed878b6726cf509121fd/skills/create-llms; adapted by TheSkillVault, https://theskillvault.ai