agent-context-audit

Solid

Audit a repo's agent context — CLAUDE.md files, codebase docs, skills, and tool/MCP designs — against Anthropic's Claude 5 context-engineering guidance ("unhobbling": Anthropic cut ~80% of Claude Code's system prompt with no eval loss). Finds overconstraint, conflicting instructions, redundancy, stale facts, and missing "unknown knowns"; produces a scored findings report with concrete rewrites, then applies approved fixes. Use when someone says "audit my CLAUDE.md", "context audit", "unhobble this repo", "review our agent docs/skills/tools", or after upgrading to Claude 5-generation models.

AI & Automation 1,064 stars 141 forks Updated today

Install

View on GitHub

Quality Score: 83/100

Stars 20%
100
Recency 20%
100
Frontmatter 20%
70
Documentation 15%
100
Issue Health 10%
80
License 10%
0
Description 5%
100

Skill Content

# agent-context-audit — unhobble this repo's agent context Goal: find where this repo's context (CLAUDE.md, docs, skills, tool designs) **hobbles** a Claude 5-generation model — overconstrains it, contradicts itself, repeats itself, or hides context the model actually needs — and leave behind a findings report plus approved fixes. Background: Anthropic removed over 80% of Claude Code's system prompt for Claude 5 models with **no measurable loss** on coding evals. Older context was written for models that needed rules; newer models need judgment, good interfaces, and the facts they can't infer. This skill audits against that shift, plus the "finding your unknowns" framework (the gap between the *map* — your prompts/docs — and the *territory* — the actual codebase). You are **auditing first, fixing second**. Do not edit anything until Step 4. ## The six shifts (the audit rubric) Every finding maps to one of these. Cite the shift number in the report. 1. **Rules → Judgment.** Hard rules ("NEVER…", "ALWAYS…", "do not add comments", "one-line docstrings max") that encode a *preference*, not a real constraint, should become judgment framing ("write code that reads like the surrounding code") — or be deleted if the model would infer it anyway. Keep hard rules only where violation is genuinely costly (security, prod data, irreversible actions, legal/billing). 2. **Examples → Interface design.** Long tool-usage examples and few-shot transcripts constrain explor...

Details

Author
AI-Builder-Club
Repository
AI-Builder-Club/skills
Created
1 months ago
Last Updated
today
Language
Python
License
None

Integrates with

Similar Skills

Semantically similar based on skill content — not just same category