geo-llmstxt
Analyzes and generates llms.txt files -- a lightweight anti-hallucination facts hedge that tells AI systems your canonical business facts and key pages. NOT an AI-visibility or citation lever (debunked by Google, Zyppy, and SE Ranking). Can validate existing llms.txt files or generate new ones from scratch by crawling the site.
TheSmokeDev · Static checks on file
Installation
Read the source and dependencies before running a command. Copying does not install or execute anything.
npx skills add TheSmokeDev/geo-skills --skill geo-llmstxtAbout this skill
name: geo-llmstxt description: Analyzes and generates llms.txt files -- a lightweight anti-hallucination facts hedge that tells AI systems your canonical business facts and key pages. NOT an AI-visibility or citation lever (debunked by Google, Zyppy, and SE Ranking). Can validate existing llms.txt files or generate new ones from scratch by crawling the site. allowed-tools:
- Read
- Grep
- Glob
- Bash
- WebFetch
- Write
llms.txt Standard Analysis and Generation Skill
Purpose
This skill handles everything related to the llms.txt convention (proposed by Jeremy Howard in September 2024) -- a single Markdown file at the domain root that states your canonical business facts and points at your most important pages.
Positioning as of August 2026: llms.txt is a 30-minute anti-hallucination facts hedge, NOT an AI-visibility lever. Do not sell it to clients as a ranking or citation play -- the evidence says it does not move citations:
- Google Search Central, 2026 (official): "You don't need to create new machine readable files... to appear in generative AI search." Google has stated plainly that no AI-specific file is required or rewarded.
- Zyppy meta-analysis of 54 studies (via digitalapplied.com, Jun 2026): llms.txt scores 2.0 out of 10 -- the lowest of all 23 measured GEO factors.
- SE Ranking (seranking.com/blog/llms-txt, Nov 2025): found zero correlation between having an llms.txt file and AI citation/visibility.
What llms.txt Is Actually For
What remains is real but modest. A well-crafted llms.txt is worth roughly 30 minutes of effort because it:
- Reduces misrepresentation: Key facts (pricing, features, locations, founding date) are stated explicitly in one place, reducing AI hallucination about your business when a system does consult the file.
- Controls the narrative: You choose which pages and facts are presented as canonical, rather than leaving inference to a crawler.
- Costs almost nothing: It is a single static Markdown file. There is no maintenance burden beyond updating it when facts change.
What it does not do: improve rankings, increase citation rates, or substitute for indexation, crawlability, or content quality. Treat it as hygiene -- like a favicon or a humans.txt with a purpose -- and never present it in an audit as a visibility win.
The llms.txt Specification
File Location
The file MUST be located at the root of the domain:
https://example.com/llms.txt
Format Specification
The file uses Markdown formatting with specific conventions:
# [Site Name]
> [One-sentence description of what the site/business does. Keep under 200 characters.]
## Docs
- [Page Title](https://example.com/page-url): Concise description of what this page covers and why it matters.
- [Another Page](https://example.com/another-page): Description of content.
## Optional
- [Less Critical Page](https://example.com/optional-page): Description.
Detailed Format Rules
1. Title (Required)
# Site Name
- Must be the first line of the file.
- Should be the official business/site name.
- Use the H1 heading format (single
#).
2. Description (Required)
> Brief description of the site/business
- Must appear immediately after the title.
- Use Markdown blockquote format (
>). - Keep under 200 characters.
- Should clearly state what the business does and who it serves.
- Avoid marketing fluff -- be factual and specific.
3. Main Sections (Required -- at least one)
Use H2 headings (##) to organize pages by category. Common section names:
| Section Name | Purpose | Example Content |
|---|---|---|
## Docs | Primary documentation or key pages | Product pages, service descriptions, core content |
## Optional | Secondary pages worth knowing about | Blog posts, supplementary resources |
## API | API documentation | API reference, authentication guides |
## Blog | Blog or news content | Recent/popular articles |
## Products | Product catalog | Product pages, pricing |
## Services | Service offerings | Service descriptions, process pages |
## About | Company information | About page, team, mission |
## Resources | Educational/reference content | Guides, tutorials, whitepapers |
## Legal | Legal documents | Terms of service, privacy policy |
## Contact | Contact information | Contact page, support channels |
4. Page Entries (Required)
Each entry follows the format:
- [Page Title](URL): Description of page content
Rules for page entries:
- Title: Use the actual page title or a clear descriptive title.
- URL: Must be a full, absolute URL (not relative paths).
- Description: 10-30 words describing what the page covers. Be specific about the information available.
- Order: List pages in order of importance within each section.
- Limit: Include 10-30 page entries total. Prioritize your most authoritative and useful pages.
5. Key Facts Section (Recommended)
## Key Facts
- Founded in [year] by [founder(s)]
- Headquarters: [City, Country]
- [X] customers/users in [Y] countries
- Key products: [Product A], [Product B], [Product C]
- Industry: [Industry classification]
This section provides quick reference data that AI systems frequently need to answer user queries about your business.
6. Contact Section (Recommended)
## Contact
- Website: https://example.com
- Email: hello@example.com
- Support: support@example.com
- Phone: +1-555-123-4567
- Address: 123 Main St, City, State, ZIP, Country
llms-full.txt (Extended Version)
In addition to llms.txt, sites can provide /llms-full.txt -- an extended version with more detail.
Differences from llms.txt:
| Feature | llms.txt | llms-full.txt |
|---|---|---|
| Length | Concise (50-150 lines) | Comprehensive (150-500+ lines) |
| Page entries | 10-30 key pages | 30 |