skills.rest
hhellbusch
hhellbuschCOMMUNITY
Explore all skills by this author →
GitHub

audit

Detect broken internal links, registry mismatches, orphaned content, and stale references in documentation.

7|Updated Feb 3, 2026
Search Tags:#documentation#audit#content integrity#link verification#registry alignment
One-click install
npx skills add https://github.com/hhellbusch/my-ai-workspace --skill audit-hhellbusch
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: audit
Source: https://github.com/hhellbusch/my-ai-workspace/tree/main/.agents/skills/audit
Command: npx skills add https://github.com/hhellbusch/my-ai-workspace --skill audit-hhellbusch

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

Content audits often miss broken links, outdated information, and inconsistencies; this Skill addresses those gaps by systematically checking workspace content for issues, helping maintain high-quality, reliable documentation and data.

Core Features & Use Cases

  • Link Integrity Verification: Checks all markdown files for broken internal links, ensuring navigability.
  • Registry and Inventory Alignment: Compares documented project contents with on-disk files, highlighting discrepancies.
  • Cross-Reference Detection: Identifies orphaned files and missing links between related documents; facilitates comprehensive content mapping.
  • Use Case: In a large documentation project, regularly run this Skill to ensure all links are functional and inventories are synchronized, reducing broken references.

Quick Start

Run the audit tool in your workspace to scan all markdown files for broken links and configuration mismatches immediately.

Frequently Asked Questions about audit

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

FAQPage Schema
How do I check for broken internal links in markdown documentation?▼

To check for broken internal links in markdown documentation, you can run an automated audit that scans all workspace files to detect and report invalid cross-references, ensuring navigability and content integrity.

What is the best way to find orphaned content and stale references in a project repository?▼

Finding orphaned content and stale references in a project repository involves scanning directory structures and markdown files to identify disconnected documents and outdated configuration mappings.

How do I verify registry alignment between documented inventories and on-disk files?▼

Verifying registry alignment compares documented project contents with actual on-disk files using configuration checks, highlighting discrepancies to synchronize your inventory and maintain data coherence.

Can I detect cross-reference gaps across project configuration files and markdown directories?▼

Yes, you can detect cross-reference gaps by scanning project configuration files and markdown directories, which identifies missing links between related documents and maps comprehensive content structures.

What types of content issues does a workspace documentation audit identify?▼

A workspace documentation audit identifies broken internal links, registry mismatches, orphaned content, and stale references across markdown files and project configurations to maintain overall correctness.

Related Skills

Explore More Content & Communication Skills→
royhenengelroyhenengel

status

Scan directory structures and Markdown files to generate project status reports.

Community
Intermediate
OmarHosamCodesOmarHosamCodes
1

wiki-lint

Audit Obsidian vaults for orphaned pages, broken links, and frontmatter issues.

Community
Advanced
vlad-ryzhkovvlad-ryzhkov
25

doc-lint

Audit Markdown documentation for structure, size, duplicates, and SSOT violations.

Community
Intermediate
deepakbunkardeepakbunkar

blog-audit

Audit markdown blog content for quality, SEO, freshness, and link health.

Community
Advanced