knowledge-map

Audits governance docs for missing references and broken links.

1|Updated Nov 27, 2025
One-click install
npx skills add https://github.com/buenhyden/hy-home.k8s --skill knowledge-map
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: knowledge-map
Source: https://github.com/buenhyden/hy-home.k8s/tree/main/.agents/skills/knowledge-map
Command: npx skills add https://github.com/buenhyden/hy-home.k8s --skill knowledge-map

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Maintain the governance knowledge base for hy-home.k8s: keep AGENTS.md, harness-catalog, stage README files, and cross-links consistent and up-to-date. Detect stale documents, broken references, and coverage gaps across docs/00.agent-governance/ and stage directories.

Core Features & Use Cases

  • Audit governance artifacts in .claude/skills and .claude/agents to ensure alignment with on-disk entries.
  • Detect broken cross-links, missing artifacts, and coverage gaps across docs stage READMEs and harness catalog.
  • Produce a gap report and actionable fixes to keep the knowledge base current.

Quick Start

Audit governance docs across AGENTS.md, harness-catalog, and docs stage READMEs and repair broken links.

Frequently Asked Questions about knowledge-map

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

FAQPage Schema
How do I audit governance documentation for broken cross-links and missing references?

To audit governance documentation drift, scan AGENTS.md, harness-catalog, and stage READMEs for missing artifacts and broken cross-links. This generates a gap report identifying stale documents, orphaned files, and coverage gaps to guide targeted fixes.

What is documentation drift in a governance knowledge base?

Documentation drift in a governance knowledge base happens when on-disk artifacts in .claude/skills and .claude/agents become misaligned with documented references. It results in broken cross-links, outdated stage READMEs, and orphaned files.

Does the governance audit cover stage READMEs and harness catalog entries?

Yes, the governance audit covers stage READMEs, harness-catalog, and AGENTS.md. It verifies stage READMEs link to existing artifacts, detects orphaned files in docs/00.agent-governance, and checks alignment with on-disk entries across .claude directories.

What's the best way to fix broken references in AGENTS.md and stage directories?

The best way to fix broken references is to run an audit across AGENTS.md, harness-catalog, and stage directories to detect coverage gaps and orphaned files. The resulting gap report provides actionable fixes to repair links and update stale documents.

How do I detect orphaned files in docs/00.agent-governance and stage directories?

Detecting orphaned files requires auditing docs/00.agent-governance and stage READMEs to find artifacts not referenced by cross-links. The audit identifies isolated files and flags missing references to ensure complete knowledge base coverage.

Why does my governance knowledge base have stale documents after updating agents?

Stale documents appear when agent or skill updates are not reflected in governance artifacts like AGENTS.md and harness-catalog. Auditing documentation drift detects outdated references and coverage gaps, generating a report to synchronize the knowledge base.