maintain-agent-docs

Maintain AGENTS.md and CLAUDE.md guidance by removing duplication and enforcing context budgets.

931|91|Updated Aug 13, 2025
One-click install
npx skills add https://github.com/videojs/v10 --skill maintain-agent-docs
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: maintain-agent-docs
Source: https://github.com/videojs/v10/tree/main/.agents/skills/maintain-agent-docs
Command: npx skills add https://github.com/videojs/v10 --skill maintain-agent-docs

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Agent guidance files like AGENTS.md and CLAUDE.md tend to accumulate duplicated instructions, drift out of sync with executable sources, and bloat context budgets. This Skill keeps repository agent documentation as a lean routing and correction layer instead of a second documentation system.

Core Features & Use Cases

  • Placement Rules: Directs durable facts to the nearest AGENTS.md, keeps CLAUDE.md as an @AGENTS.md alias, and routes repeatable workflows into skills under .agents/skills/.
  • Drift and Duplication Cleanup: Searches existing agent docs for overlap or contradiction, prefers updating source pointers and validators over copying content, and removes obsolete guidance in the same change.
  • Validation Workflow: Runs pnpm check:workspace and reviews reported context budgets after changes.
  • Use Case: When setup instructions are duplicated across AGENTS.md, CLAUDE.md, and a skill, use this Skill to consolidate them into pointers to executable sources with passing validators.

Quick Start

Use the maintain-agent-docs skill to remove duplicated setup instructions from the agent guidance files and verify the context budget report.

Frequently Asked Questions about maintain-agent-docs

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

FAQPage Schema
How do I reduce duplication across AGENTS.md and CLAUDE.md files?

Keep each CLAUDE.md as an @AGENTS.md alias unless Claude-only behavior is genuinely required, and put durable facts in the nearest AGENTS.md. Replace copied commands or schemas with pointers to executable sources and validators.

Where should I put new agent instructions in a repository?

Place durable, broadly applicable facts in the nearest AGENTS.md, repeatable vertical workflows in a skill under .agents/skills/, and mechanically checkable rules in code, tests, lint, or hooks. Only add a rule when an agent would plausibly get the repository wrong without it.

How do I validate agent documentation changes in this repo?

Run pnpm check:workspace after editing agent docs or skills and review the reported context budgets. The workspace check script mechanically verifies guidance constraints.

When should agent guidance become a skill instead of an AGENTS.md entry?

Use a skill for explicit, repeatable vertical workflows, while AGENTS.md holds durable routing facts. Checked-in skills live as direct children of .agents/skills/, with .claude/skills/ and .opencode/skills/ treated as generated aliases.

What belongs in skill frontmatter for portability?

Keep skill frontmatter limited to a name and a precise description. Avoid adding tool-specific fields so the skill remains portable across agent platforms.