repo-knowledge-audit

Audit repository Markdown documentation and generate a prioritized findings report.

Updated Apr 3, 2026
One-click install
npx skills add https://github.com/kirvin/agent-dev-harness --skill repo-knowledge-audit
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: repo-knowledge-audit
Source: https://github.com/kirvin/agent-dev-harness/tree/main/plugins/kf/skills/repo-knowledge-audit
Command: npx skills add https://github.com/kirvin/agent-dev-harness --skill repo-knowledge-audit

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill audits a repository's documentation to identify gaps, stale references, token bloat, and missing content for agent efficiency, helping to produce a prioritized findings report.

Core Features & Use Cases

  • Documentation Audit: Identifies issues like broken links, wrong information, and missing content.
  • Prioritized Report: Generates a report with prioritized findings for fixes.
  • Use Case: Before using kf:repo-knowledge-architect to design fixes, run this skill to analyze the repository's documentation and understand the areas that need improvement.

Quick Start

Run the kf:repo-knowledge-audit skill to perform an audit on your repository's documentation.

Frequently Asked Questions about repo-knowledge-audit

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

FAQPage Schema
How do I audit my repository documentation for agent efficiency issues?

To audit repository documentation for agent efficiency, run this skill to analyze Markdown files and compare them against expected content models. It identifies missing content, broken references, and token bloat to produce a prioritized findings report.

What documentation issues affect agent efficiency in a codebase?

Documentation issues affecting agent efficiency include missing content, broken references, stale information, and token bloat. This skill detects these problems by analyzing Markdown files and comparing them against expected content models.

How do I generate a prioritized report for fixing broken links and missing content in my repo?

You can generate a prioritized findings report by running this documentation audit skill. It analyzes your Markdown files to identify broken references, missing content, and token bloat, then outputs a report prioritized for improvement.

When should I run a repository documentation audit before designing fixes?

Run a repository documentation audit before designing fixes to understand the specific areas needing improvement. It provides a prioritized findings report that serves as the foundation for subsequent architecture and fix design steps.

Does this documentation audit work with Markdown files only?

Yes, this documentation audit specifically analyzes Markdown files within your repository. It compares them against expected content models to identify gaps, broken references, and token bloat that impact agent efficiency.