geo-llmstxt

Name: geo-llmstxt
Author: zubair-trabzada

9.1kstars1.4kforks

How to install geo-llmstxt?

zubair-trabzada/geo-seo-claude/geo-llmstxt

$npx -y skills add zubair-trabzada/geo-seo-claude --skill geo-llmstxt

Installs into the current project.

Summary

Analyzes and generates llms.txt files -- the emerging standard for helping AI systems understand website structure and content. Can validate existing llms.txt files or generate new ones from scratch by crawling the site.

Files · 1

View on GitHub

SKILL.md

1	# llms.txt Standard Analysis and Generation Skill
2
3	## Purpose
4
5	This skill handles everything related to the `llms.txt` standard -- an emerging convention (proposed by Jeremy Howard in September 2024, gaining adoption through 2025-2026) that allows websites to provide structured guidance to AI systems about their content, structure, and key information. It is analogous to `robots.txt` (which tells crawlers what NOT to access) but instead tells AI systems what IS most useful to understand about the site.
6
7	## Why llms.txt Matters
8
9	AI language models face a fundamental challenge when processing websites: they must determine which pages are most important, what the site is about, and how content is organized -- typically by crawling many pages and inferring structure. `llms.txt` solves this by providing an explicit, machine-readable (and human-readable) summary.
10
11	Benefits of having a well-crafted llms.txt:
12
13	1. Faster AI comprehension: AI systems can understand your site's purpose and structure from a single file rather than crawling dozens of pages.
14	2. Controlled narrative: You choose which pages and facts AI systems see first, shaping how they represent your brand.
15	3. Higher citation accuracy: AI systems that consult llms.txt can cite the correct, authoritative page for each topic.
16	4. Reduced misrepresentation: Key facts (pricing, features, locations) are stated explicitly, reducing AI hallucination about your business.
17	5. Early adopter advantage: As of early 2026, fewer than 5% of websites have an llms.txt file, making it a differentiator.
18
19	---
20
21	## The llms.txt Specification
22
23	### File Location
24
25	The file MUST be located at the root of the domain:
26	```
27	https://example.com/llms.txt
28	```
29
30	### Format Specification
31
32	The file uses Markdown formatting with specific conventions:
33
34	```markdown
35	# [Site Name]
36
37	> [One-sentence description of what the site/business does. Keep under 200 characters.]
38
39	## Docs
40
41	- [Page Title](https://example.com/page-url): Concise description of what this page covers and why it matters.
42	- [Another Page](https://example.com/another-page): Description of content.
43
44	## Optional
45
46	- [Less Critical Page](https://example.com/optional-page): Description.
47	```
48
49	### Detailed Format Rules
50
51	1. Title (Required)
52	```markdown
53	# Site Name
54	```
55	- Must be the first line of the file.
56	- Should be the official business/site name.
57	- Use the H1 heading format (single `#`).
58
59	2. Description (Required)
60	```markdown
61	> Brief description of the site/business
62	```
63	- Must appear immediately after the title.
64	- Use Markdown blockquote format (`>`).
65	- Keep under 200 characters.
66	- Should clearly state what the business does and who it serves.
67	- Avoid marketing fluff -- be factual and specific.
68
69	3. Main Sections (Required -- at least one)
70
71	Use H2 headings (`##`) to organize pages by category. Common section names:
72
73	\| Section Name \| Purpose \| Example Content \|
74	\|---\|---\|---\|
75	\| `## Docs` \| Primary documentation or key pages \| Product pages, service descriptions, core content \|
76	\| `## Optional` \| Secondary pages worth knowing about \| Blog posts, supplementary resources \|
77	\| `## API` \| API documentation \| API reference, authentication guides \|
78	\| `## Blog` \| Blog or news content \| Recent/popular articles \|
79	\| `## Products` \| Product catalog \| Product pages, pricing \|
80	\| `## Services` \| Service offerings \| Service descriptions, process pages \|
81	\| `## About` \| Company information \| About page, team, mission \|
82	\| `## Resources` \| Educational/reference content \| Guides, tutorials, whitepapers \|
83	\| `## Legal` \| Legal documents \| Terms of service, privacy policy \|
84	\| `## Contact` \| Contact information \| Contact page, support channels \|
85
86	4. Page Entries (Required)
87
88	Each entry follows the format:
89	```markdown
90	- [Page Title](URL): Description of page content
91	```
92
93	Rules for page entries:
94	- Title: Use the actual page title or a clear descriptive title.
95	- URL: Must be a full, absolute URL (not relative paths).
96	- Description: 10-30 words describing what the page covers. Be specific about the information available.
97	- Order: List pages in order of importance within each section.
98	- Limit: Include 10-30 page entries total. Prioritize your most authoritative and useful pages.
99
100	5. Key Facts Section (Recommended)
101
102	```markdown
103	## Key Facts
104	- Founded in [year] by [founder(s)]
105	- Headquarters: [City, Country]
106	- [X] customers/users in [Y] countries
107	- Key products: [Product A], [Product B], [Product C]
108	- Industry: [Industry classification]
109	```
110
111	This section provides quick reference data that AI systems frequently need to answer user queries about your business.
112
113	**6. Contact Section (Re

People who liked this also viewed

6 picks

Type

geo-llmstxt

9.1kstars1.4kforks

View on GitHub

How to install geo-llmstxt?

zubair-trabzada/geo-seo-claude/geo-llmstxt

$npx -y skills add zubair-trabzada/geo-seo-claude --skill geo-llmstxt

Installs into the current project.

Summary

Files · 1

View on GitHub

SKILL.md

1	# llms.txt Standard Analysis and Generation Skill
2
3	## Purpose
4
5	This skill handles everything related to the `llms.txt` standard -- an emerging convention (proposed by Jeremy Howard in September 2024, gaining adoption through 2025-2026) that allows websites to provide structured guidance to AI systems about their content, structure, and key information. It is analogous to `robots.txt` (which tells crawlers what NOT to access) but instead tells AI systems what IS most useful to understand about the site.
6
7	## Why llms.txt Matters
8
9	AI language models face a fundamental challenge when processing websites: they must determine which pages are most important, what the site is about, and how content is organized -- typically by crawling many pages and inferring structure. `llms.txt` solves this by providing an explicit, machine-readable (and human-readable) summary.
10
11	Benefits of having a well-crafted llms.txt:
12
13	1. Faster AI comprehension: AI systems can understand your site's purpose and structure from a single file rather than crawling dozens of pages.
14	2. Controlled narrative: You choose which pages and facts AI systems see first, shaping how they represent your brand.
15	3. Higher citation accuracy: AI systems that consult llms.txt can cite the correct, authoritative page for each topic.
16	4. Reduced misrepresentation: Key facts (pricing, features, locations) are stated explicitly, reducing AI hallucination about your business.
17	5. Early adopter advantage: As of early 2026, fewer than 5% of websites have an llms.txt file, making it a differentiator.
18
19	---
20
21	## The llms.txt Specification
22
23	### File Location
24
25	The file MUST be located at the root of the domain:
26	```
27	https://example.com/llms.txt
28	```
29
30	### Format Specification
31
32	The file uses Markdown formatting with specific conventions:
33
34	```markdown
35	# [Site Name]
36
37	> [One-sentence description of what the site/business does. Keep under 200 characters.]
38
39	## Docs
40
41	- [Page Title](https://example.com/page-url): Concise description of what this page covers and why it matters.
42	- [Another Page](https://example.com/another-page): Description of content.
43
44	## Optional
45
46	- [Less Critical Page](https://example.com/optional-page): Description.
47	```
48
49	### Detailed Format Rules
50
51	1. Title (Required)
52	```markdown
53	# Site Name
54	```
55	- Must be the first line of the file.
56	- Should be the official business/site name.
57	- Use the H1 heading format (single `#`).
58
59	2. Description (Required)
60	```markdown
61	> Brief description of the site/business
62	```
63	- Must appear immediately after the title.
64	- Use Markdown blockquote format (`>`).
65	- Keep under 200 characters.
66	- Should clearly state what the business does and who it serves.
67	- Avoid marketing fluff -- be factual and specific.
68
69	3. Main Sections (Required -- at least one)
70
71	Use H2 headings (`##`) to organize pages by category. Common section names:
72
73	\| Section Name \| Purpose \| Example Content \|
74	\|---\|---\|---\|
75	\| `## Docs` \| Primary documentation or key pages \| Product pages, service descriptions, core content \|
76	\| `## Optional` \| Secondary pages worth knowing about \| Blog posts, supplementary resources \|
77	\| `## API` \| API documentation \| API reference, authentication guides \|
78	\| `## Blog` \| Blog or news content \| Recent/popular articles \|
79	\| `## Products` \| Product catalog \| Product pages, pricing \|
80	\| `## Services` \| Service offerings \| Service descriptions, process pages \|
81	\| `## About` \| Company information \| About page, team, mission \|
82	\| `## Resources` \| Educational/reference content \| Guides, tutorials, whitepapers \|
83	\| `## Legal` \| Legal documents \| Terms of service, privacy policy \|
84	\| `## Contact` \| Contact information \| Contact page, support channels \|
85
86	4. Page Entries (Required)
87
88	Each entry follows the format:
89	```markdown
90	- [Page Title](URL): Description of page content
91	```
92
93	Rules for page entries:
94	- Title: Use the actual page title or a clear descriptive title.
95	- URL: Must be a full, absolute URL (not relative paths).
96	- Description: 10-30 words describing what the page covers. Be specific about the information available.
97	- Order: List pages in order of importance within each section.
98	- Limit: Include 10-30 page entries total. Prioritize your most authoritative and useful pages.
99
100	5. Key Facts Section (Recommended)
101
102	```markdown
103	## Key Facts
104	- Founded in [year] by [founder(s)]
105	- Headquarters: [City, Country]
106	- [X] customers/users in [Y] countries
107	- Key products: [Product A], [Product B], [Product C]
108	- Industry: [Industry classification]
109	```
110
111	This section provides quick reference data that AI systems frequently need to answer user queries about your business.
112
113	**6. Contact Section (Re

People who liked this also viewed

6 picks

Type