instructions-detox
- Repo stars 0
- Author updated Live
- Author repo skills-registry
- Domain
- Security
- Compatible agents
-
- Claude Code
- Cursor
- Cline
- Codex
- Windsurf
- Gemini CLI
- +20
- Trust score
- 88 / 100 · community maintained
- Author / version / license
- @tomevault-io · no license declared
- Token usage
- Lean
- Setup complexity
- Plug-and-play
- External API key
- Not required
- Operating systems
- Unspecified (assume cross-platform)
- Runtime requirements
- No special requirements
- Permissions
-
- Read-only
- Write / modify
- Network behavior
- Local-only
- Install commands
- 26 variants
Profile is derived at build time from SKILL.md and install vectors. Subject to drift from author intent.
Heads up: 未限定 allowed-tools，默认拥有全部工具权限。
---
name: instructions-detox
description: Audit Copilot instruction files for bloat, overlap, stale rules, and weak applyTo scope. Use whe…
category: security
runtime: no special runtime
---
# instructions-detox output preview
## PART A: Task fit
- Use case: 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..
- Inputs: target material, constraints, expected output, and acceptance criteria.
- Evidence boundary: follow “Purpose / When to Use / Do Not Use When” and do not present inference as author intent.
## PART B: Execution result
- **01** The card summarizes the use case; runtime output centers on “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.”.
- **02** When the source has headings, the agent prioritizes “Purpose / When to Use / Do Not Use When” so the result follows the author’s structure.
- **03** Typical output includes task judgment, concrete steps, required commands or file edits, validation, and follow-up options.
- **04** Risk context follows the fingerprint: read files, write/modify files; mostly runs locally; usually needs no extra API key.
## Running Rules
- read files, write/modify files; mostly runs locally; usually needs no extra API key.
- Validate with a small sample before expanding scope.
- Return the result, validation criteria, and next iteration options. Choose the trigger
The source does not require a stable slash command. After installation, invoke the skill by name and describe the task.
Provide inputs and boundaries
Name target files or source material, expected output, forbidden changes, and whether network or shell access is allowed. Permission fingerprint: read files, write/modify files.
Validate with a small run
Start with a small task and check whether the result follows “Purpose / When to Use / Do Not Use When”. Inspect diffs, logs, previews, or tests before expanding scope.
Review before delivery
Confirm the final output includes a concrete result, evidence, and next action. If it stays generic, tighten inputs, boundaries, and acceptance criteria.
---
name: instructions-detox
description: Audit Copilot instruction files for bloat, overlap, stale rules, and weak applyTo scope. Use whe…
category: security
source: tomevault-io/skills-registry
---
# instructions-detox
## When to use
- Audit Copilot instruction files for bloat, overlap, stale rules, and weak applyTo scope. Use when reviewing or refacto…
- Use it when the task has clear inputs, repeatable steps, and validation criteria.
## What to provide
- Target material, scope, expected result, and forbidden changes.
- Whether network, commands, file writes, or external services are allowed.
## Execution rules
- Organize steps around “Purpose / When to Use / Do Not Use When” and keep inference separate from source facts.
- read files, write/modify files; mostly runs locally; usually needs no extra API key.
- Validate with a small sample before expanding the task.
## Output requirements
- Return the deliverable, key evidence, validation method, and next action.
- Mark missing information as unknown; do not invent commands, platforms, or dependencies. Evidence boundary and execution chain
The author source anchors workflow facts; repository files anchor sources and commands; Fluxly only adds fit, limitations, and quality judgment.
skill "instructions-detox" {
input -> user goal + target files + boundaries + acceptance criteria
context -> Purpose / When to Use / Do Not Use When
rules -> SKILL.md triggers / order / output contract
runtime -> no special runtime | read files, write/modify files | mostly runs locally
guardrails -> usually needs no extra API key + small-sample validation + diff/log review
output -> copyable result + checklist + next iteration
}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
applyToscope 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
applyTopatterns 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
applyToscopes - 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.
Decide Fit First
Design Intent
How To Use It
Boundaries And Review