Agent skill

llms.txt Analyzer and Generator

by zubair-trabzada in zubair-trabzada/geo-seo-claude

Validates an existing llms.txt file or crawls a site to generate a new one, following the format rules for a root-level Markdown file aimed at AI systems.

MITAuto-check: notesMarketing & SEO

Install llms.txt Analyzer and Generator

skills CLI
$ npx skills add zubair-trabzada/geo-seo-claude --skill geo-llmstxt -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install zubair-trabzada/geo-seo-claude geo-llmstxt --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/zubair-trabzada/geo-seo-claude.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/geo-llmstxt .claude/skills/geo-llmstxt && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
geo-llmstxt
GitHub stars
11k
Used in
2 other repos
Token cost
~3.9k tokens
SKILL.md length
1,580 words
Files
1
Skills in repo
16
Repo updated
First seen
Licence
MIT

At a glance

Validates an existing llms.txt file or crawls a site to generate a new one, following the format rules for a root-level Markdown file aimed at AI systems.

  • Works in 10 steps: Fetch the File → Validate Format → Assess Content Quality → …
  • Checking whether a site's llms.txt follows the format rules
  • SKILL.md covers Purpose, Why llms.txt Matters, The llms.txt Specification and llms-full.txt (Extended Version), plus 4 more sections
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

llms.txt is a proposed convention, introduced by Jeremy Howard in September 2024, in which a site publishes a Markdown summary of its purpose and key pages for AI systems. It resembles robots.txt but describes what is most useful instead of what to avoid. This skill handles both directions: auditing a file that already exists and building a new one by crawling the site.

The rules it works from say the file lives at the domain root, opens with the site name as a single H1 heading, and follows it with a short blockquote description under 200 characters that is factual and specific. The allowed tools let the agent read and search local files, fetch web pages and write the result to disk. It belongs to a wider set of generative engine optimization checks for websites.

When your agent uses it

  • Checking whether a site's llms.txt follows the format rules
  • Generating an llms.txt for a site that has none
  • Preparing a site's key pages so AI systems can find them quickly

Example prompts

  • “Validate the llms.txt on example.com and list what needs fixing.”
  • “Crawl my docs site and generate an llms.txt for it.”
  • “Does my llms.txt description stay under the length limit?”

Requirements

  • Network access to fetch and crawl the target website
  • Pre-approved tools (allowed-tools): Read, Grep, Glob, Bash, WebFetch, Write

Workflow steps

10 steps, taken from the step headings in SKILL.md.

  1. Fetch the File
  2. Validate Format
  3. Assess Content Quality
  4. Compare Against Site Content
  5. Site Discovery
  6. Page Prioritization
  7. Write Descriptions
  8. Compile Key Facts
  9. Assemble the File
  10. Validate the Generated File

What it can do on your machine

Read from SKILL.md and the folder at commit 989cae0. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves these tools, so the agent can use them without asking each time:

    • Read
    • Grep
    • Glob
    • Bash
    • WebFetch
    • Write

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md (its code samples are markdown).

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

llms.txt Analyzer and Generator loads about 3.9k tokens when it runs. Until then it costs about 58 tokens; SKILL.md has 1,580 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~58
When it runs · the whole SKILL.md, loaded when a task matches
~3.9k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check: notes

The automated check noted patterns worth knowing about, such as sudo or a known installer.

  • NotePre-approves every shell command (allowed-tools: Bash)SKILL.md
    allowed-tools: Read, Grep, Glob, Bash, WebFetch, Write

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from zubair-trabzada/geo-seo-claude at commit 989cae0, republished under its MIT licence (© zubair-trabzada). 1,580 words, ~3,935 tokens.

