Individual skill
drill-five-whys
Iteratively ask why, evidence-checking each causal step, to move from symptom toward root cause.
skills/drill-five-whys/SKILL.md
Source commit 41f752b8444ed9030dd9dc223c302ce874e51f83
What was checked
- Matches the observed repository HEAD
- Yes
- Scanner rules are current
- No
- Repository scan complete
- No
- Skill scan complete
- Yes
- Observed behavior
- Not checked yet
- Last checked
- Nov 5, 2026
These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.
Install this skill
Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.
An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.
Repository context
- Repository stars (not skill ratings)
- 510
- Repository last updated
- Oct 23, 2026
- License
- Apache-2.0
Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.
- academic-research Repository topic
- deep-research Repository topic
- literature-review Repository topic
- mcp Repository topic
- skill Repository topic
- ai-scientist Repository topic
- auto-research Repository topic
- claude-code Repository topic
- research-agent Repository topic
- scientific-discovery Repository topic
- engineering Derived category
Files and excerpt
File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.
Browse files
SKILL.mdcore · 1,179 bytes
Read excerpt
# drill-five-whys
## Purpose
Iteratively ask why, checking evidence at each causal step, to move from symptom toward root cause.
## Input contract
```yaml
required: [symptom_statement, causal_evidence]
optional: [initial_cause, max_depth]
constraints: [each why answer must explain the preceding statement and cite evidence or uncertainty]
```
## Procedure
1. Normalize the symptom as an observable effect.
2. Ask why the effect occurs and record the proposed cause.
3. Test the cause against evidence before asking the next why.
4. Stop at a controllable root, an evidence boundary, or a documented unresolved branch.