context-audit

Analyzes context window usage trends and audits configuration files for token bloat.

6|Updated Mar 27, 2026
One-click install
npx skills add https://github.com/greglas75/zuvo --skill context-audit-greglas75
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: context-audit
Source: https://github.com/greglas75/zuvo/tree/main/skills/context-audit
Command: npx skills add https://github.com/greglas75/zuvo --skill context-audit-greglas75

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? AI coding sessions silently accumulate context bloat from oversized include files, bloated CLAUDE.md rules, excessive MCP servers, and missing permission settings, degrading response quality and wasting tokens without any visibility into the cause. ## Core Features & Use Cases - Trend Analysis: Parses runs.log include data to show loading frequency, heaviest skill runs, tier distribution, and week-over-week deltas. - Full Setup Audit: With /context data, audits MCP servers, memory files against five bloat filters, skill description sizes, settings, and permission deny rules, producing a 0-100 health score. - Baseline Snapshots: Saves current metrics to a JSON baseline so future runs can measure growth or improvement. - Use Case: After weeks of adding rules to CLAUDE.md, run a full audit to discover 300 lines of redundant instructions and two MCP servers with 40+ tools each, then apply the suggested fixes to reclaim context space. ## Quick Start Ask the assistant to run a context audit to analyze include loading trends and score the health of your setup.

Frequently Asked Questions about context-audit

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

FAQPage Schema
How do I check what is filling my Claude Code context window?

Run the context audit in trend mode to parse runs.log include data collected by the track-includes hook. It shows per-include loading frequency, cumulative byte costs, and the heaviest skill runs so you can identify the largest consumers.

How to audit CLAUDE.md for bloated or redundant rules?

Use the full audit mode, which requires /context output, to evaluate every memory file against five filters: default behavior, contradiction, redundancy, bandaid fixes, and vagueness. It flags files exceeding 200 combined lines and deducts score points per issue.

Does the context audit require manual data collection?

No, include sizes are captured automatically by the track-includes.sh PostToolUse hook and stored in runs.log field 12 as name:bytes pairs. Only the optional full audit mode requires you to run /context manually first.

What happens if there is not enough metrics data for a trend analysis?

If fewer than three runs.log entries contain include data, the audit stops and asks you to run a few skills first so the hook can collect measurements. Trend deltas additionally require more than 14 days of data.

Can the audit fix the configuration problems it finds?

Yes, in full mode it offers to apply settings.json and permissions.deny fixes automatically since they are safe and reversible. Changes to CLAUDE.md are shown as diffs first and require your confirmation before modification.