Install any skill in seconds. Free to start, no credit card required.
Get Started Free →majiayu000/repo-agent-context-audit
Audit and recommend improvements for a repository's agent-readable context, including AGENTS.md, CLAUDE.md, WARP.md, CONTRIBUTING.md, .agents/skills, and specs/ PRODUCT.md and TECH.md contracts.
Passed 15 of 18 test cases with the skill, and 9 of 18 without it.
and 6 more in the full report
7 fixed11 passed either way4 still failing0 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 7 test cases the skill fixed. Same model, same prompt, with and without the skill.
We want to execute a initial passive check on our repository at `/src/analytics` to locate all agent context instruction files, reusable procedures, and feature specifications. What command line tool within the context suite should be run first?
| Checked | Without skill | With skill |
|---|---|---|
| Specifies running python3 scripts/scan_repo_context.py /src/analytics | Missed | Passed |
The instructions your model reads when the skill loads.
Assess whether a repository has a small, usable agent context stack: a short top-level instruction file, task-specific skills, and behavior/implementation specs for substantial work. Default to a read-only audit and minimal recommendations; create or edit high-context files only when the user explicitly asks.
If the user asks to generate, split, or apply root/scoped AGENTS.md files,
handoff to agentsmd-scaffold. This skill may identify that scaffold as the
smallest useful change, but should not duplicate the generation workflow.
Prefer this three-layer shape:
AGENTS.md or repo-equivalent: 80-150 lines, top-level routing only..agents/skills/<task>/SKILL.md: reusable workflows for common fragile tasks.specs/<id>/PRODUCT.md and specs/<id>/TECH.md: checked-in contracts for substantial features.Do not force this exact layout when a repo already has a coherent equivalent, such as WARP.md, CLAUDE.md, CONTRIBUTING.md, or framework-specific instruction files. Map existing files to the layers first, then fill only the real gaps.
Run the read-only scanner when possible:
# From this skill directory:
python3 scripts/scan_repo_context.py <repo-root>
Then inspect the important files directly. Always search before creating:
AGENTS.md, CLAUDE.md, WARP.md, .claude/instructions.mdCONTRIBUTING.md, README.md, .github/copilot-instructions.md.agents/skills/*/SKILL.mdspecs/**/{PRODUCT,product,TECH,tech}.mdIf multiple instruction files overlap, record their scopes and precedence instead of merging them by default.
test cases passed, vs 9 / 18 without
Published skills whose descriptions closely match this one, with their headline benchmark lift.
More skills from the same source and nearby in the registry, with their headline benchmark lift.