llmstxtlisted

# llms.txt A small convention from [llmstxt.org](https://llmstxt.org/): one H1, a blockquote summary, then H2 sections of markdown links. It is not a standard and no engine is known to require it. What it is good for is stating your own priorities, in your own words, in a place a model will look. Be honest about that when someone asks whether it is worth doing. ## Preflight Run this first, once per session: ```bash geo --version ``` Expected: `seomator-geo-audit 1.2.x` or newer. - **Command not found** -> stop and say: "The geo CLI is not installed. Install it with `uv tool install seomator-geo-audit` (or `pipx install seomator-geo-audit`), then run this again." - **Older than 1.2.0** -> stop and say: "This skill needs seomator-geo-audit 1.2.0 or newer. Upgrade with `uv tool upgrade seomator-geo-audit`." - **Anything else odd** -> run `geo doctor` and relay what it reports. ## Run ```bash geo llmstxt <url> --json # check what exists geo llmstxt <url> --generate --json # build one from the site geo llmstxt <url> --generate --out llms.txt # and write it to a file ``` `--generate` crawls, so the crawl flags apply: `--max-pages`, `--rate`, `--no-sitemap`. ## Read the envelope `llmstxt.llms_txt` reports `present`, `valid`, and a `problems` list naming each structural fault. `llmstxt.llms_full_txt` reports only whether the longer variant exists. `llmstxt.generated` carries the proposed file: | Field | Meaning | |---|---| | `text`