ln-600-docs-auditor

Audit project documentation across eight quality categories and output compliance scores.

1|Updated Feb 19, 2026
One-click install
npx skills add https://github.com/mcauduro0/Macro_Trading --skill ln-600-docs-auditor-mcauduro0
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ln-600-docs-auditor
Source: https://github.com/mcauduro0/Macro_Trading/tree/main/.claude/skills/ln-600-docs-auditor
Command: npx skills add https://github.com/mcauduro0/Macro_Trading --skill ln-600-docs-auditor-mcauduro0

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill addresses the challenge of maintaining high-quality, accurate, and concise project documentation by systematically auditing its structure, content, and adherence to standards.

Core Features & Use Cases

  • Comprehensive Audit: Evaluates documentation across 8 critical categories, including hierarchy, single source of truth, compression, requirements compliance, actuality, legacy cleanup, stack adaptation, and semantic content.
  • Automated Scoring: Provides a compliance score out of 10 for each category and an overall score, highlighting areas for improvement.
  • Actionable Insights: Generates detailed findings and recommended actions to enhance documentation quality.
  • Use Case: After a major documentation update for a new feature, run this Skill to ensure all new and existing documents are well-structured, accurate, and easy to understand before release.

Quick Start

Use the ln-600-docs-auditor skill to audit the documentation quality of the current project.

Frequently Asked Questions about ln-600-docs-auditor

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

FAQPage Schema
How do I audit documentation quality and compliance for my software project?

To audit documentation quality, this Skill evaluates project docs across eight categories including hierarchy, single source of truth, and requirements compliance. It outputs an automated compliance score per category and generates actionable findings for improvement.

What categories are evaluated during a technical writing structure audit?

A documentation structure audit evaluates hierarchy, single source of truth, compactness, requirements compliance, actuality, legacy cleanup, stack adaptation, and semantic content. Each category receives a compliance score out of ten to highlight specific structural weaknesses.

How do I check if my project docs follow a single source of truth and remove legacy content?

You can check for a single source of truth and perform legacy cleanup by running this audit. It systematically reviews your documentation to identify redundant information and outdated content, providing recommended actions to consolidate and update your files.

How does semantic content verification work during a documentation review?

Semantic content verification is handled by delegating deep analysis to a specialized semantic content auditor. The primary audit focuses on structural and compliance metrics, while the delegated tool handles the underlying meaning and technical accuracy of the text.

When should I run a documentation compliance audit in my development workflow?

You should run a documentation compliance audit after major updates or before a new feature release. This ensures all newly added and existing documents maintain structural compactness, adhere to requirements, and remain accurately adapted to your current tech stack.