How do I install the Context Audit skill?

Run npx skillmds add majiayu000/context-audit in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Context Audit safe to use?

This skill has not completed SkillMD's automated safety review yet. Capability flags: reads secrets. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Context Audit?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Context Audit free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Context Audit?

majiayu000 (@majiayu000) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Context Audit by majiayu000 — Agent Skill

Name: Context Audit
Rating: 4.666666666666667 (3 reviews)
Author: majiayu000

File contents

LLM Context Comprehensive Audit

Performs deep quality audits of CLAUDE.md context files, checking structure, content quality, efficiency, design doc references, and compliance with standards.

Overview

This skill provides comprehensive quality auditing for LLM context files by running all validation checks, analyzing content efficiency, verifying design doc pointers, checking line limits, and generating detailed audit reports with prioritized recommendations.

Quick Start

Audit all context files:

/context-audit

Audit specific file:

/context-audit CLAUDE.md

Audit package context:

/context-audit pkgs/effect-type-registry/CLAUDE.md

Quick audit (non-strict):

/context-audit --strict=false

Parameters

Optional

target: Path to CLAUDE.md file or "all" (default: all)
strict: Enable strict mode with additional checks (default: true)
check-refs: Validate design doc references exist (default: true)
output: Output file path for audit report

Workflow

High-level audit process:

Parse parameters to determine audit scope and strictness
Load design.config.json to get quality standards (line limits, etc.)
Discover CLAUDE.md files using Glob (root + package-level)
Run validation checks (structure, formatting, markdown quality)
Analyze content quality (efficiency, organization, token usage)
Check design doc pointers (existence, validity, coverage)
Verify line limits (root: 500, child: 300 from config)
Calculate health scores (file, package, overall)
Identify issues by severity (critical, high, medium, low)
Generate recommendations prioritized by impact
Output audit report with actionable improvements

Instructions

IMPORTANT: Follow the detailed step-by-step instructions in instructions.md to perform the audit correctly.

For usage examples and common scenarios, see examples.md.

Output Format

The audit generates a structured report with:

Summary Section

Total files audited
Overall health score (0-100)
Critical/high/medium/low issue counts
Pass/fail status

File-Level Details

For each CLAUDE.md file:

File path and role (root vs child)
Line count vs limit
Structure validation results
Content quality score
Design doc pointer status
Specific issues found

Recommendations

Prioritized list of improvements:

Critical issues (must fix)
High priority (should fix)
Medium priority (nice to have)
Low priority (optional)

Quality Metrics

Average line count
Design doc pointer coverage
Content efficiency score
Token optimization score

Success Criteria

The audit passes when:

All files under line limits (root: 500, child: 300)
No critical or high severity issues
All design doc pointers valid and exist
Content is lean imperative instructions (not implementation details)
Proper separation between root and child contexts

Related Skills

/context-validate - Basic structure and formatting validation
/context-review - Quality and efficiency review
/context-update - Update context files based on audit findings
/context-split - Split large files that exceed limits
/design-audit - Similar comprehensive audit for design docs

---name: context-auditdescription: Comprehensive quality audit for CLAUDE.md context files. Use when performing thorough quality checks, preparing for releases, ensuring context efficiency, or verifying token optimization.--- # LLM Context Comprehensive Audit Performs deep quality audits of CLAUDE.md context files, checking structure, content quality, efficiency, design doc references, and compliance with standards. ## Overview This skill provides comprehensive quality auditing for LLM context files by running all validation checks, analyzing content efficiency, verifying design doc pointers, checking line limits, and generating detailed audit reports with prioritized recommendations. ## Quick Start **Audit all context files:** ```bash /context-audit ``` **Audit specific file:** ```bash /context-audit CLAUDE.md ``` **Audit package context:** ```bash /context-audit pkgs/effect-type-registry/CLAUDE.md ``` **Quick audit (non-strict):** ```bash /context-audit --strict=false ``` ## Parameters ### Optional - `target`: Path to CLAUDE.md file or "all" (default: all) - `strict`: Enable strict mode with additional checks (default: true) - `check-refs`: Validate design doc references exist (default: true) - `output`: Output file path for audit report ## Workflow High-level audit process: 1. **Parse parameters** to determine audit scope and strictness 2. **Load design.config.json** to get quality standards (line limits, etc.) 3. **Discover CLAUDE.md files** using Glob (root + package-level) 4. **Run validation checks** (structure, formatting, markdown quality) 5. **Analyze content quality** (efficiency, organization, token usage) 6. **Check design doc pointers** (existence, validity, coverage) 7. **Verify line limits** (root: 500, child: 300 from config) 8. **Calculate health scores** (file, package, overall) 9. **Identify issues** by severity (critical, high, medium, low) 10. **Generate recommendations** prioritized by impact 11. **Output audit report** with actionable improvements ## Instructions **IMPORTANT:** Follow the detailed step-by-step instructions in `instructions.md` to perform the audit correctly. For usage examples and common scenarios, see `examples.md`. ## Output Format The audit generates a structured report with: ### Summary Section - Total files audited - Overall health score (0-100) - Critical/high/medium/low issue counts - Pass/fail status ### File-Level Details For each CLAUDE.md file: - File path and role (root vs child) - Line count vs limit - Structure validation results - Content quality score - Design doc pointer status - Specific issues found ### Recommendations Prioritized list of improvements: 1. Critical issues (must fix) 2. High priority (should fix) 3. Medium priority (nice to have) 4. Low priority (optional) ### Quality Metrics - Average line count - Design doc pointer coverage - Content efficiency score - Token optimization score ## Success Criteria The audit passes when: - All files under line limits (root: 500, child: 300) - No critical or high severity issues - All design doc pointers valid and exist - Content is lean imperative instructions (not implementation details) - Proper separation between root and child contexts ## Related Skills - `/context-validate` - Basic structure and formatting validation - `/context-review` - Quality and efficiency review - `/context-update` - Update context files based on audit findings - `/context-split` - Split large files that exceed limits - `/design-audit` - Similar comprehensive audit for design docs

Frequently asked questions