Instructions 上下文
- 作者仓库星标 0
- 作者仓库 skills-registry
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.
<!-- tomevault:4.0:skill_md:2026-05-23 -->Source: CambridgeMonorail/WallRun — distributed by TomeVault.
- 流狐分类
- 安全
- 作者声明 Agent
- 未找到明确声明；不据此推断已兼容或已测试
- 静态检查
- 88 / 100 · 启发式扫描，不代表运行安全
- 作者 / 版本 / 许可
- @tomevault-io · 未声明 license
- 流狐 Token 估算
- 低消耗
- 流狐接入估算
- 即装即用
- 是否需要外部 API Key
- 未发现要求
- 检测到的系统要求
- 未声明
- 底层运行要求
- 未声明
- 检测到的文件与系统行为
-
- 只读
- 允许写入 / 修改
- 检测到的网络行为
- 仅限本地
- 安装命令数
- 无（仅作为资料）
档案由构建时根据 SKILL.md 与安装命令自动衍生，可能与作者实际意图存在差异。
需要注意： 未限定 allowed-tools，默认拥有全部工具权限。
作者没有在当前 SKILL.md 中定义固定输出样例。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.
Use this skill when: instruction files have accumulated over time without cleanup Copilot suggestions feel inconsistent, noisy, or off-pattern
Do not use this skill when: debugging application runtime issues implementing product features
Context is scarce. Every instruction must earn its place. If an instruction does not measurably change agent behavior, tighten it or delete it.
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.
A healthy instruction ecosystem has: small, focused files with one job each clear and narrow applyTo scopes
# 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
…作者原文负责流程事实；流狐只索引当前章节、要点、文件与命令。
章节 -> Purpose → When to Use → Do Not Use When → Core Principle → Review Procedure → Success Metrics
要点 -> 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.
文件/命令 -> 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
内容 SHA-256 -> 6537c5276f36
方法与流程
适用与边界
原文中的明确线索
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