generating-llm-indexes

Generate llms.txt and llms-full.txt documentation indexes for AI assistants and RAG ingestion.

Updated Mar 6, 2026
One-click install
npx skills add https://github.com/musher-dev/bundles --skill generating-llm-indexes
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: generating-llm-indexes
Source: https://github.com/musher-dev/bundles/tree/main/developer-docs-authoring/skills/generating-llm-indexes
Command: npx skills add https://github.com/musher-dev/bundles --skill generating-llm-indexes

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill automates the creation of machine-readable documentation indexes, making it easier for AI coding assistants and RAG pipelines to understand and utilize your documentation.

Core Features & Use Cases

  • Generate llms.txt: Creates a curated sitemap for AI assistants, detailing documentation structure and content.
  • Generate llms-full.txt: Produces a comprehensive content dump for deep RAG ingestion.
  • Use Case: Ensure your AI coding assistant can quickly find and reference relevant API documentation by generating an optimized llms.txt file.

Quick Start

Generate machine-readable documentation indexes for AI assistant consumption.

Frequently Asked Questions about generating-llm-indexes

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I generate llms.txt files for my developer documentation?

Generating llms.txt files for developer documentation is automated by this Skill, which reads existing docs and writes structured indexes designed specifically for AI assistant consumption and RAG ingestion.

What is the difference between llms.txt and llms-full.txt for RAG ingestion?

For RAG ingestion, llms.txt provides a curated sitemap for quick AI assistant reference, while llms-full.txt outputs a comprehensive content dump designed for deep full-text retrieval and larger context windows.

How do I make my API documentation readable for AI coding assistants?

Making API documentation readable for AI coding assistants involves generating a structured llms.txt index that organizes content into a machine-readable format fitting directly into LLM context windows.

Do I need specific file manipulation tools to create LLM indexes?

Creating LLM indexes requires Read, Glob, Grep, Write, and Edit tools to perform the necessary file manipulation and content processing to output the final machine-readable documentation.

When should I use a full documentation dump instead of a curated index for AI?

Use a full documentation dump like llms-full.txt when your pipeline requires deep RAG ingestion and comprehensive content retrieval, instead of a structural sitemap meant for quick AI navigation.