Geo Fundamentals
wasp-lang/wasp
Generative Engine Optimization for AI search engines (ChatGPT, Claude, Perplexity).
Update the llms.txt file in the root folder to reflect changes in documentation or specifications following the llms.txt specification at https://llmstxt.org/
Install Update LLMs
$ npx skills add github/awesome-copilot --skill update-llms -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install github/awesome-copilot update-llms --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/github/awesome-copilot.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/update-llms .claude/skills/update-llms && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "update-llms" agent skill from https://github.com/github/awesome-copilot/tree/main/skills/update-llms into .claude/skills/update-llms/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "update-llms", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/github/awesome-copilot/tree/main/skills/update-llmsType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add github/awesome-copilot --skill update-llms -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install github/awesome-copilot update-llms --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/github/awesome-copilot.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/update-llms .agents/skills/update-llms && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "update-llms" agent skill from https://github.com/github/awesome-copilot/tree/main/skills/update-llms into .agents/skills/update-llms/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "update-llms", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add github/awesome-copilot --skill update-llms -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install github/awesome-copilot update-llms --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/github/awesome-copilot.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/update-llms .cursor/skills/update-llms && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "update-llms" agent skill from https://github.com/github/awesome-copilot/tree/main/skills/update-llms into .cursor/skills/update-llms/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "update-llms", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/github/awesome-copilot.git --path skills/update-llms--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add github/awesome-copilot --skill update-llms -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install github/awesome-copilot update-llms --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/github/awesome-copilot.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/update-llms .gemini/skills/update-llms && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "update-llms" agent skill from https://github.com/github/awesome-copilot/tree/main/skills/update-llms into .gemini/skills/update-llms/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "update-llms", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install github/awesome-copilot update-llmsInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add github/awesome-copilot --skill update-llms -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/github/awesome-copilot.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/update-llms .github/skills/update-llms && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "update-llms" agent skill from https://github.com/github/awesome-copilot/tree/main/skills/update-llms into .github/skills/update-llms/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "update-llms", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add github/awesome-copilot --skill update-llms -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install github/awesome-copilot update-llms --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/github/awesome-copilot.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/update-llms .opencode/skills/update-llms && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "update-llms" agent skill from https://github.com/github/awesome-copilot/tree/main/skills/update-llms into .opencode/skills/update-llms/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "update-llms", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
update-llms- GitHub stars
- 40k
- Used in
- 2 other repos
- Token cost
- ~2.1k tokens
- SKILL.md length
- 930 words
- Files
- 1
- Skills in repo
- 417
- Repo updated
- First seen
- Licence
- MIT
At a glance
Update the llms.txt file in the root folder to reflect changes in documentation or specifications following the llms.txt specification at https://llmstxt.org/
- Works in 8 steps: Review Current File and Specification → Repository Structure Analysis → Content Discovery and Change Detection → …
- Tasks that involve AI search optimization
- SKILL.md covers Primary Directive, Analysis and Planning Phase, Implementation Requirements and Execution Steps, plus 3 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Update LLMs is an agent skill from github/awesome-copilot, published by the product's own GitHub organization. Update the llms.txt file in the root folder to reflect changes in documentation or specifications following the llms.txt specification at https://llmstxt.org/
Its SKILL.md is about 2.1k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in Marketing & SEO, covering AI search optimization. The repository describes itself as: Community-contributed instructions, agents, skills, and configurations to help you make the most of GitHub Copilot. The licence is MIT.
When your agent uses it
- Tasks that involve AI search optimization
Example prompts
- “/update-llms”
Workflow steps
8 steps, taken from the step headings in SKILL.md.
What it can do on your machine
Read from SKILL.md and the folder at commit 727ff2e. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md.
From the folder's file list and the shell code blocks in SKILL.md.
Network
Links to these hosts (documentation or services it may open):
llmstxt.org
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Update LLMs loads about 2.1k tokens when it runs. Until then it costs about 43 tokens; SKILL.md has 930 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from github/awesome-copilot at commit 727ff2e, republished under its MIT licence (© github). 930 words, ~2,098 tokens.
Download SKILL.mdSave it as
.claude/skills/update-llms/SKILL.md (or your agent's skills folder).- name
- update-llms
- description
- Update the llms.txt file in the root folder to reflect changes in documentation or specifications following the llms.txt specification at https://llmstxt.org/
Update LLMs.txt File
Update the existing llms.txt file in the root of the repository to reflect changes in documentation, specifications, or repository structure. This file provides high-level guidance to large language models (LLMs) on where to find relevant content for understanding the repository's purpose and specifications.
Primary Directive
Update the existing llms.txt file to maintain accuracy and compliance with the llms.txt specification while reflecting current repository structure and content. The file must remain optimized for LLM consumption while staying human-readable.
Analysis and Planning Phase
Before updating the llms.txt file, you must complete a thorough analysis:
Step 1: Review Current File and Specification
- Read the existing
llms.txtfile to understand current structure - Review the official specification at https://llmstxt.org/ to ensure continued compliance
- Identify areas that may need updates based on repository changes
Step 2: Repository Structure Analysis
- Examine the current repository structure using appropriate tools
- Compare current structure with what's documented in existing
llms.txt - Identify new directories, files, or documentation that should be included
- Note any removed or relocated files that need to be updated
Step 3: Content Discovery and Change Detection
- Identify new README files and their locations
- Find new documentation files (
.mdfiles in/docs/,/spec/, etc.) - Locate new specification files and their purposes
- Discover new configuration files and their relevance
- Find new example files and code samples
- Identify any changes to existing documentation structure
Step 4: Create Update Plan
Based on your analysis, create a structured plan that includes:
- Changes needed to maintain accuracy
- New files to be added to the llms.txt
- Outdated references to be removed or updated
- Organizational improvements to maintain clarity
Implementation Requirements
Format Compliance
The updated llms.txt file must maintain this exact structure per the specification:
- H1 Header: Single line with repository/project name (required)
- Blockquote Summary: Brief description in blockquote format (optional but recommended)
- Additional Details: Zero or more markdown sections without headings for context
- File List Sections: Zero or more H2 sections containing markdown lists of links
Content Requirements
Required Elements
- Project Name: Clear, descriptive title as H1
- Summary: Concise blockquote explaining the repository's purpose
- Key Files: Essential files organized by category (H2 sections)
File Link Format
Each file link must follow: [descriptive-name](relative-url): optional description
Section Organization
Organize files into logical H2 sections such as:
- Documentation: Core documentation files
- Specifications: Technical specifications and requirements
- Examples: Sample code and usage examples
- Configuration: Setup and configuration files
- Optional: Secondary files (special meaning - can be skipped for shorter context)
Content Guidelines
Language and Style
- Use concise, clear, unambiguous language
- Avoid jargon without explanation
- Write for both human and LLM readers
- Be specific and informative in descriptions
File Selection Criteria
Include files that:
- Explain the repository's purpose and scope
- Provide essential technical documentation
- Show usage examples and patterns
- Define interfaces and specifications
- Contain configuration and setup instructions
Exclude files that:
- Are purely implementation details
- Contain redundant information
- Are build artifacts or generated content
- Are not relevant to understanding the project
Execution Steps
Step 1: Current State Analysis
- Read the existing
llms.txtfile thoroughly - Examine the current repository structure completely
- Compare existing file references with actual repository content
- Identify outdated, missing, or incorrect references
- Note any structural issues with the current file
Step 2: Content Planning
- Determine if the primary purpose statement needs updates
- Review and update the summary blockquote if needed
- Plan additions for new files and directories
- Plan removals for outdated or moved content
- Reorganize sections if needed for better clarity
Show full SKILL.md (351 more words)Show less
Step 3: File Updates
- Update the existing
llms.txtfile in the repository root - Maintain compliance with the exact format specification
- Add new file references with appropriate descriptions
- Remove or update outdated references
- Ensure all links are valid relative paths
Step 4: Validation
- Verify continued compliance with https://llmstxt.org/ specification
- Check that all links are valid and accessible
- Ensure the file still serves as an effective LLM navigation tool
- Confirm the file remains both human and machine readable
Quality Assurance
Format Validation
- ✅ H1 header with project name
- ✅ Blockquote summary (if included)
- ✅ H2 sections for file lists
- ✅ Proper markdown link format
- ✅ No broken or invalid links
- ✅ Consistent formatting throughout
Content Validation
- ✅ Clear, unambiguous language
- ✅ Comprehensive coverage of essential files
- ✅ Logical organization of content
- ✅ Appropriate file descriptions
- ✅ Serves as effective LLM navigation tool
Specification Compliance
- ✅ Follows https://llmstxt.org/ format exactly
- ✅ Uses required markdown structure
- ✅ Implements optional sections appropriately
- ✅ File located at repository root (
/llms.txt)
Update Strategy
Addition Process
When adding new content:
- Identify the appropriate section for new files
- Create clear, descriptive names for links
- Write concise but informative descriptions
- Maintain alphabetical or logical ordering within sections
- Consider if new sections are needed for new content types
Removal Process
When removing outdated content:
- Verify files are actually removed or relocated
- Check if relocated files should be updated rather than removed
- Remove entire sections if they become empty
- Update cross-references if needed
Reorganization Process
When restructuring content:
- Maintain logical flow from general to specific
- Keep essential documentation in primary sections
- Move secondary content to "Optional" section if appropriate
- Ensure new organization improves LLM navigation
Example structure for llms.txt:
# [Repository Name]
> [Concise description of the repository's purpose and scope]
[Optional additional context paragraphs without headings]
## Documentation
- [Main README](README.md): Primary project documentation and getting started guide
- [Contributing Guide](CONTRIBUTING.md): Guidelines for contributing to the project
- [Code of Conduct](CODE_OF_CONDUCT.md): Community guidelines and expectations
## Specifications
- [Technical Specification](spec/technical-spec.md): Detailed technical requirements and constraints
- [API Specification](spec/api-spec.md): Interface definitions and data contracts
## Examples
- [Basic Example](examples/basic-usage.md): Simple usage demonstration
- [Advanced Example](examples/advanced-usage.md): Complex implementation patterns
## Configuration
- [Setup Guide](docs/setup.md): Installation and configuration instructions
- [Deployment Guide](docs/deployment.md): Production deployment guidelines
## Optional
- [Architecture Documentation](docs/architecture.md): Detailed system architecture
- [Design Decisions](docs/decisions.md): Historical design decision recordsSuccess Criteria
The updated llms.txt file should:
- Accurately reflect the current repository structure and content
- Maintain compliance with the llms.txt specification
- Provide clear navigation to essential documentation
- Remove outdated or incorrect references
- Include new important files and documentation
- Maintain logical organization for easy LLM consumption
- Use clear, unambiguous language throughout
- Continue to serve both human and machine readers effectively
© github, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
Just SKILL.md in skills/update-llms of github/awesome-copilot.
Open the folder on GitHubat commit 727ff2e
Used in 2 other repositories
We found 2 copies of this SKILL.md (exact, near-identical or edited) in other folders, from 2 other GitHub owners. This page covers the copy in github/awesome-copilot, which our catalogue first saw on October 7, 2026.
Compare with similar skills
Update LLMs next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Update LLMs this skillgithub/awesome-copilot | 40k | 2 repos | ~2.1k | Automated safety check: Pass | MIT | |
| Geo Fundamentalswasp-lang/wasp | 19k | 8 repos | ~861 | Automated safety check: Pass | MIT | |
| SEO GeoReScienceLab/opc-skills | 1.8k | 4 repos | ~2.1k | Automated safety check: Pass | Apache-2.0 | |
| GEO-First SEO Audit Toolzubair-trabzada/geo-seo-claude | 11k | — | ~2.8k | Automated safety check: Notes | MIT | |
| GEO Monthly Delta Reportzubair-trabzada/geo-seo-claude | 11k | — | ~2.4k | Automated safety check: Notes | MIT | |
| SEO DataforseoAgriciDaniel/codex-seo | 787 | 2 repos | ~4.6k | Automated safety check: Pass | MIT |
Similar skills
SEO Geo
ReScienceLab/opc-skills
SEO & GEO (Generative Engine Optimization) for websites. An agent skill from ReScienceLab/opc-skills.
GEO-First SEO Audit Tool
zubair-trabzada/geo-seo-claude
Audits a website for AI search visibility across ChatGPT, Claude, Perplexity and Google AI Overviews while checking traditional SEO, schema and E-E-A-T content quality.
GEO Monthly Delta Report
zubair-trabzada/geo-seo-claude
Compares a baseline and a current GEO audit for a client, calculates score changes and action item progress, and writes a monthly progress report.
SEO Dataforseo
AgriciDaniel/codex-seo
Live SEO data via DataForSEO MCP server. An agent skill from AgriciDaniel/codex-seo.
Fire Your SEO Agency
leopard627/fire-your-seo-agency
SEO·AEO·GEO·LLMO·NEO(네이버) 다섯 레인을 진단하고 직접 구현하며, 인용되는 콘텐츠를 계속 생산하는 서브 블로그·콘텐츠 운영 파이프라인까지 세팅하는 스킬.
More from github/awesome-copilot
All 417 skills in this repo- Official
Acquire Codebase Knowledge
github/awesome-copilot
Maps an unfamiliar codebase into seven evidence-backed documents in docs/codebase/, using a scan script and templates, for onboarding or architecture write-ups.
- Official
Azure Architecture Autopilot
github/awesome-copilot
Designs Azure infrastructure from a natural-language description, or diagrams an existing resource group, then refines the design through conversation and deploys it with Bicep.
- Official
Draw.io Diagram Generator
github/awesome-copilot
Generates, edits and validates draw.io files with correct mxGraph XML, covering flowcharts, architecture, sequence, ER and UML class diagrams.
- Official
Credit Risk Data Cleaning
github/awesome-copilot
Cleans raw credit data and screens variables before loan modeling, dropping unstable, noisy or redundant features and writing an Excel report of every step.
- Official
Daily Focus Board
github/awesome-copilot
Builds a warm, browser-based daily focus board the user updates by talking to their agent, with Eisenhower priorities, a brain-dump box and kind not-today carryover.
- Official
Python Pypi Package Builder
github/awesome-copilot
End-to-end skill for building, testing, linting, versioning, and publishing a production-grade Python library to PyPI.
Related
Categories
Questions about Update LLMs
What does Update LLMs do?
Update the llms.txt file in the root folder to reflect changes in documentation or specifications following the llms.txt specification at https://llmstxt.org/. Update LLMs is an agent skill from github/awesome-copilot, published by the product's own GitHub organization.
When should I use Update LLMs?
Update LLMs fits situations like: tasks that involve AI search optimization.
How do I install Update LLMs in Claude Code?
Run `npx skills add github/awesome-copilot --skill update-llms -a claude-code`. Or copy the skill folder (skills/update-llms in github/awesome-copilot) into .claude/skills/update-llms in your project. Claude Code loads it when a task matches its description.
How do I install Update LLMs in Codex?
Run `npx skills add github/awesome-copilot --skill update-llms -a codex`. Or copy the skill folder (skills/update-llms in github/awesome-copilot) into .agents/skills/update-llms in your project. Codex loads it when a task matches its description.
Can I use Update LLMs in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add github/awesome-copilot --skill update-llms -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/update-llms, .gemini/skills/update-llms, .github/skills/update-llms and .opencode/skills/update-llms in your project.
What does Update LLMs need to run?
SKILL.md names no scripts, command-line tools or credentials: Update LLMs is instructions for the agent only.
Does Update LLMs access the network?
SKILL.md names 1 domain. As links in the text: llmstxt.org. This is read from the text; nothing was executed.
Is Update LLMs safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Update LLMs use?
Update LLMs is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Update LLMs use?
About 2.1k tokens (SKILL.md is roughly 8.4k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Update LLMs?
Skills that share tags, products or a category with Update LLMs: Geo Fundamentals (wasp-lang/wasp, 19k stars), SEO Geo (ReScienceLab/opc-skills, 1.8k stars), GEO-First SEO Audit Tool (zubair-trabzada/geo-seo-claude, 11k stars) and GEO Monthly Delta Report (zubair-trabzada/geo-seo-claude, 11k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Update LLMs?
github (a GitHub organization, an official publisher) maintains it in github/awesome-copilot, which has 39,748 GitHub stars. The repository holds 417 skills in this directory. The repository was last updated on October 7, 2026.
Source: github/awesome-copilot on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.