update-llms

Update the repository's llms.txt file to match current documentation and structure.

Updated Mar 8, 2026
One-click install
npx skills add https://github.com/tamago0224/kuroshio-mta --skill update-llms-tamago0224
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: update-llms
Source: https://github.com/tamago0224/kuroshio-mta/tree/main/.agents/skills/update-llms
Command: npx skills add https://github.com/tamago0224/kuroshio-mta --skill update-llms-tamago0224

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The skill ensures that the llms.txt file at the repository root stays accurate and compliant with the llms.txt specification, reflecting any changes in documentation, file structure, or project specifications.

Core Features & Use Cases

  • Compliance Assurance: Validates and updates llms.txt to meet the official specification.
  • Documentation Alignment: Keeps high‑level guidance in sync with new or moved files, README updates, and configuration changes.
  • Repository Maintenance: Ideal for developers and maintainers when the project evolves, ensuring LLMs receive correct navigation information.

Quick Start

Request the skill to refresh the llms.txt file so it matches the latest repository layout and documentation.

Frequently Asked Questions about update-llms

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

FAQPage Schema
How do I update llms.txt to match my repository's current documentation?

To update llms.txt, the skill scans your repository's layout and documentation changes, refreshing the file to align with the latest structure and providing valid relative links to key project files.

What is the llms.txt specification used for in a repository?

The llms.txt specification provides high-level navigation information for LLMs. Keeping the file compliant ensures LLMs receive accurate guidance about your project's documentation and file structure.

When do I need to regenerate the llms.txt file for my project?

You should regenerate the llms.txt file when documentation is updated, files are moved, or project specifications change, ensuring the content accurately reflects the current repository state.

Does updating llms.txt require a specific repository structure or configuration?

Updating llms.txt targets repositories with an existing root file. It validates compliance against the official specification and uses relative links, requiring no external dependencies or specific configurations.

What is the best way to keep llms.txt compliant with the specification after moving files?

The best way to keep llms.txt compliant is to run an synchronization process that automatically maps moved files and updates the relative links, maintaining accurate navigation for LLMs.