instructions-detox

Security Community

Repo stars 0
Author repo skills-registry

Interpretation is structured for decision-making; original keeps the upstream SKILL.md unchanged.

Decide Fit First

Core job: Audit Copilot instruction files for bloat, overlap, stale rules, and weak applyTo scope. Use when reviewing or refactoring .inst…
Best fit: Use it when the task has reusable inputs, steps, and validation criteria rather than a one-off answer.
Avoid forcing it: If the source lacks commands, platform support, or external-service evidence, keep those fields unknown instead of guessing.

Design Intent

Structure: The skill is organized around “Purpose”, “When to Use”, “Do Not Use When”, “Core Principle”, showing how the author expects the agent to judge fit, collect context, and produce verifiable output.
Trigger evidence: Prioritize the author’s wording around when to use it, what context to collect, and what output shape to produce.
Evidence boundary: Author text states facts, repository files prove commands and paths, and Fluxly only adds fit, limits, and usage judgment.

How To Use It

Inputs: Provide target material, scope, expected result, forbidden changes, and validation method.
Invocation: Name instructions-detox directly; if the source includes slash commands, start with the command and then add task context.
Validation: Start small and check whether the result follows “Purpose / When to Use / Do Not Use When” before expanding.

Boundaries And Review

Dependencies: It usually needs no extra API key, so start with a small validation task.
Permissions: Declared permissions include read / write; ask the agent to state file, command, and rollback boundaries before acting.
Quality bar: A useful result names the deliverable, evidence, and next action. Generic prose means the task needs tighter context.

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.

Fluxly profile Author and license come from source; runtime, permissions, and network are Fluxly detections or estimates

Fluxly category: Security
Author-declared agents: No explicit declaration found; this is not inferred or tested compatibility
Static check: 88 / 100 · heuristic scan, not runtime safety proof
Author / version / license: @tomevault-io · no license declared
Fluxly token estimate: Lean
Fluxly setup estimate: Plug-and-play
External API key: No requirement detected
Detected OS requirements: Unspecified
Runtime requirements: Unspecified
Detected file/system behavior: Read-only
Write / modify
Detected network behavior: Local-only
Install commands: None (reference only)

Profile is derived at build time from SKILL.md and install vectors. Subject to drift from author intent.

Heads up: 未限定 allowed-tools，默认拥有全部工具权限。

Output preview instructions-detox.preview

The current SKILL.md does not define a fixed output example.

SKILL.md SKILL.md

# 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

1. Inventory the instruction surface and identify canonical versus generated files.
2. Check whether each file has a narrow purpose and a clear trigger or scope.
3. Remove or flag duplicated guidance, philosophical prose, and stale rules.
4. Audit `applyTo` patterns for over-broad matching and gaps.
5. Compare the instructions with the current codebase and workflow reality.
6. 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:

1. severity-ordered findings

…

Evidence boundary and execution chain

Author text anchors workflow facts; Fluxly only indexes current sections, terms, files, and commands.

sections -> Purpose → When to Use → Do Not Use When → Core Principle → Review Procedure → Success Metrics
terms    -> Context is scarce. Every instruction must earn its place. · Instructions Detox · Use this skill to review instruction files as behavioral guard rails rather than passive documentation. · Context is scarce. · If an instruction does not measurably change agent behavior, tighten it or delete it. · 1. Inventory the instruction surface and identify canonical versus generated files. · 1. severity-ordered findings 2. · - Prefer deletion or consolidation over adding more instruction text.
files/cmd -> applyTo · @instructions-detox · references/01-full-detox-review.md · references/02-quick-bloat-check.md · references/03-rot-detection.md · references/04-scope-audit.md · references/05-maintenance-review.md · CambridgeMonorail/WallRun
body sha256 -> 6537c5276f36