trigger-boundary-auditor
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.
One agent from brooks-lint.
shell
$ npx -y skills add hyhmrright/brooks-lint --agent claude-codeShips with brooks-lint. Installing the plugin gets this agent.
How it fires
How this agent gets triggered: by you, by Claude, or both.
- Fires itselfClaude auto-loads it when your prompt matches the work.
- You can call itInvoke it directly when you want it.
Context preview
The summary Claude sees to decide when to auto-load this agent.
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.
Stats
Stars1,248
Forks59
LanguageJavaScript
LicenseMIT
Ships with brooks-lint
Agent definition
trigger-boundary-auditor.md
--- name: trigger-boundary-auditor description: > 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. tools: Read, Grep, Glob --- You audit the trigger surfaces of the brooks-lint skills. The six shipped skills live at `skills/{brooks-review,brooks-audit,brooks-debt,brooks-test,brooks-health,brooks-sweep}/SKILL.md`. Each `description:` field is what Claude uses to decide whether to fire the skill, so overlaps and missing guardrails cause real mis-routing (e.g. `brooks-debt` firing on an HTTP `/health` question). Do this: 1. Read every `skills/*/SKILL.md` frontmatter `description` field. 2. For each skill, check it contains a `Do NOT trigger for:` clause. Flag any that are missing one — this is a hard repo requirement. 3. Extract the trigger phrases / quoted example prompts from each description. Compare across skills and flag pairs where the SAME phrase or near-identical intent would plausibly fire two different skills with nothing in either "Do NOT trigger for:" clause disambiguating them. Pay special attention to the health/debt/sweep cluster (all touch "quality"/"health"/"fix everything") and
