New: 98,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Agent skill

LLMs Txt Generator

by Varnan-Tech in Varnan-Tech/opendirectory

Generates and maintains a standards-compliant llms.txt file for any website — either by crawling the live site OR by reading the website's codebase directly.

MITAuto-check passedMarketing & SEO

Install LLMs Txt Generator

skills CLI
$ npx skills add Varnan-Tech/opendirectory --skill llms-txt-generator -a claude-code

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

GitHub CLI
$ gh skill install Varnan-Tech/opendirectory llms-txt-generator --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/Varnan-Tech/opendirectory.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/llms-txt-generator .claude/skills/llms-txt-generator && 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
llms-txt-generator
GitHub stars
674
Token cost
~2.4k tokens
SKILL.md length
1,219 words
Files
7 (incl. references)
Skills in repo
61
Repo updated
First seen
Licence
MIT

At a glance

Generates and maintains a standards-compliant llms.txt file for any website — either by crawling the live site OR by reading the website's codebase directly.

  • Works in 7 steps: Detect Source — Codebase or Live Site? → Check for Existing llms.txt (Live Site… → Read the Spec and Template → …
  • Asked to create an llms.txt
  • SKILL.md covers Workflow and Output Quality Standards
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

LLMs Txt Generator is an agent skill from Varnan-Tech/opendirectory. Generates and maintains a standards-compliant llms.txt file for any website — either by crawling the live site OR by reading the website's codebase directly. Use this skill when asked to create an llms.txt, add AI discoverability to a site, improve GEO (Generative Engine Optimization), make a website readable by AI agents, generate an llms-full.txt, check if a site has llms.txt, or audit a site's AI readiness for generative search. Trigger this skill any time a user mentions llms.txt, AI discoverability, LLM site…

Its SKILL.md is about 2.4k tokens, which your agent loads only when the skill is triggered. The skill folder holds 10 other files, including reference files (for example `README.md`, `evals/evals.json` and `references/llms-txt-spec.md`). Compatibility notes: ["claude-code","gemini-cli","github-copilot"]

It sits in Marketing & SEO, covering AI search optimization. It works with Astro. The repository describes itself as: AI Agent Skills built for Founders who hate Marketing. The licence is MIT.

When your agent uses it

  • Asked to create an llms.txt
  • Add AI discoverability to a site
  • Improve GEO (Generative Engine Optimization)
  • Make a website readable by AI agents

Example prompts

  • “Use the llms-txt-generator skill to generate and maintains a standards-compliant llms.txt file for any website — either by crawling the live site OR…”
  • “/llms-txt-generator”

Requirements

  • Compatibility (from SKILL.md): ["claude-code","gemini-cli","github-copilot"]

Workflow steps

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

  1. Detect Source — Codebase or Live Site?
  2. Check for Existing llms.txt (Live Site Mode only)
  3. Read the Spec and Template
  4. Generate llms.txt
  5. Check for llms-full.txt
  6. Save and Output
  7. Placement Instructions

What it can do on your machine

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

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md.

    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.

  • Compatibility

    ["claude-code","gemini-cli","github-copilot"]

    From compatibility in the SKILL.md frontmatter.

Context cost

LLMs Txt Generator loads about 2.4k tokens when it runs, and up to ~4.1k if it reads all its reference files. Until then it costs about 179 tokens; SKILL.md has 1,219 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~179
When it runs · the whole SKILL.md, loaded when a task matches
~2.4k
With references · SKILL.md plus every file in references/, read only if the agent opens them
~4.1k

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 passed

The automated check found no risky patterns in SKILL.md.

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 Varnan-Tech/opendirectory at commit 62e437a, republished under its MIT licence (© Varnan-Tech). 1,219 words, ~2,409 tokens.

Download SKILL.mdSave it as .claude/skills/llms-txt-generator/SKILL.md (or your agent's skills folder). This skill also uses 6 other files; get the full folder from GitHub.
name
llms-txt-generator
description
Generates and maintains a standards-compliant llms.txt file for any website — either by crawling the live site OR by reading the website's codebase directly. Use this skill when asked to create an llms.txt, add AI discoverability to a site, improve GEO (Generative Engine Optimization), make a website readable by AI agents, generate an llms-full.txt, check if a site has llms.txt, or audit a site's AI readiness for generative search. Trigger this skill any time a user mentions llms.txt, AI discoverability, LLM site readability, or wants their site to appear in AI-generated answers. Also trigger when the user is inside a website codebase and asks about SEO, AI readiness, or content structure.
compatibility
["claude-code","gemini-cli","github-copilot"]
author
OpenDirectory
version
1.0.0

llms.txt Generator

You are an expert in Generative Engine Optimization (GEO) and the llms.txt standard. Your job is to crawl a website and produce a perfectly structured llms.txt file that makes the site fully readable and citable by AI agents.

CRITICAL RULE: DO NOT INVENT CONTENT. Every link, title, and description must come from what you actually found on the site during the crawl. Never fabricate URLs or describe content you did not visit.

MANDATORY SETUP CHECK: Before starting, confirm you have:

  • Chrome running with remote debugging enabled (chrome --remote-debugging-port=9222)
  • Chrome DevTools MCP server configured in your agent settings
  • Target website URL from the user

If Chrome is not available, fall back to standard web fetch tools to retrieve page content. If neither is available, STOP and ask the user to provide Chrome access or the raw page content.

Workflow

Step 1: Detect Source — Codebase or Live Site?

Before anything else, check whether you are inside a website codebase:

  1. Look for package.json, astro.config.*, next.config.*, nuxt.config.*, gatsby-config.*, vite.config.*, or _config.yml in the current working directory or its parent.
  2. If found → Codebase Mode (go to Step 2A).
  3. If not found → ask the user for the target URL and proceed to Step 2B.
Step 2A: Codebase Mode — Read the Repo Directly

You have access to the source. Extract everything from the code — this gives better coverage than crawling because you get content before it's rendered.

2A-1. Detect the framework and site config:

  • Read package.json → identify framework (next, astro, nuxt, gatsby, @sveltejs/kit, etc.) and the name/description fields
  • Read framework config file (next.config.*, astro.config.*, etc.) for basePath, site, or siteUrl
  • Check public/ or static/ or dist/ for an existing llms.txt — if found, read it
  • QA: What framework is this? What is the base URL? Does llms.txt already exist?

2A-2. Discover all pages/routes:

FrameworkWhere to look
Next.js (pages router)pages/**/*.tsx, pages/**/*.jsx — skip _app, _document, api/
Next.js (app router)app/**/page.tsx, app/**/page.jsx — directory name = route
Astrosrc/pages/**/*.astro, src/pages/**/*.md
Nuxtpages/**/*.vue
Gatsbysrc/pages/**/*.tsx, src/pages/**/*.jsx
SvelteKitsrc/routes/**/+page.svelte
Hugo / Jekyllcontent/**/*.md, _posts/**/*.md

Read each page file and extract: page title (<title>, export const metadata, frontmatter title:), meta description, and main headings (H1, H2).

2A-3. Find blog/content posts:

  • Check content/, posts/, src/content/, _posts/, blog/ for markdown/MDX files
  • Read frontmatter (title, description, date, slug) from each file
  • List the 5–10 most recent or most important posts

2A-4. Read the site's existing SEO/meta config:

  • src/config.ts, src/site.config.ts, seo.config.*, or any file exporting siteTitle, siteDescription, siteUrl
  • constants.ts, config/index.ts — look for site-level metadata

2A-5. Construct the base URL:

  • Prefer siteUrl or site from config files
  • Fall back to asking the user: "What is your production URL? (e.g. https://yoursite.com)"
  • QA: Is the base URL confirmed? All links in llms.txt must use the full absolute URL.

Then skip to Step 4 to generate the file using codebase data.

Step 2B: Live Site Mode — Get Target URL

If the user hasn't provided a URL, ask: "What website should I generate llms.txt for?"

Step 3: Check for Existing llms.txt (Live Site Mode only)

Before crawling, check if the site already has one:

  1. Navigate to [URL]/llms.txt
  2. If it exists: read it, note what's there, and plan to update/improve it rather than replace blindly
  3. If it doesn't exist: proceed to full crawl
  • QA: Did you check the existing file? Note its status (missing / outdated / present and good).
Step 3B: Connect to Browser and Crawl

Use the Chrome DevTools MCP server to connect to the live browser. Follow the same connection pattern as the chrome-cdp-skill:

  1. Connect to http://localhost:9222 via Chrome DevTools MCP
  2. Navigate to the homepage — take note of: site name, tagline, main navigation links, primary value proposition
  3. Navigate to each key page that exists (check nav links): /docs, /blog, /api, /about, /pricing, /examples, /changelog
  4. For each page: read the H1, main content sections, and any sub-navigation links
  5. For the blog: read titles and descriptions of the 5-10 most relevant/recent posts

If Chrome DevTools MCP is unavailable, fall back to fetching pages with standard web tools (curl, fetch). If the site returns 403, try adding a browser User-Agent header.

  • QA: Did you successfully load and read each page? List which pages you visited and which returned 404. Do not include 404 pages.
Step 4: Read the Spec and Template

Before writing output, read both reference files:

  • references/llms-txt-spec.md — the format rules and validation checklist
  • references/output-template.md — the exact template to follow

Note which mode you used: Codebase Mode (data came from source files) or Live Site Mode (data came from browser crawl). Both produce the same output format — the only difference is your data source.

Show full SKILL.md (458 more words)Show less
Step 5: Generate llms.txt

Using only content from your crawl, produce the llms.txt file:

  1. Write the H1 header (product/site name — factual, not tagline)
  2. Write the summary blockquote (1-3 sentences, factual, LLM-friendly — no marketing fluff)
  3. Add only the H2 sections that have real content on the site
  4. For each link: write a factual, content-dense description of what an LLM will find at that URL
  5. Apply the validation checklist from references/llms-txt-spec.md before finalizing
  • QA: Is every URL real and verified from the crawl? Is every description factual, not marketing copy? Is the file under 5,000 words? Fix any issues before proceeding.
Step 6: Check for llms-full.txt

Ask the user: "Do you also want me to generate llms-full.txt with the full prose content of key pages included? This is larger but gives AI agents everything in one file."

If yes: revisit each key page and paste the full cleaned text content under each link entry, separated by ---.

Step 7: Save and Output
  1. Save llms.txt to the current working directory (or the user's project root if known)
  2. If llms-full.txt was requested, save that too
  3. Print the full contents of llms.txt in the conversation so the user can review it
  4. If the user's site is on GitHub, offer to open a PR to add the file to the repo root
  • QA: Is the file saved? Did you confirm the save path with the user?
Step 8: Placement Instructions

If Codebase Mode: You know the framework — place the file immediately:

FrameworkAction
Next.js / VercelWrite directly to public/llms.txt in the repo
AstroWrite directly to public/llms.txt
NuxtWrite directly to public/llms.txt
GatsbyWrite directly to static/llms.txt
SvelteKitWrite directly to static/llms.txt
HugoWrite directly to static/llms.txt
JekyllWrite directly to root of repo as llms.txt

Ask the user: "I can write llms.txt directly to public/llms.txt in your repo. Should I do that now, or do you want to review it first?"

If approved, write the file. Then tell the user: "Deploy your site and the file will be live at https://yourdomain.com/llms.txt."

If Live Site Mode: Tell the user where to add it:

Place llms.txt at your web root so it's accessible at: https://yourdomain.com/llms.txt

- Next.js / Vercel: put in /public/llms.txt
- Astro / Nuxt / Gatsby / SvelteKit: put in /public/llms.txt
- GitHub Pages: put in root of repo
- Hugo / Jekyll: put in /static/llms.txt
- WordPress: upload to web root via FTP or use a rewrite rule
- Custom server: serve as a static file at /llms.txt

Output Quality Standards

A great llms.txt file:

  • Has a factual H1 and a clear 2-3 sentence summary that an LLM could quote directly
  • Covers all major content areas the site actually has
  • Uses link descriptions that explain WHAT IS THERE, not what the company wants you to think
  • Is scannable in under 30 seconds
  • Contains no broken links, no redirect chains, no CDN asset URLs
  • Passes all checks in references/llms-txt-spec.md

A bad llms.txt file:

  • Has marketing language ("our amazing API", "best-in-class docs")
  • Contains invented or guessed URLs
  • Is missing major sections of the site
  • Has empty or vague descriptions ("info about our product")

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

Files

SKILL.md and 6 other files (references) in skills/llms-txt-generator of Varnan-Tech/opendirectory.

  • SKILL.md
  • .env.example
  • README.md
  • evals/evals.json
  • references/llms-txt-spec.md
  • references/output-template.md
  • test-output/genzcareer.in/llms.txt

Open the folder on GitHubat commit 62e437a

Compare with similar skills

LLMs Txt 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 Generator compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
LLMs Txt Generator this skillVarnan-Tech/opendirectory674—~2.4kAutomated safety check: PassMIT
Geo Fundamentalswasp-lang/wasp19k9 repos~861Automated safety check: PassMIT
SEO GeoReScienceLab/opc-skills1.8k4 repos~2.1kAutomated safety check: PassApache-2.0
GEO-First SEO Audit Toolzubair-trabzada/geo-seo-claude11k—~2.8kAutomated safety check: NotesMIT
GEO Monthly Delta Reportzubair-trabzada/geo-seo-claude11k—~2.4kAutomated safety check: NotesMIT
SEO DataforseoAgriciDaniel/codex-seo7992 repos~4.6kAutomated safety check: PassMIT

Similar skills

  • Geo Fundamentals

    wasp-lang/wasp

    Generative Engine Optimization for AI search engines (ChatGPT, Claude, Perplexity).

    19k GitHub starsUsed in 9 repos~861 tokens
    Marketing & SEOAuto-check passed

  • SEO Geo

    ReScienceLab/opc-skills

    SEO & GEO (Generative Engine Optimization) for websites. An agent skill from ReScienceLab/opc-skills.

    1.8k GitHub starsUsed in 4 repos~2.1k tokens
    Marketing & SEOAuto-check passed

  • 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 today
    Marketing & SEOAuto-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 today
    Marketing & SEOAuto-check: notes

  • SEO Dataforseo

    AgriciDaniel/codex-seo

    Live SEO data via DataForSEO MCP server. An agent skill from AgriciDaniel/codex-seo.

    799 GitHub starsUsed in 2 repos~4.6k tokens
    Marketing & SEOAuto-check passed

  • Fire Your SEO Agency

    leopard627/fire-your-seo-agency

    SEO·AEO·GEO·LLMO·NEO(네이버) 다섯 레인을 진단하고 직접 구현하며, 인용되는 콘텐츠를 계속 생산하는 서브 블로그·콘텐츠 운영 파이프라인까지 세팅하는 스킬.

    711 GitHub stars~1.1k tokensUpdated 14 days ago
    Marketing & SEOAuto-check passed

More from Varnan-Tech/opendirectory

All 61 skills in this repo

  • Graphic Ebook

    Varnan-Tech/opendirectory

    Creates professionally designed B2B SaaS e-books in HTML + CSS, exported as print-ready PDF.

    674 GitHub stars~5k tokensUpdated 1 mo ago
    Auto-check passed

  • Docs From Code

    Varnan-Tech/opendirectory

    Generates and updates README.md and API reference docs by reading your codebase's functions, routes, types, schemas, and architecture.

    674 GitHub stars~1.8k tokensUpdated 1 mo ago
    Auto-check passed

  • Graphic Chart

    Varnan-Tech/opendirectory

    Generates data visualization charts (bar, line, area, pie, doughnut, scatter, radar, treemap) as PNG using Apache ECharts v6.

    674 GitHub stars~2.9k tokensUpdated 1 mo ago
    Auto-check passed

  • Graphic Gif

    Varnan-Tech/opendirectory

    Creates animated looping GIFs from CSS animations (default) or AI image-to-video.

    674 GitHub stars~3k tokensUpdated 1 mo ago
    Auto-check passed

  • Map Your Market

    Varnan-Tech/opendirectory

    Given a product description, category keywords, or competitor names (any combination), searches Reddit, Hacker News, GitHub Issues, G2, and Google Trends for the real pains your market experiences…

    674 GitHub stars~4.3k tokensUpdated 1 mo ago
    Auto-check passed

  • Newsletter Digest

    Varnan-Tech/opendirectory

    Aggregates RSS feeds from the past week, synthesizes the top stories using Gemini, and publishes a newsletter digest to Ghost CMS.

    674 GitHub stars~1.9k tokensUpdated 1 mo ago
    Auto-check passed

Works with

Categories

Questions about LLMs Txt Generator

What does LLMs Txt Generator do?

Generates and maintains a standards-compliant llms.txt file for any website — either by crawling the live site OR by reading the website's codebase directly. LLMs Txt Generator is an agent skill from Varnan-Tech/opendirectory.txt file for any website — either by crawling the live site OR by reading the website's codebase directly.

When should I use LLMs Txt Generator?

LLMs Txt Generator fits situations like: asked to create an llms.txt; add AI discoverability to a site; improve GEO (Generative Engine Optimization); make a website readable by AI agents.

How do I install LLMs Txt Generator in Claude Code?

Run `npx skills add Varnan-Tech/opendirectory --skill llms-txt-generator -a claude-code`. Or copy the skill folder (skills/llms-txt-generator in Varnan-Tech/opendirectory) into .claude/skills/llms-txt-generator in your project. Claude Code loads it when a task matches its description.

How do I install LLMs Txt Generator in Codex?

Run `npx skills add Varnan-Tech/opendirectory --skill llms-txt-generator -a codex`. Or copy the skill folder (skills/llms-txt-generator in Varnan-Tech/opendirectory) into .agents/skills/llms-txt-generator in your project. Codex loads it when a task matches its description.

Can I use LLMs Txt 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 Varnan-Tech/opendirectory --skill llms-txt-generator -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/llms-txt-generator, .gemini/skills/llms-txt-generator, .github/skills/llms-txt-generator and .opencode/skills/llms-txt-generator in your project.

What does LLMs Txt Generator need to run?

SKILL.md names no scripts, command-line tools or credentials: LLMs Txt Generator is instructions for the agent only. Compatibility (from SKILL.md): ["claude-code","gemini-cli","github-copilot"].

Does LLMs Txt 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 Generator safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does LLMs Txt Generator use?

LLMs Txt 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 Generator use?

About 2.4k tokens (SKILL.md is roughly 9.6k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 1.7k tokens, read only when the agent opens those files.

What are the alternatives to LLMs Txt Generator?

Skills that share tags, products or a category with LLMs Txt Generator: Geo Fundamentals (wasp-lang/wasp, 19k stars), SEO Geo (ReScienceLab/opc-skills, 1.8k stars), GEO-First SEO Audit Tool (zubair-trabzada/geo-seo-claude, 11k stars) and GEO Monthly Delta Report (zubair-trabzada/geo-seo-claude, 11k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains LLMs Txt Generator?

Varnan-Tech (a GitHub organization) maintains it in Varnan-Tech/opendirectory, which has 674 GitHub stars. The repository holds 61 skills in this directory. The repository was last updated on August 16, 2026.

Source: Varnan-Tech/opendirectory on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.