legibility--auditor

Name: legibility--auditor
Availability: InStock
Author: Pattern

Audit repository documentation coverage and agent-readiness against the Agent Readiness checklist.

57|3|Updated Mar 30, 2026

Search Tags:#documentation #onboarding #audit #autonomy #agents.md #repo-structure #legibility

Ready to run

npx skills add https://github.com/patterninc/code-mint --skill legibility-auditor

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: legibility--auditor
Source: https://github.com/patterninc/code-mint/tree/main/.agents/skills/legibility--auditor
Command: npx skills add https://github.com/patterninc/code-mint --skill legibility-auditor

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Audits a repository's documentation coverage and agent-readiness to ensure autonomous navigation and robust onboarding of codebases.

Core Features & Use Cases

Evaluates repository structure for AGENTS.md presence, root and path-specific guidance, and the clarity of UX intent.
Generates an Agent Readiness Report detailing gaps, risks, and recommended improvements.
Helps onboarding teams align documentation with agent-first practices across subdirectories.

Quick Start

Run legibility--auditor against the onboarding scope to generate the Agent Readiness Report.

Frequently Asked Questions about legibility--auditor

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

FAQPage Schema

How do I audit my repository documentation for agent readiness?▼

To audit repository documentation for agent readiness, evaluate AGENTS.md placement, progressive disclosure quality, and UX intent documentation to produce a comprehensive Legibility Audit Report detailing findings and remediation steps.

What is repo legibility and why does it matter for autonomous agents?▼

Repo legibility is the measure of how easily autonomous agents can navigate a codebase through proper documentation coverage. It matters because clear AGENTS.md guidance and documented UX intent enable robust onboarding and autonomous operation.

How do I check if my AGENTS.md files are configured correctly for onboarding?▼

Check AGENTS.md configuration by auditing root and path-specific guidance across subdirectories. The audit surfaces gaps in progressive disclosure and identifies where local AGENTS.md files are needed to support agent onboarding.

Does the agent readiness audit work for repositories with complex subdirectory structures?▼

Yes, the agent readiness audit evaluates path-specific guidance across subdirectories to surface hidden assumptions impacting agent navigation. It aligns documentation with agent-first practices across the entire onboarding scope.

What is the best way to surface hidden assumptions impacting agent navigation in a codebase?▼

The best way to surface hidden assumptions impacting agent navigation is to apply a legibility audit to the onboarding scope. This evaluates documentation coverage and checks compliance against the Agent Readiness checklist.

What should be included in a legibility audit report for repository onboarding?▼

A legibility audit report should include findings on missing files, documentation gaps, risks, and recommended remediation steps. It must detail AGENTS.md placement issues and areas lacking progressive disclosure or UX intent clarity.