| name | instructions-detox |
| description | Audit Copilot instruction files for bloat, overlap, stale rules, and weak applyTo scope. Use when reviewing or refactoring .instructions.md, AGENTS.md, copilot-instructions.md, or SKILL.md files, and produce a prioritized markdown report with findings, line references, and recommended deletions or rewrites. Use when this capability is needed. |
| metadata | {"author":"CambridgeMonorail"} |
Instructions Detox Skill
Purpose
Use this skill to review instruction files as behavioral guard rails rather than passive documentation. The goal is to remove context waste, detect drift, and keep instruction loading predictable.
When to Use
Use this skill when:
- instruction files have accumulated over time without cleanup
- Copilot suggestions feel inconsistent, noisy, or off-pattern
- you are adding new instruction files and want to avoid overlap
- you are reviewing
applyTo scope quality
- you need a maintenance audit before merging instruction changes
Do Not Use When
Do not use this skill when:
- debugging application runtime issues
- implementing product features
- fixing lint, test, or build failures unrelated to instruction quality
Core Principle
Context is scarce. Every instruction must earn its place.
If an instruction does not measurably change agent behavior, tighten it or delete it.
Review Procedure
- Inventory the instruction surface and identify canonical versus generated files.
- Check whether each file has a narrow purpose and a clear trigger or scope.
- Remove or flag duplicated guidance, philosophical prose, and stale rules.
- Audit
applyTo patterns for over-broad matching and gaps.
- Compare the instructions with the current codebase and workflow reality.
- Produce a prioritized remediation report with the highest-risk problems first.
Success Metrics
A healthy instruction ecosystem has:
- small, focused files with one job each
- clear and narrow
applyTo scopes
- constraints that prevent bad behavior
- minimal duplication across files
- wording that matches actual repository workflows
Output Contract
Produce a markdown report containing:
- severity-ordered findings
- exact file references and line references
- quoted examples of bloated, stale, or duplicated guidance
- recommended rewrites, deletions, or scope changes
- a short action plan for remediation
Constraints
- Prefer deletion or consolidation over adding more instruction text.
- Do not rewrite generated mirrors before updating the canonical source.
- Do not propose vague style advice without evidence from the files.
Workflows
- Full Detox Review - Complete 8-step audit process
- Quick Bloat Check - Fast bloat scan (< 15 min)
- Rot Detection - Verify instructions match reality
- Scope Audit - Review applyTo patterns
- Maintenance Review - Quarterly check-in
Agent
Use the Instructions Detox agent (@instructions-detox) to run these workflows.
Source: CambridgeMonorail/WallRun — distributed by TomeVault.
