Analyzed Aug 11, 2026
juliusbrussee/caveman
investigate-first
Diagnose ambiguous failures before editing. Use for unknown causes, intermittent behavior, performance regressions, or investigations needing evidence-ranked hypotheses.
Installation
npx skills add juliusbrussee/caveman --skill investigate-first
Similar popular skills
Related neighbors and high-traction skills in the same topics — useful to compare before installing.
Analyzes observability data — logs, traces, errors, sessions, and metrics — to find root cause …
7 installs>- Investigator OPSEC — threat-model who might notice you, control your attribution surface acr…
58.2K installsGuide and conduct user research — from planning through synthesis. Interview scripts, survey de…
25 installsInvestigate a Grafana Cloud k6 test — describe the script, list run history, identify pass/fail…
42 installs>- Start-here router and tradecraft baseline for any investigation into a person, company, doma…
1.7K installsExpert guidance for deep security incident and entity investigations in Google SecOps. Use when…
60 installsSecurity audits
Partner security reviews for this skill.
Analyzed Aug 11, 2026
Analyzed Aug 11, 2026
0 alerts
Also in this package
Other skills from juliusbrussee/caveman · top by installs.
npx skills add juliusbrussee/caveman
More details
Agent compatibility
Declared targets from SKILL.md / docs. Unmarked agents are not listed — the skill may still install via the CLI.
Repository health
main
Package contents
Files included with this skill beyond the listing page.
-
skill md
SKILL.md688 B -
docs
SUMMARY.md194 B
History
- First seen on skills.sh
- First recorded snapshot · 39,900 installs
SKILL.md
Investigate first
Gather evidence before changing product code.
- Separate observed symptom from inferred cause.
- Trace inputs, state transitions, ownership boundaries, and failure output.
- Rank hypotheses by evidence and cheap falsification value.
- Do not edit until one credible mechanism explains evidence.
- Stop exploration when evidence is sufficient to name cause or exact blocker.
Report cause and proof. Make no fix unless task authorizes implementation.