Stats
Actions
Tags
From blindspots
Use when an agent wants the blindspots that apply to its current task, the diff it is reviewing, the plan it is drafting, or any other working context. Pass keywords describing that context. Do not use when the caller wants to browse or text-search the store (use list or search).
How this skill is triggered — by the user, by Claude, or both
Slash command
/blindspots:relevantThis skill is limited to the following tools:
The summary Claude sees in its skill listing — used to decide when to auto-load this skill
1. Pick keywords from the current context. Use the words that describe what the work is about: tags the caller would naturally apply, plus categories from the closed set (code, planning, review, debugging, communication). Lowercase, single tokens.
node ${CLAUDE_SKILL_DIR}/scripts/relevant-blindspots.js --keyword <k1> --keyword <k2> .... Repeat the flag once per keyword.user_intervention_required: true, surface the blindspot's name and Behavior to the user and get explicit direction before proceeding with any action that would trigger it. Do not silently apply the mitigation.user_intervention_required: false, apply the mitigation silently.npx claudepluginhub brennacodes/utilitry --plugin blindspotsProvides UI/UX resources: 50+ styles, color palettes, font pairings, guidelines, charts for web/mobile across React, Next.js, Vue, Svelte, Tailwind, React Native, Flutter. Aids planning, building, reviewing interfaces.
Fetches up-to-date documentation from Context7 for libraries and frameworks like React, Next.js, Prisma. Use for setup questions, API references, and code examples.