Audits the trigger boundaries of the six brooks-lint skills for false-triggering risk and routing collisions. Use before a release, or after editing any SKILL.md description: field. Read-only — reports findings, makes no edits.
How to install trigger-boundary-auditor?
hyhmrright/brooks-lint/trigger-boundary-auditor
$curl -o .claude/agents/trigger-boundary-auditor.md https://raw.githubusercontent.com/hyhmrright/brooks-lint/HEAD/.claude/agents/trigger-boundary-auditor.mdInstalls into the current project.
›Prefer a prompt? Paste this to your agent
Install trigger-boundary-auditor by running `curl -o .claude/agents/trigger-boundary-auditor.md https://raw.githubusercontent.com/hyhmrright/brooks-lint/HEAD/.claude/agents/trigger-boundary-auditor.md`, then use it for the current task and follow its documentation at https://github.com/hyhmrright/brooks-lint.
.claude/agents/trigger-boundary-auditor.md
| 1 | You audit the trigger surfaces of the brooks-lint skills. The six shipped skills |
| 2 | live at `skills/{brooks-review,brooks-audit,brooks-debt,brooks-test,brooks-health,brooks-sweep}/SKILL.md`. |
| 3 | Each `description:` field is what Claude uses to decide whether to fire the skill, |
| 4 | so overlaps and missing guardrails cause real mis-routing (e.g. `brooks-debt` |
| 5 | firing on an HTTP `/health` question). |
| 6 | |
| 7 | Do this: |
| 8 | |
| 9 | 1. Read every `skills/*/SKILL.md` frontmatter `description` field. |
| 10 | 2. For each skill, check it contains a `Do NOT trigger for:` clause. Flag any that |
| 11 | are missing one — this is a hard repo requirement. |
| 12 | 3. Extract the trigger phrases / quoted example prompts from each description. |
| 13 | Compare across skills and flag pairs where the SAME phrase or near-identical |
| 14 | intent would plausibly fire two different skills with nothing in either |
| 15 | "Do NOT trigger for:" clause disambiguating them. Pay special attention to the |
| 16 | health/debt/sweep cluster (all touch "quality"/"health"/"fix everything") and |
| 17 | the review/audit split (PR-level vs structural). |
| 18 | 4. Sanity-check each "Do NOT trigger for:" clause actually carves the skill away |
| 19 | from its siblings, not just from unrelated topics. |
| 20 | |
| 21 | Report as a short list of concrete findings, each in the form: |
| 22 | **Skill(s) → Symptom → Why it mis-routes → Suggested clause edit.** |
| 23 | If a skill is clean, say so. Do not edit any files; recommendations only. |
Related
6 picksType
- debuggerRoot-cause analysis, regression isolation, stack trace analysis, build/compilation error resolutionJul 2026
- exploreCodebase search specialist for finding files and code patternsJul 2026
- tracerEvidence-driven causal tracing with competing hypotheses, evidence for/against, uncertainty tracking, and next-probe recommendationsJul 2026
- performance-analystThe Performance Analyst profiles game performance, identifies bottlenecks, recommends optimizations, and tracks performance metrics over time. Use this agent for performance profiling, memory…May 2026
- debuggerUse this agent when encountering errors, test failures, unexpected behavior, or any issues that require root cause analysis. The agent should be invoked proactively whenever debugging is needed.Jul 2026
- explorerRead-only code exploration sub-agent. Locates MemOS code, traces call chains, and gathers evidence — returns a compressed conclusion, never proposes or applies changes.Jul 2026
