agentleFS
agentconfigagentconfig/agentconfig.org/.github/skills/generate-llms/SKILL.md

generate-llms

Skill7 starsChanged 3 months agoISCView on GitHub

Generate llms.txt and llms-full.txt files for AI agent consumption following the llmstxt.org standard. Use when updating site content that should be reflected in the llms files, or when building/deploying the site.

The file

We split this skill into the rules it gives an agent

8 rules. About 0 are common, 7 are distinctive, and 1 is very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈7

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    When creating a new page, add an entry to the registry to include it in the llms files.

    line 35
  2. Distinctive:

    Use this skill when:

    line 39
  3. Distinctive:

    Before deploying or releasing a new version of the site

    line 42
  4. Distinctive:

    When an agent needs to understand what content should be in llms files

    line 43
  5. Distinctive:

    Run the generation script:

    line 111
  6. Distinctive:

    When to use it

    line 123
  7. Distinctive:

    If the script isn't available, generate manually by:

    line 146
  8. Very specific:

    Read each data file in site/src/data/

    line 148

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Generate LLMs Files

Generate /llms.txt and /llms-full.txt files that help AI agents understand and use the agentconfig.org site content.

Overview

This skill generates machine-readable documentation files following the llmstxt.org standard:

  • /llms.txt — A curated table of contents with links to detailed pages
  • /llms-full.txt — Comprehensive markdown containing all site content
  • /*.md — Page-specific markdown files (skills.md, agents.md, mcp.md, etc.)

Page Registry

Pages are automatically discovered from the page registry at site/src/data/pages.ts:

export const pages: readonly PageMeta[] = [
  {
    slug: 'skills',
    title: 'Skills Tutorial',
    description: 'How to create agent skills...',
    mdFile: 'skills.md',
    partNumber: 4,
  },
  // ... more pages
]

When creating a new page, add an entry to the registry to include it in the llms files.

When to Use

Use this skill when:

  • You've updated content in the data files (site/src/data/*.ts)
  • You've added a new page (remember to add it to the page registry!)
  • Before deploying or releasing a new version of the site
  • When an agent needs to understand what content should be in llms files

Data Sources

The llms files are generated from these TypeScript data files:

FileContent
site/src/data/pages.tsPage registry - lists all pages for llms generation
site/src/data/primitives.ts13 AI primitives with descriptions, use cases, and provider implementations
site/src/data/comparison.tsFour-provider comparison matrix derived from primitives.ts
site/src/data/providerProfiles.tsPer-provider profiles derived from primitives.ts
site/src/data/skillsTutorial.tsSkills tutorial sections and concepts
site/src/data/skillExamples.ts5 example skills with full code
site/src/data/agentsTutorial.tsAgent instructions guide with code samples
site/src/data/hooksTutorial.tsHooks tutorial with provider tabs, lifecycle events, and reusable policy logic
site/src/data/mcpTutorial.tsMCP tutorial sections and code samples

File Structure

site/public/
├── llms.txt           # Table of contents (llmstxt.org format)
├── llms-full.txt      # Complete site content in one file
├── skills.md          # Skills page content (rich markdown)
├── agents.md          # Agents page content (rich markdown)
├── hooks.md           # Hooks page content (rich markdown)
├── mcp.md             # MCP page content (rich markdown)
└── profiles.md        # Provider profiles content (rich markdown)

Generation Process

Step 1: Generate /llms.txt (Table of Contents)

The homepage llms.txt follows the strict llmstxt.org format:

  • H1 with project name
  • Blockquote with summary
  • Optional paragraph (no headings)
  • H2 sections with link lists only
# agentconfig.org

> A reference site for configuring AI coding assistants. Covers 13 AI primitives,
> provider comparison across GitHub Copilot, Claude Code, Cursor, and OpenAI Codex,
> and progressive tutorials for skills, instructions, hooks, and MCP.

## Pages

- [Homepage](https://agentconfig.org/): AI primitives reference, file tree, provider comparison
- [Skills Tutorial](https://agentconfig.org/skills): How to create agent skills following agentskills.io
- [Agent Instructions](https://agentconfig.org/agents): Project instructions across GitHub Copilot, Claude Code, Cursor, and OpenAI Codex

## Docs

- [Full site content](/llms-full.txt): Complete content for deep context
- [Skills page content](/skills.md): Skills tutorial with 5 example skills
- [Agents page content](/agents.md): Agents tutorial with code samples

## Optional

- [agentskills.io specification](https://agentskills.io/specification): The skills format
- [AGENTS.md specification](https://agents.md): Open format for coding agents

Step 2: Generate /llms-full.txt (Complete Content)

Run the generation script:

bun .github/skills/generate-llms/scripts/generate-llms-full.ts

This reads all data files and generates comprehensive markdown including:

  1. Site overview with purpose and structure
  2. All 13 AI primitives with full details:
    • Description
    • What it is
    • When to use it
    • What it prevents
    • What to combine it with
    • Provider implementations (GitHub Copilot, Claude Code, Cursor, and OpenAI Codex)
  3. Provider comparison table showing support levels
  4. Config file locations for all four providers
  5. Skills tutorial with all concepts and 5 example skills
  6. Agents tutorial with all sections and code samples

Step 3: Generate Page-Specific .md Files

/skills.md:

  • Tutorial sections (Understanding the Spec, Progressive Disclosure, etc.)
  • 5 example skills with full SKILL.md content
  • Key takeaways for each example

/agents.md:

  • 9 tutorial sections from beginner to advanced
  • Code samples for AGENTS.md, CLAUDE.md, copilot-instructions.md
  • Path-scoped rules, agent personas, monorepo strategies

Manual Generation

If the script isn't available, generate manually by:

  1. Read each data file in site/src/data/
  2. Extract the exported arrays/objects
  3. Format as markdown following the templates below

Template: Primitive Entry

### {name}

{description}

**What it is:** {whatItIs}

**Use when:**
{useWhen as bullet list}

**Prevents:** {prevents}

**Combine with:** {combineWith as comma-separated list}

**Provider Implementations:**

| Provider | Implementation | Location | Support |
|----------|---------------|----------|---------|
| Copilot | {implementation} | {location} | {support} |
| Claude | {implementation} | {location} | {support} |

Template: Skill Example

### {displayName}

**Complexity:** {complexity}
**Demonstrates:** {demonstrates}

{description}

**Files:**

\`\`\`{language}
// {path}
{content}
\`\`\`

**Key Takeaways:**
{keyTakeaways as bullet list}

Validation

After generating, verify:

  1. Links work — All internal links resolve
  2. Content is current — Matches what's shown on the site
  3. Format is correct — Valid markdown, proper headings
  4. Size is reasonable — llms-full.txt should be comprehensive but not bloated

Example Prompts

Generate all llms files

Generate all the llms.txt files for agentconfig.org

Update after content change

I updated the primitives data, regenerate the llms files

Check what should be in llms-full.txt

What content should be included in llms-full.txt?

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.