investigate

Installation
SKILL.md

Investigate

For when something feels wrong but the user can't fully articulate it yet, or they have a specific doubt about a code path, approach, claim, or conclusion. The goal is to narrow the hunch, then confirm or refute with evidence. Do not manufacture problems if the hunch is unfounded. Narrow the unease together — not doubting the user's instincts.

Primary-source-first after the target is clear: read the actual code, the actual source document, or the actual data — never secondhand description or memory.

When to Use

  • Specific doubt about a code path, approach, claim, or conclusion
  • Narrow a vague unease into confirm/refute with citable primary-source evidence
  • Parallel web research on independent topics (via multi)

Not for: written plan review (second-opinion), fuzzy ideation (crystallize). For reproducible bugs, pair with testing (+ debug when layer/logs unclear) — see agent-routing.md § Quality & ops. Ambient extract → agent-routing.md § Specific doubt.

Stance and routing

Installs
4
First Seen
3 days ago
investigate — csark0812/toolbox