agentleFS
UXMagicaiUXMagicai/seosorted-skills/skills/llms-txt-generator/SKILL.md

llms-txt-generator

Skill0 starsChanged 40 days agoMITView on GitHub

Free tool to generate an llms.txt file for a website — a curated, markdown map of the site's most important pages that helps AI assistants and LLM crawlers understand and cite it — no account needed. Use when the user asks for llms.txt, an AI-readable site summary, how to help ChatGPT or Claude understand their site, or GEO/AEO quick wins.

5 other projects use a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

1 rule. 0 are common, 1 is distinctive, and 0 are very specific to this project.

  • 0

    Common

    Most of the 4 edited versions we read keep these.

  • 1

    Distinctive

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Write the file in this format:

    line 16

“Common” is measured: kept by at least 6 in 10 of the 4 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

llms.txt generator (free)

llms.txt sits at https://<domain>/llms.txt and gives language models a short, curated index of the site in markdown (proposed standard: https://llmstxt.org).

Steps

  1. Fetch the home page, /sitemap.xml (or the sitemap from robots.txt), and the main navigation. With SEOsorted connected, audit_any_page operation: "sitemap" with the site url finds and reads the sitemap for you (free).
  2. Pick the pages that matter most: product/service pages, pricing, docs or guides, about, contact, and the 10–20 best articles. Skip tag pages, pagination, legal boilerplate (except a privacy/terms link in "Optional").
  3. Fetch each chosen page's title and write a one-line description of what it answers, in plain language.
  4. Write the file in this format:
# <Site name>

> <One or two sentences: what the business does and for whom.>

<Optional short paragraph with key facts: locations, audience, what it does not do.>

## Products
- [Page title](https://example.com/page): What this page answers.

## Guides
- [Article title](https://example.com/blog/post): What this article answers.

## Optional
- [Privacy policy](https://example.com/privacy)
  1. Return the file and tell the user to upload it to the site root, then link it from nowhere in particular — crawlers look for it by path.

With an SEOsorted account, ai-crawler-analytics shows which AI bots then fetch it.

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.