Install
$ agentstack add skill-waitdeadai-minmaxing-investigate ✓ scanned · ✓ verified, works with Claude Code, Cursor, and more.
Security review
✓ PassedNo issues found. Passed automated security review. · v0.1.0 How review works →
- ✓ Prompt-injection patterns
- ✓ Secret / credential exfiltration
- ✓ Dangerous shell & filesystem operations
- ✓ Untrusted network calls
- ✓ Known-malicious package signatures
What it can access
- ✓ Network access No
- ✓ Filesystem access No
- ✓ Shell / process execution No
- ✓ Environment & secrets No
- ✓ Dynamic code execution No
From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.
Verified badge
Passed review? Show it. Paste this badge into your README, it links to the public security report.
Reliability & compatibility
Declared compatibility
Compatibility is declared by the source manifest. End-to-end runtime verification is coming, see below.
We're building live execution health for every listing: tool-call success rate, median latency, uptime, and last-checked timestamps, measured, not self-reported. It isn't live yet, so we don't show numbers we can't stand behind.
How agent discovery & health will work →About
/investigate
Systematic root-cause debugging with hypothesis testing. 3-fix limit prevents rabbit holes. Root cause or escalate.
MAXPARALLELAGENTS — ceiling for parallel hypothesis work. Parallelize evidence gathering or independent hypotheses only when they are truly independent.
Use when: User says "investigate this", "debug this", "what's causing this", "root cause", "why is this broken", "swarm investigate".
Swarm: "swarm investigate" → /investigate with an efficacy-first debugging wave up to MAX_PARALLEL_AGENTS.
Hypothesis first, then fix. Never guess.
Purpose
Find root cause of bugs/issues systematically. Hypothesis testing prevents guessing. 3-fix limit prevents endless debugging. Parallelize evidence, not random fix attempts.
Execution Protocol
Step 0: Memory Recall (Before Starting)
Recall similar past issues before investigating:
# Recall similar error-solution pairs
bash scripts/memory.sh recall "[issue keywords]" --depth simple 2>/dev/null || echo "Memory recall: skipped"
# Check for known errors
bash scripts/memory.sh search "[error message]" 2>/dev/null || true
Step 1: Gather Evidence
## Investigation: [Issue Description]
### Initial Observation
[What was seen/reported]
### Environment
- Where: [prod/staging/local]
- When: [timestamp]
- Who: [user/automated]
- Frequency: [once/always/sometimes]
### Data Collected
- Logs: [relevant log entries]
- Error messages: [exact errors]
- Reproduction steps: [how to reproduce]
- Impact: [who/what affected]
Step 2: Generate Hypotheses
List 3-5 possible causes, ranked by likelihood:
## Hypotheses
| # | Hypothesis | Likelihood | Can Test? |
|---|-----------|------------|-----------|
| 1 | [Cause A] | High/Med/Low | Yes/No |
| 2 | [Cause B] | High/Med/Low | Yes/No |
| 3 | [Cause C] | High/Med/Low | Yes/No |
Step 3: Test Hypotheses
For each testable hypothesis:
## Testing Hypothesis 1: [Cause A]
### Test Plan
[How to test this hypothesis]
### Execution
```bash
[commands to run]
Result
- SUPPORTED — Evidence points to this
- RULED OUT — Evidence contradicts this
- INCONCLUSIVE — Need more data
### Step 4: Fix (Max 3 Fixes)
After identifying root cause:
```markdown
## Fix Attempt 1/3
### Root Cause
[What caused the issue]
### Fix
- File: [path]
- Change: [what to change]
- Why: [how this fixes the root cause]
### Verification
```bash
[command to verify fix]
Result: PASS/FAIL
**If Fix Fails:**
- Document what was tried
- Move to Hypothesis 2
- Try Fix 2/3
**If Fix Succeeds:**
- Document the fix
- Verify no regression
- Stop (don't over-engineer)
- Log error-solution pair:
```bash
bash scripts/memory.sh add error-solution "\"[exact error message]\"" "\"Root cause: [cause], Fix: [change made]\""
python3 -c "
from memory.causal import record_outcome
factors = ['hypothesis_testing', 'root_cause_found', 'fix_verified']
record_outcome(factors, 'success')
" 2>/dev/null || echo "record_outcome: skipped"
Step 5: 3-Fix Limit Protocol
After 3 fixes without resolution:
## ESCALATE
### What Was Tried
1. Fix 1: [description] — FAILED
2. Fix 2: [description] — FAILED
3. Fix 3: [description] — FAILED
### What We Know
- [facts established]
- [patterns observed]
### What We Don't Know
- [unanswered questions]
### Recommended Escalation
- Who/where to escalate to
- What information to provide
- What to ask for
Log escalation to memory:
python3 -c "
from memory.causal import record_outcome
factors = ['3_fix_limit', 'escalated', 'root_cause_unresolved']
record_outcome(factors, 'failure')
" 2>/dev/null || echo "record_outcome: skipped"
Step 6: Final Output
## Investigation Results: [Issue]
### Root Cause
[Identified cause]
### Fix Applied
- File: [path]
- Change: [change made]
- Verified: [how]
### Regression Check
- [x] Issue resolved
- [x] No new issues
- [x] Related functionality works
### If Escalated
- Escalation reason: Exceeded 3-fix limit
- Escalation target: [who]
- Information provided: [summary]
Quality Gates
- Must gather evidence before hypothesizing → BLOCK
- Must test hypotheses systematically → BLOCK
- Maximum 3 fix attempts → ESCALATE after 3
- Must verify fix before closing → BLOCK
- Must escalate after 3 failed fixes → BLOCK
- Cannot skip escalation after 3 attempts → BLOCK
Anti-Patterns
- Guessing without evidence → BLOCK
- Fixing without identifying root cause → BLOCK
- More than 3 fix attempts → ESCALATE
- Assuming cause without testing → BLOCK
- Not documenting what was tried → BLOCK
- Over-engineering after first fix → WARN
Source & license
This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.
- Author: waitdeadai
- Source: waitdeadai/minmaxing
- License: Apache-2.0
Install and usage instructions live in the source repository linked above.
Reviews
No reviews yet, be the first.
Write a review
Versions
- v0.1.0 Imported from the upstream source.