check-llms-drift

Detect stale and orphaned llms.txt entries against Cargo and npm dependencies.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/jmagar/rust-bin --skill check-llms-drift
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: check-llms-drift
Source: https://github.com/jmagar/rust-bin/tree/main/.claude/skills/check-llms-drift
Command: npx skills add https://github.com/jmagar/rust-bin --skill check-llms-drift

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

Audit docs/references llms.txt entries for drift and staleness.

Core Features & Use Cases

  • Detect stale entries based on generated frontmatter or gitmtime.
  • Identify orphaned references not present in Cargo.lock / Cargo.toml or package.json.
  • Optional: verify dependency version drift against crates.io / npm and flag updates.

Quick Start

Run the script to perform an automated drift scan of docs/references llms.txt entries.

Frequently Asked Questions about check-llms-drift

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

FAQPage Schema
How do I detect stale entries in my llms.txt documentation?

You can detect staleness in llms.txt docs by parsing YAML frontmatter and cross-referencing dependencies against Cargo.toml or package.json. The audit flags outdated references and orphaned entries using generated metadata or gitmtime.

How do I identify orphaned references in a Rust and web monorepo?

You can identify orphaned references by cross-referencing llms.txt entries against Cargo.lock, Cargo.toml, and apps/web/package.json. The audit flags documentation references that are missing from your actual project dependency lockfiles.

Can I verify dependency version drift against crates.io and npm?

Yes, you can optionally verify dependency version drift against crates.io and npm. The audit cross-references your lockfiles to flag available updates and version mismatches for documented dependencies.

What is documentation drift in LLM references?

Documentation drift in LLM references happens when llms.txt entries become outdated or orphaned from the codebase. This occurs when dependencies change in Cargo.toml or package.json but the documentation is not synchronized.

Does the drift audit work without external registry checks?

Yes, the drift audit works locally by parsing YAML frontmatter and cross-referencing Cargo.lock or package.json. Verifying dependency version drift against crates.io and npm registries is strictly an optional feature.