skills.rest
baekenough
baekenoughCOMMUNITY
Explore all skills by this author →
GitHub

omcustom:update-docs

Validate and update AGENT.md, SKILL.md, CLAUDE.md, index.yaml to match repository structure.

13|6|Updated Apr 14, 2026
Search Tags:#documentation#validation#sync#project-structure#cross-reference#agent-skill
One-click install
npx skills add https://github.com/baekenough/second-brain --skill omcustom-update-docs
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: omcustom:update-docs
Source: https://github.com/baekenough/second-brain/tree/main/.claude/skills/update-docs
Command: npx skills add https://github.com/baekenough/second-brain --skill omcustom-update-docs

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Keeps all project documentation (AGENT.md, SKILL.md, index.yaml, CLAUDE.md) in sync with the actual codebase and ensures consistent agent-to-skill-to-guide relationships.

Core Features & Use Cases

  • Documentation validation: checks that all docs reference existing agents, skills, and guides and that counts reflect the repository state.
  • Cross-reference integrity: maintains accurate mappings between agents, skills, and guides and updates CLAUDE.md summaries.
  • Organic integration checks: verifies end-to-end mappings and flags orphaned or misaligned resources for remediation.
  • Use case: when a skill is renamed or moved, the workflow updates references and CLAUDE.md to reflect the change, preserving a coherent documentation graph.

Quick Start

Execute the update-docs command to validate and synchronize all documentation with the current project structure.

Frequently Asked Questions about omcustom:update-docs

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

FAQPage Schema
How do I keep documentation in sync when renaming or moving project files?▼

Documentation validation checks that all project docs reference existing agents, skills, and guides, ensuring counts and mappings accurately reflect the current repository state.

What causes broken cross-references between agents, skills, and guides?▼

Broken cross-references occur when resources are renamed or reorganized without updating the documentation graph, requiring a validation scan to detect and fix orphaned or misaligned mappings.

How do I validate AGENT.md and CLAUDE.md against the current repository state?▼

You validate AGENT.md and CLAUDE.md by executing an update workflow that scans the repository structure to detect discrepancies and applies updates to align summaries and references.

Does documentation synchronization require a model invocation to run?▼

Documentation synchronization does not require a model invocation, as the update-docs workflow operates purely by scanning the repository structure, detecting discrepancies, and applying updates directly.

What is the best way to detect orphaned agents and skills in a project?▼

The best way to detect orphaned agents and skills is to run an organic integration check that verifies end-to-end mappings and flags misaligned resources for remediation.

Related Skills

Explore More Content & Communication Skills→
wormholecowboywormholecowboy
1

builder-resume

Load the current plan and validate its directory to resume work.

Community
Basic
tronghieutronghieu
36

lumi-check

Run the Lumina-Wiki linter in JSON mode and classify findings by severity.

Community
Advanced
LukasStricklerLukasStrickler
4

docs-check

Analyze git diffs to identify required documentation updates after code changes.

Community
Basic
Everyone-Needs-A-CopilotEveryone-Needs-A-Copilot
13

link-validation

Validate Markdown links, anchors, and cross-references across repository files.

Official
Basic