doc-keeper

Validate MCP Registry, agent specs, skill paths, and vault entries for consistency.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/TalkingMonkeyOz/claude-family --skill doc-keeper
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: doc-keeper
Source: https://github.com/TalkingMonkeyOz/claude-family/tree/main/.claude/skills/doc-keeper
Command: npx skills add https://github.com/TalkingMonkeyOz/claude-family --skill doc-keeper

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps maintain the accuracy and currency of documentation, vault entries, and configuration registries across Claude Family deployments, reducing drift and manual auditing.

Core Features & Use Cases

  • MCP Registry Verification: Cross-check the knowledge-vault/MCP Registry.md against the global ~/.claude.json mcpServers and per-project configurations, ensuring consistency.
  • Agent Spec Verification: Validate that all agent_types have corresponding configs, that removed agents are accurately tracked, and that token cost estimates are reasonable.
  • Skill Path Verification: Ensure every skill under .claude/skills/ has a skill.md and that references in docs correctly point to existing skills.
  • Vault Entry Validation: Identify knowledge-vault entries with outdated timestamps, broken wiki links, or missing related entries to keep the vault healthy.

Quick Start

Review the Documentation Keeper findings report and address any flagged items related to MCP Registry, agent specs, skill paths, and vault entries.

Frequently Asked Questions about doc-keeper

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

FAQPage Schema
How do I verify documentation consistency across MCP Registry, agent specs, and skill paths?

Documentation Keeper cross-checks your MCP Registry, global ~/.claude.json mcpServers, per-project .mcp.json files, and skill.md presence to detect inconsistencies, stale entries (synced_at > 30 days), and broken references, surfacing discrepancies for remediation.

What's the best way to audit vault entries and detect outdated knowledge-vault data?

The Skill validates knowledge-vault entries by checking timestamps, identifying stale records older than 30 days, verifying wiki link integrity, and confirming related entries exist, flagging items that need refresh or removal.

Can I validate that agent configurations match their specs across deployments?

Yes. The Skill verifies agent_types have corresponding configs, ensures removed agents are tracked accurately, validates token cost estimates are reasonable, and surfaces configuration drift between global and project-specific settings.

How do I ensure every skill has required documentation and correct references?

Skill Path Verification checks that all skills under .claude/skills/ have accompanying skill.md files and validates that documentation references point to existing skills, catching orphaned or misconfigured skill paths.

What happens if my MCP Registry gets out of sync with deployed configurations?

Documentation Keeper detects registry drift by comparing knowledge-vault/MCP Registry.md against active mcpServers in ~/.claude.json and project configs, reporting mismatches so you can realign documentation with actual deployments.

Do I need existing documentation files for this Skill to work?

The Skill works with existing MCP Registry files, .mcp.json configs, agent specs, and knowledge vaults; it validates their consistency and integrity but requires those sources to already be in place to cross-reference.