plugins/consider/skills/hanlons-razor/SKILL.md
Interpret behavior charitably — attribute to mistakes before malice; use when behavior seems hostile or frustrating and an adversarial interpretation is forming
npx skillsauth add bcbeidel/wos hanlons-razorInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
<output_format>
[The behavior or event that seems problematic]
[The "malice" or "incompetence" reading]
[What would you need to know to determine which interpretation is correct?]
[The interpretation best supported by available evidence]
[How to respond given the most likely explanation] </output_format>
<example> ## Hanlon's Razor: PR Sitting Unreviewed for a WeekYou submitted a PR 7 days ago, pinged the assigned reviewer twice, and got no response. The reviewer has been merging other PRs during this time.
The reviewer is deliberately ignoring your PR because they disagree with your approach and want to passively block it rather than give direct feedback.
Check whether the PRs they've been reviewing are smaller or release-critical. Ask directly: "Is this a good time, or should I find another reviewer?" Their response will distinguish between "busy" and "avoiding."
PR size + competing priorities. A 400-line PR requires 30-60 minutes of focused review. During a release crunch, that time block doesn't exist. The other merged PRs were likely small and fast.
Break the PR into 2-3 smaller PRs if possible. Message the reviewer offering to walk through the changes in 15 minutes to reduce their review burden. If still no response after the offer, reassign to a different reviewer without resentment. </example>
Chainable to: consider (to apply additional models), map-vs-territory (to check what assumptions are driving the uncharitable interpretation)
tools
Use when the user wants to "audit a help skill", "review my plugin index", or "verify my help-skill is up to date". Audits a plugins/<plugin>/skills/help/SKILL.md against the help-skill rubric — coverage, freshness, frontmatter fidelity, plus five judgment dimensions and a trigger-collision check.
tools
Use when the user wants to "scaffold a help skill", "add a /<plugin>:help command", or "build a plugin index skill", or wants to give a plugin an orientation surface that lists its skills and common workflows. Produces a SKILL.md at plugins/<plugin>/skills/help/SKILL.md.
tools
Audits pair-level integrity of a primitive-pair (the artifact `/build:build-skill-pair` produces) by walking the four required artifact slots — principles doc, `build-<primitive>/SKILL.md`, `check-<primitive>/SKILL.md`, and the `primitive-routing.md` registration — and reports cross-artifact issues a per-SKILL.md checker cannot see: missing principles doc, divergent principles paths between halves, absent routing registration, missing build→check handoff. Per-half structural compliance with the unified pattern (`check-skill-pattern.md`) is delegated to `plugins/build/_shared/scripts/check_skill_pattern.py`. Use when the user wants to "audit a skill pair", "review a primitive pair", or "validate the skill pair for X". Not for auditing a single SKILL.md — route to `/build:check-skill`. Not for re-distilling a stale principles doc — route to `/build:build-skill-pair`.
testing
Audit a root-level resolver — verify AGENTS.md pointer, managed-region integrity, filing-table coverage against disk, context-table actionability, and trigger-eval pass rate. Use when the user wants to "audit a resolver", "validate routing table", or "find dark capabilities".