generate-llms-txt

Generate or update website-facing llms.txt files following the llmstxt.org proposal.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/nclandrei/dotfiles --skill generate-llms-txt
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: generate-llms-txt
Source: https://github.com/nclandrei/dotfiles/tree/main/config/skills/generate-llms-txt
Command: npx skills add https://github.com/nclandrei/dotfiles --skill generate-llms-txt

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

llms.txt is a lightweight index of site-wide links and short descriptions that must be kept in sync with the deployed site. This skill automates generating or updating that file to reflect canonical URLs and commands.

Core Features & Use Cases

  • Generate or update website-facing llms.txt following the llmstxt.org proposal.
  • Discover canonical sources in the repository and map them to accessible links or commands.
  • Support multiple deployment contexts via profiles: website, repo-context, and cli.

Quick Start

Generate or update the site-wide llms.txt using the website profile.

Frequently Asked Questions about generate-llms-txt

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

FAQPage Schema
What is an llms.txt file and when do I need it for my static site?

An llms.txt file is a lightweight index of site-wide links and descriptions kept in sync with deployed content. You need it for static-site deployments to provide accessible, canonical URLs and commands for automated context retrieval.

How do I generate an llms.txt file for my website?

Generate an llms.txt file by discovering canonical sources in your repository and mapping them to accessible links. Apply the website profile during static-site deployment to automatically build or update the file following the llmstxt.org proposal.

Does the llms.txt generator work with repository context and CLI profiles?

The llms.txt generator supports multiple deployment contexts via profiles: website, repo-context, and cli. It requires repository-accessible source content with canonical links and deployment path clarity to map validated references correctly.

Why does my llms.txt file need canonical links and validated references?

Your llms.txt file needs canonical links and validated references to ensure the index accurately reflects the deployed site. The generator discovers repository source content and maps it to accessible links or commands based on clear deployment paths.

What's the best way to keep my llms.txt file in sync with my deployed website?

The best way to keep your llms.txt file in sync is to automate generation or updates during static-site deployments. This ensures the file consistently reflects canonical URLs and commands without manual maintenance.