llms-txt-extraction-guide

Extract llms.txt and install.md documentation into JSON, markdown, or plain text.

5|Updated May 2, 2026
One-click install
npx skills add https://github.com/nirholas/three-ui --skill llms-txt-extraction-guide
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: llms-txt-extraction-guide
Source: https://github.com/nirholas/three-ui/tree/main/data/skills/development/llms-txt-extraction-guide
Command: npx skills add https://github.com/nirholas/three-ui --skill llms-txt-extraction-guide

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps you quickly extract and normalize AI documentation from any website that publishes llms.txt and install.md, so LLM agents can reliably discover and use tools and setup instructions without manual copying.

Core Features & Use Cases

  • Standards-based extraction: Detects and extracts llms.txt, llms-full.txt, and install.md into structured outputs.
  • Agent-optimized formats: Produces multiple export formats including markdown, JSON, plain text, and split section files suitable for RAG and tool context.
  • Scalable access paths: Uses a Web interface, a CLI, a REST API, and an MCP server for both interactive and automated pipelines.
  • Common use case: Ingest DeFi or SaaS documentation from many protocols to build an up-to-date knowledge base that an agent can query during tool execution.

Quick Start

Paste the target documentation URL into llm.energy and extract the website’s llms.txt, llms-full.txt, and install.md into AI-ready documents.

Frequently Asked Questions about llms-txt-extraction-guide

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

FAQPage Schema
How do I extract llms.txt and install.md for building an LLM agent knowledge base?

This Skill detects and extracts llms.txt, llms-full.txt, and install.md from target URLs, normalizing website documentation into structured outputs like markdown and JSON for RAG context and agent knowledge bases.

Can I ingest SaaS documentation into RAG context using an MCP server?

Yes, you can use the MCP server, REST API, CLI, or Web interface to automate setup instruction ingestion and build queryable RAG context from SaaS documentation across many domains.

What output formats are supported when extracting llms.txt files?

The extraction supports multiple agent-optimized formats including markdown, JSON, plain text, and split section files, making the output suitable for RAG and tool execution contexts.

Does this extraction tool work with DeFi protocol documentation?

Yes, the tool applies to ingesting DeFi documentation from many protocols, allowing you to extract summaries, full documentation, and install instructions to maintain an up-to-date knowledge base.

What is the best way to automate website documentation ingestion for LLM agents?

Automating documentation ingestion is best handled via the CLI or REST API, which extract standards-based llms.txt and install.md files to reliably provide tool context without manual copying.