Claude Skills by yeaight7

Use when reviewing SQL that affects reporting, metrics, transformations, financial logic, product logic, or stakeholder-facing outputs -- especially when a query still runs fine but its business meaning may have drifted.

Use when deciding whether to compact agent context -- the window is filling up, you are about to switch from one phase to another (research, planning, implementation, debugging), a failed approach left dead-end reasoning, or a previous mid-task compaction lost critical state.

Use when designing or using MCP-backed structured code search with search, AST query, symbol inventory, and bounded extraction workflows.

Use when a task is too large or too mixed for one agent -- it splits into research, planning, implementation, review, and verification stages, needs different specialties, or has parallelizable branches that still share dependencies.

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

Use at the start of a new task -- before writing or editing code -- when the request is vague, the scope boundaries are unclear, or the acceptance criteria for "done" have not been stated.

Use when implementing any feature or bugfix, before writing implementation code

Use when code needs restructuring and observable behavior must stay unchanged, with existing tests kept green at every step.

Use when an ML training run fails or misbehaves -- NaN losses, out-of-memory errors, shape mismatches, or a model that cannot fit even a single batch.

Use when a request needs parallel external perspectives — combined backend and UI work, code review from multiple angles, or cross-validation where different models may disagree.

Use when starting work in a repository with Agent Powerups installed, when a task may match a reusable local skill, command, workflow, hook recipe, AGENTS.md template, or MCP feature.

Use when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims; evidence before assertions always

Use when you have a spec or requirements for a multi-step task, before touching code.