Download SKILL.mdSave it as .claude/skills/geo-llmstxt/SKILL.md (or your agent's skills folder).
name
geo-llmstxt
description
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.
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 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.

Why llms.txt Matters

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.

Benefits of having a well-crafted llms.txt:

  1. Faster AI comprehension: AI systems can understand your site's purpose and structure from a single file rather than crawling dozens of pages.
  2. Controlled narrative: You choose which pages and facts AI systems see first, shaping how they represent your brand.
  3. Higher citation accuracy: AI systems that consult llms.txt can cite the correct, authoritative page for each topic.
  4. Reduced misrepresentation: Key facts (pricing, features, locations) are stated explicitly, reducing AI hallucination about your business.
  5. Early adopter advantage: As of early 2026, fewer than 5% of websites have an llms.txt file, making it a differentiator.

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:

markdown
# [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)

markdown
# 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)

markdown
> 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 NamePurposeExample Content
## DocsPrimary documentation or key pagesProduct pages, service descriptions, core content
## OptionalSecondary pages worth knowing aboutBlog posts, supplementary resources
## APIAPI documentationAPI reference, authentication guides
## BlogBlog or news contentRecent/popular articles
## ProductsProduct catalogProduct pages, pricing
## ServicesService offeringsService descriptions, process pages
## AboutCompany informationAbout page, team, mission
## ResourcesEducational/reference contentGuides, tutorials, whitepapers
## LegalLegal documentsTerms of service, privacy policy
## ContactContact informationContact page, support channels

4. Page Entries (Required)

Each entry follows the format:

markdown
- [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)

markdown
## 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)

markdown
## 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:

Featurellms.txtllms-full.txt
LengthConcise (50-150 lines)Comprehensive (150-500+ lines)
Page entries10-30 key pages30-100+ pages
Descriptions10-30 words per entry30-100 words per entry, may include key facts from each page
AudienceQuick AI comprehensionDeep AI analysis
Sections3-6 sections8-15 sections
Key factsBusiness-level factsPage-level facts and data points

Both files can coexist. AI systems check for llms.txt first, then may optionally load llms-full.txt for deeper understanding.


Analysis Mode

When checking an existing llms.txt file:

Step 1: Fetch the File
  1. Use WebFetch to retrieve [domain]/llms.txt.
  2. Also check for [domain]/llms-full.txt.
  3. Record HTTP status code:
    • 200: File exists -- proceed to validation.
    • 404: File does not exist -- recommend generation.
    • 403: File exists but is blocked -- flag as misconfiguration.
    • 301/302: Redirect -- follow and note the redirect.
Step 2: Validate Format

Check each structural element:

ElementCheckSeverity if Missing
H1 TitlePresent, matches business nameCritical
Blockquote descriptionPresent, under 200 chars, factualHigh
At least one H2 sectionPresentCritical
Page entries with URLsAt least 5 entries presentHigh
URLs are absoluteAll URLs use full https:// pathsHigh
URLs are validAll URLs return 200 statusMedium
Descriptions presentEvery entry has a description after the colonMedium
Key Facts sectionPresent with business informationMedium
Contact sectionPresent with at least emailLow
Reasonable length30-200 linesLow
No broken MarkdownProper formatting throughoutMedium
Step 3: Assess Content Quality

Rate the llms.txt on these dimensions:

Completeness (0-100):

  • Does it cover all major site sections visible in the navigation?
  • Are the most important/highest-traffic pages included?
  • Is the Key Facts section present with accurate business data?
  • Does it include recent/updated content?

Accuracy (0-100):

  • Do descriptions accurately reflect page content?
  • Are URLs valid and pointing to the correct pages?
  • Are Key Facts verifiable and current?
  • Is the business description accurate?

Usefulness (0-100):

  • Would an AI system understand the site's purpose from this file alone?
  • Are descriptions specific enough to differentiate pages?
  • Are the most citation-worthy pages highlighted?
  • Is the organization logical and intuitive?

Overall llms.txt Score = (Completeness * 0.40) + (Accuracy * 0.35) + (Usefulness * 0.25)

Step 4: Compare Against Site Content
  1. Crawl the site's main navigation and sitemap.
  2. Identify important pages NOT listed in llms.txt.
  3. Check if any listed URLs are broken or redirected.
  4. Verify that the business description matches current homepage messaging.
  5. Flag stale entries (pages that have been significantly updated since the llms.txt was written).

Generation Mode

When creating a new llms.txt file from scratch:

Show full SKILL.md (633 more words)Show less
Step 1: Site Discovery
  1. Fetch the homepage and extract:
    • Site name (from <title>, <meta property="og:site_name">, or H1)
    • Business description (from meta description or hero section)
    • Main navigation links
    • Footer links
  2. Fetch /sitemap.xml to discover all public pages.
  3. Identify the site's primary business type (SaaS, E-commerce, Local, Publisher, Agency).
Step 2: Page Prioritization

Categorize all discovered pages and select the most important ones:

Always Include:

  • Homepage
  • About / Company page
  • Pricing page (if exists)
  • Primary product/service pages (top 3-5)
  • Contact page
  • Documentation landing page (if exists)

Include if High Quality:

  • Top blog posts (by apparent importance, recency, or comprehensiveness)
  • Case studies or customer stories
  • Key resource/guide pages
  • FAQ page
  • Careers page (for large companies)

Skip:

  • Thin category/tag pages
  • Pagination pages
  • Login/signup pages
  • Legal boilerplate (unless specifically relevant)
  • Duplicate or near-duplicate content
  • Pages with minimal unique content
Step 3: Write Descriptions

For each selected page:

  1. Fetch the page content using WebFetch.
  2. Read the H1, meta description, and first 2-3 paragraphs.
  3. Write a description that:
    • Is 10-30 words long
    • States what information is on the page
    • Mentions specific topics, data, or features covered
    • Avoids marketing language ("best," "leading," "revolutionary")
    • Uses factual, informative language

Good description examples:

  • Explains the three pricing tiers (Free, Pro, Enterprise) with feature comparison and annual/monthly costs.
  • Details the company's founding in 2018, team of 45 employees, and office locations in Austin and London.
  • Covers integration setup for Slack, Salesforce, and HubSpot with step-by-step guides and API endpoints.

Bad description examples:

  • Our amazing pricing page! (marketing language, no specifics)
  • Learn more about our company. (too vague)
  • Click here for details. (not descriptive)
Step 4: Compile Key Facts

Gather key business facts from the site:

  • Year founded
  • Founder name(s)
  • Headquarters location
  • Number of employees (if public)
  • Number of customers/users (if public)
  • Key products or services (list top 3-5)
  • Industry classification
  • Notable clients or partnerships (if public)
  • Key differentiators (what makes this business unique)
  • Recent milestones or achievements (last 12 months)
Step 5: Assemble the File

Construct the llms.txt following this template:

markdown
# [Site Name]

> [One clear sentence: what the business does, who it serves, and its primary value proposition. Under 200 characters.]

## Docs

- [Most Important Page](https://example.com/page): Description covering the key content on this page.
- [Second Page](https://example.com/page-2): Description of this page's content and value.
- [Third Page](https://example.com/page-3): What users and AI systems will find here.

## Products

- [Product A](https://example.com/product-a): Core features, target users, and pricing model for Product A.
- [Product B](https://example.com/product-b): What Product B does and how it differs from Product A.

## Resources

- [Guide Title](https://example.com/guide): Comprehensive guide covering [topic] with [X] sections and practical examples.
- [Blog Post](https://example.com/blog/post): Analysis of [topic] with original data from [source].

## Key Facts

- Founded in [year] by [name(s)]
- Headquartered in [City, Country]
- [Specific metric: e.g., "Serves 10,000+ businesses in 40 countries"]
- [Key differentiator: e.g., "Only platform offering real-time X and Y integration"]
- Industry: [Classification]

## Contact

- Website: https://example.com
- Email: [primary contact email]
- Support: [support URL or email]
Step 6: Validate the Generated File

Before outputting:

  1. Verify all URLs are reachable (200 status).
  2. Confirm total entry count is between 10-30.
  3. Check that no description exceeds 50 words.
  4. Verify the overall file length is 50-150 lines.
  5. Ensure Markdown formatting is clean and consistent.

Output Format

For Analysis Mode

Generate GEO-LLMSTXT-ANALYSIS.md:

markdown
# llms.txt Analysis: [Domain]

**Analysis Date:** [Date]
**llms.txt Status:** [Found at URL / Not Found / Error]
**llms-full.txt Status:** [Found / Not Found]

---

## Overall llms.txt Score: [X]/100

| Dimension | Score |
|---|---|
| Completeness | [X]/100 |
| Accuracy | [X]/100 |
| Usefulness | [X]/100 |

---

## Format Validation

| Element | Status | Notes |
|---|---|---|
| H1 Title | [Pass/Fail] | [Notes] |
| Description blockquote | [Pass/Fail] | [Notes] |
| H2 Sections | [Pass/Fail] | [X sections found] |
| Page entries | [Pass/Fail] | [X entries found] |
| URL validity | [Pass/Fail] | [X broken URLs] |
| Entry descriptions | [Pass/Fail] | [X missing descriptions] |
| Key Facts | [Pass/Fail] | [Notes] |
| Contact section | [Pass/Fail] | [Notes] |

---

## Missing Pages

These important pages were found on the site but not in llms.txt:

1. [Page Title](URL) -- [Why it should be included]
2. [Page Title](URL) -- [Why it should be included]

## Improvement Recommendations

1. [Specific recommendation]
2. [Specific recommendation]
3. [Specific recommendation]

## Suggested Updated llms.txt

[Complete rewritten llms.txt file if significant improvements are needed]
For Generation Mode

Output the complete llms.txt file content, ready to be saved to the site's root directory. Also output a brief GEO-LLMSTXT-GENERATION.md report explaining:

  • How many pages were discovered and how many were selected
  • The prioritization rationale
  • Any pages that were borderline (might add later)
  • Recommended update frequency (e.g., monthly for active blogs, quarterly for stable sites)

Best Practices Reference

  1. Update regularly. If your site publishes weekly blog posts, update llms.txt monthly. If your product changes quarterly, update after each release.
  2. Lead with your strongest content. The first entries in each section should be your most authoritative, comprehensive pages.
  3. Be specific in descriptions. "Comprehensive 3,000-word guide to React Server Components with code examples" is far more useful than "React guide."
  4. Include your differentiators. If your site has unique data, original research, or exclusive features, highlight these in descriptions and Key Facts.
  5. Keep it concise. The llms.txt should be scannable in under 60 seconds. Save detail for llms-full.txt.
  6. Use absolute URLs. Always include the full https:// URL, never relative paths.
  7. Test after deployment. After uploading, verify the file is accessible at https://yourdomain.com/llms.txt with no redirects.
  8. Coordinate with robots.txt. Ensure pages listed in llms.txt are not blocked in robots.txt for AI crawlers.
  9. Mirror your site structure. Section names in llms.txt should roughly correspond to your main navigation categories.
  10. Avoid sensitive pages. Do not include internal tools, admin panels, or pages with sensitive information.

© zubair-trabzada, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in skills/geo-llmstxt of zubair-trabzada/geo-seo-claude.

Open the folder on GitHubat commit 989cae0

Used in 2 other repositories

We found 6 copies of this SKILL.md (exact, near-identical or edited) in other folders, from 2 other GitHub owners. This page covers the copy in zubair-trabzada/geo-seo-claude, which our catalogue first saw on October 7, 2026.

Compare with similar skills

llms.txt Analyzer and Generator next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

llms.txt Analyzer and Generator compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
llms.txt Analyzer and Generator this skillzubair-trabzada/geo-seo-claude11k2 repos~3.9kAutomated safety check: NotesMIT
SEO and GEO Auditdageno-agents/seo-geo-audit176—~2kAutomated safety check: PassMIT
Universal SEO AnalysisAgriciDaniel/claude-seo19k—~4.9kAutomated safety check: PassMIT
SEO AuditAgriciDaniel/codex-seo7992 repos~1.9kAutomated safety check: PassMIT
Full Website SEO AuditAgriciDaniel/claude-seo19k—~2.6kAutomated safety check: PassMIT
Site Launch Checklistsamber/cc-skills227—~13kAutomated safety check: NotesMIT

Similar skills

  • SEO and GEO Audit

    dageno-agents/seo-geo-audit

    Runs one prioritized audit that combines technical SEO, content quality, trust signals, entity clarity and AI search readiness for a page, site or domain.

    176 GitHub stars~2k tokensUpdated 1 mo ago
    Marketing & SEOAuto-check passed
  • Universal SEO Analysis

    AgriciDaniel/claude-seo

    Hub for site-wide SEO work: audits, technical checks, schema, content quality, local, hreflang and AI-search readiness, run through slash commands.

    19k GitHub stars~4.9k tokensUpdated 6 days ago
    Marketing & SEOAuto-check passed
  • SEO Audit

    AgriciDaniel/codex-seo

    Full website SEO audit with parallel subagent delegation. An agent skill from AgriciDaniel/codex-seo.

    799 GitHub starsUsed in 2 repos~1.9k tokens
    Marketing & SEOAuto-check passed
  • Full Website SEO Audit

    AgriciDaniel/claude-seo

    Runs a full-site SEO audit by crawling the site and delegating to specialist checks, then returns a scored, prioritized report. Meant for site-wide reviews only.

    19k GitHub stars~2.6k tokensUpdated 6 days ago
    Marketing & SEOAuto-check passed
  • Site Launch Checklist

    samber/cc-skills

    Pre-launch checklist for shipping a new website or web app. An agent skill from samber/cc-skills.

    227 GitHub stars~13k tokensUpdated 10 days ago
    Marketing & SEOAuto-check: notes
  • Generative Engine Optimization

    tech-leads-club/agent-skills

    Makes a page or site easier for AI answer engines to find, understand, trust and quote, using metadata, structured data, an llms.txt file and clear page structure.

    7k GitHub stars~2.5k tokensUpdated 2 days ago
    Marketing & SEOAuto-check passed

More from zubair-trabzada/geo-seo-claude

All 16 skills in this repo
  • GEO-First SEO Audit Tool

    zubair-trabzada/geo-seo-claude

    Audits a website for AI search visibility across ChatGPT, Claude, Perplexity and Google AI Overviews while checking traditional SEO, schema and E-E-A-T content quality.

    11k GitHub stars~2.8k tokensUpdated yesterday
    Auto-check: notes
  • GEO Monthly Delta Report

    zubair-trabzada/geo-seo-claude

    Compares a baseline and a current GEO audit for a client, calculates score changes and action item progress, and writes a monthly progress report.

    11k GitHub stars~2.4k tokensUpdated yesterday
    Auto-check: notes
  • AI Citability Scorer

    zubair-trabzada/geo-seo-claude

    Scores how likely AI assistants are to quote passages from a web page and suggests rewrites that make those passages easier to extract.

    11k GitHub starsUsed in 2 repos~3.7k tokens
    Auto-check: notes
  • GEO Service Proposal Generator

    zubair-trabzada/geo-seo-claude

    Builds a client-ready AI-search-optimization proposal from an existing GEO audit, with pricing tiers, an ROI estimate and a markdown document ready to send.

    11k GitHub stars~3k tokensUpdated yesterday
    Auto-check: notes
  • GEO Content E-E-A-T Scorer

    zubair-trabzada/geo-seo-claude

    Scores a page's content against Google's E-E-A-T framework and AI-citability structure, then writes a scored gap-analysis report.

    11k GitHub starsUsed in 2 repos~4k tokens
    Auto-check: notes
  • GEO Prospect Tracker

    zubair-trabzada/geo-seo-claude

    Tracks GEO agency leads and clients through a sales pipeline in a local JSON file, with notes, audit scores, deal values and a pipeline summary.

    11k GitHub stars~1.7k tokensUpdated yesterday
    Auto-check: notes

Categories

Questions about llms.txt Analyzer and Generator

What does llms.txt Analyzer and Generator do?

Validates an existing llms.txt file or crawls a site to generate a new one, following the format rules for a root-level Markdown file aimed at AI systems. txt is a proposed convention, introduced by Jeremy Howard in September 2024, in which a site publishes a Markdown summary of its purpose and key pages for AI systems.txt but describes what is most useful instead of what to avoid.

When should I use llms.txt Analyzer and Generator?

llms.txt Analyzer and Generator fits situations like: checking whether a site's llms.txt follows the format rules; generating an llms.txt for a site that has none; preparing a site's key pages so AI systems can find them quickly.

How do I install llms.txt Analyzer and Generator in Claude Code?

Run `npx skills add zubair-trabzada/geo-seo-claude --skill geo-llmstxt -a claude-code`. Or copy the skill folder (skills/geo-llmstxt in zubair-trabzada/geo-seo-claude) into .claude/skills/geo-llmstxt in your project. Claude Code loads it when a task matches its description.

How do I install llms.txt Analyzer and Generator in Codex?

Run `npx skills add zubair-trabzada/geo-seo-claude --skill geo-llmstxt -a codex`. Or copy the skill folder (skills/geo-llmstxt in zubair-trabzada/geo-seo-claude) into .agents/skills/geo-llmstxt in your project. Codex loads it when a task matches its description.

Can I use llms.txt Analyzer and Generator in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add zubair-trabzada/geo-seo-claude --skill geo-llmstxt -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/geo-llmstxt, .gemini/skills/geo-llmstxt, .github/skills/geo-llmstxt and .opencode/skills/geo-llmstxt in your project.

What does llms.txt Analyzer and Generator need to run?

SKILL.md names no scripts, command-line tools or credentials: llms.txt Analyzer and Generator is instructions for the agent only. Our summary lists: Network access to fetch and crawl the target website. Its frontmatter pre-approves these tools: Read, Grep, Glob, Bash, WebFetch, Write.

Does llms.txt Analyzer and Generator access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is llms.txt Analyzer and Generator safe to install?

Our automated static check of SKILL.md found notes only (pre-approves every shell command (allowed-tools: bash)), nothing it rates as a warning. It is not a guarantee. Review the folder before installing.

What licence does llms.txt Analyzer and Generator use?

llms.txt Analyzer and Generator is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does llms.txt Analyzer and Generator use?

About 3.9k tokens (SKILL.md is roughly 16k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to llms.txt Analyzer and Generator?

Skills that share tags, products or a category with llms.txt Analyzer and Generator: SEO and GEO Audit (dageno-agents/seo-geo-audit, 176 stars), Universal SEO Analysis (AgriciDaniel/claude-seo, 19k stars), SEO Audit (AgriciDaniel/codex-seo, 799 stars) and Full Website SEO Audit (AgriciDaniel/claude-seo, 19k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains llms.txt Analyzer and Generator?

zubair-trabzada (a GitHub user) maintains it in zubair-trabzada/geo-seo-claude, which has 10,982 GitHub stars. The repository holds 16 skills in this directory. The repository was last updated on October 10, 2026.

Source: zubair-trabzada/geo-seo-claude on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.