DO

Enforces documentation file structure and governance rules to prevent stray files.

Install

mkdir -p .claude/skills/docs-governance && curl -L -o skill.zip "https://agentskills.codes/api/skills/download/14523" && unzip -o skill.zip -d .claude/skills/docs-governance && rm skill.zip

Installs to .claude/skills/docs-governance

Activation

This is the description your AI agent reads to decide when to run this skill — the better it matches your request, the more reliably it fires.

Before creating, renaming, or moving any `.md` file outside `src/`, or when the user says \"stray docs\", \"docs governance\", \"where should this doc live\", or runs the stray-doc auditor: invoke `Skill('docs-governance')` and place the file using its vault-synced allowlist and filename-heuristic table.
305 chars✓ has a “when” triggerlonger than Claude Code's old 250-char listing cap (fine on current versions)
Beginner

Key capabilities

  • →Place non-code documentation in authorized paths
  • →Identify and move stray `.md` files
  • →Propose target locations using filename heuristics
  • →Update internal links after moving files
  • →Generate an inventory of skills, commands, and agents

How it works

The skill identifies stray `.md` files by comparing all `.md` files against an allowlist of authorized paths. It then uses filename heuristics to propose a target location and performs a `git mv` operation, updating internal links.

Inputs & outputs

You give it
A `.md` file outside the authorized documentation paths
You get back
The `.md` file moved to an authorized path and internal links updated

When to use docs-governance

  • →Fixing stray documentation files
  • →Organizing project docs
  • →Moving documentation to standard locations

About docs-governance

Ensures all non-code documentation lives in authorized paths. Syncs documentation into the vault to provide a central repository overview.

Before creating, renaming, or moving any `.md` file outside `src/`, or when the user says \"stray docs\", \"docs governance\", \"where should this doc live\", or runs the stray-doc auditor: invoke `Skill('docs-governance')` and place the file using its vault-synced allowlist and filename-heuristic t

When not to use it

  • →The file is inline code comments in `src/**`
  • →The file is a tool-specific config like `.github/copilot-instructions.md`
  • →The file is a scoped `AGENTS.md` (e.g., `server/AGENTS.md`)

Limitations

  • →Requires user confirmation before moving files
  • →Does not automatically delete files; requires user decision
  • →Filename heuristics are a guide, not a definitive rule

How it compares

This skill enforces a structured documentation governance policy by automatically identifying and relocating non-compliant `.md` files, ensuring all documentation is discoverable within a vault-synced system.

Compared to similar skills

docs-governance side by side with the closest alternatives in the catalog.

SkillInstallsUpdatedSafetyDifficulty
docs-governance (this skill)04moReviewBeginner
marker228moReviewBeginner
markdown-converter54moReviewBeginner
enhance-claude-memory117moReviewBeginner

Try saying

Example prompts that trigger this skill in your AI assistant.

Search skills

Search the agent skills registry