llms-txt-generator
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
npx skills add Varnan-Tech/opendirectory --skill llms-txt-generator --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# 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 it
- Workflow
- Step 1: Detect Source — Codebase or Live Site?
- Step 2A: Codebase Mode — Read the Repo Directly
- Step 2B: Live Site Mode — Get Target URL
- Step 3: Check for Existing llms.txt (Live Site Mode only)
- Step 3B: Connect to Browser and Crawl
- Step 4: Read the Spec and Template
- Step 5: Generate llms.txt
- Step 6: Check for llms-full.txt
- Step 7: Save and Output
- Step 8: Placement Instructions
- Output Quality Standards
What does the llms-txt-generator skill 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. 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
How do I install it?
Run `npx skills add Varnan-Tech/opendirectory --skill llms-txt-generator --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From Varnan-Tech/opendirectory, a repository with 571 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.