Agent skill · Documentation

llms-txt-support

Detect and use llms.txt files for LLM-optimized documentation. Use when checking if a site has LLM-ready docs before scraping.

majiayu000github.com/majiayu000GitHub ↗
claude-codeMIT
Install
npx skills add majiayu000/claude-skill-registry --skill llms-txt-support --agent claude-code

Same command for any agent — swap --agent for codex, cursor, copilot.

Facts
Files in the skill folder: 2
SKILL.md size: 6 KB
Bundled scripts: none
Path: skills/ai-llm/llms-txt-support/SKILL.md
Open the folder on GitHub →
Where it comes from
Stars: 534
Language: HTML

Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.

From the SKILL.md

# llms.txt Support Skill ## Purpose Single responsibility: Detect, fetch, and utilize llms.txt files that provide LLM-optimized documentation, enabling 10x faster documentation ingestion. (BP-4) ## Background The llms.txt standard (https://llmstxt.org/) provides a convention for websites to expose LLM-friendly documentation. Instead of scraping entire sites, check for llms.txt first. **File hierarchy (check in order):** 1. `llms-full.txt` - Complete documentation (largest) 2. `llms.txt` - Standard documentation 3. `llms-small.txt` - Condensed documentation (smallest) ## Grounding Checkpoint (Archetype 1 Mitigation) Before executing, VERIFY: - [ ] Base URL is accessible - [ ] Check all three llms.txt variants in order - [ ] Validate file content is actual documentation (not error page) - [ ] Confirm file size is reasonable for the documentation scope **DO NOT assume llms.txt exists. Always probe first.** ## Uncertainty Escalation (Archetype 2 Mitigation) ASK USER instead of guessing when: - Multiple llms.txt variants found - which size to use? - llms.txt content appears partial or outdated - File returns but content seems like error page - Site has llms.txt but content doesn't match

What's inside
Steps it walks through
  1. Purpose
  2. Background
  3. Grounding Checkpoint (Archetype 1 Mitigation)
  4. Uncertainty Escalation (Archetype 2 Mitigation)
  5. Context Scope (Archetype 3 Mitigation)
  6. Workflow Steps
  7. Step 1: Detect llms.txt (Grounding)
  8. Step 2: Validate Content
  9. Step 3: Choose Variant
  10. Step 4: Fetch and Process
  11. Step 5: Validate Output
  12. Overview
  13. Installation
  14. Quick Start
Ships with 1 file
  • metadata.json
Commands it runs
Check for llms.txt variants (in order of preference)
curl -I https://example.com/llms-full.txt
curl -I https://example.com/llms.txt
curl -I https://example.com/llms-small.txt
Check common alternate locations
curl -I https://example.com/.well-known/llms.txt
curl -I https://docs.example.com/llms.txt
Fetch and inspect first 100 lines
curl -s https://example.com/llms.txt | head -100
Check file size
More from claude-skill-registry
All skills →
About this skill
What does the llms-txt-support skill do?

Detect and use llms.txt files for LLM-optimized documentation. Use when checking if a site has LLM-ready docs before scraping.

How do I install it?

Run `npx skills add majiayu000/claude-skill-registry --skill llms-txt-support --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 majiayu000/claude-skill-registry, a repository with 534 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.

Keep going