# Error Investigation

> Investigate an error message deeply — reproduce a search across official docs, GitHub, and community reports, then synthesize a diagnosis. Use when the user hits an error and "try Google" isn't enough.

- Skill: `samraddhashrivastavatech/error-investigation` (Agent Skill)
- Install (CLI): `npx skillmds@latest add samraddhashrivastavatech/error-investigation`
- Raw SKILL.md: https://api.skillmd.com/api/skills/samraddhashrivastavatech/error-investigation/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Research & Search
- Author: SAMRADDHASHRIVASTAVATECH (https://skillmd.com/u/samraddhashrivastavatech)
- Updated: 2026-09-22
- Page: https://skillmd.com/skills/samraddhashrivastavatech/error-investigation

---


# Error investigation

Turn an error message into a diagnosis: hunt documentation, issue trackers, and
community reports in parallel, then synthesize.

## When to use

- A cryptic error with no obvious fix.
- An error that exists across versions/environments.
- The user wants a probable cause plus verification steps, not a guess.

## Tools used

- `investigate_error` — `error` (the exact message) with optional `tech`
  context.

## Workflow

1. Quote the exact error string + known tech stack (`tech`).
2. `investigate_error` — it routes across web/docs/GitHub/community coverage.
3. Cross-check candidate causes against reproducibility (same version? minimal
   repro?)
4. Deliver: likely cause, the fix path, and how to verify it — separating
   confirmed from reported.

## Input schema

```json
{ "error": "str", "tech": "str" }
```

## Output schema

```json
{ "error": "str", "likely_cause": "str", "evidence": "list[{source,url}]", "fixes": "list[str]" }
```

## Security

Never paste logs/error strings containing secrets into search. Report fixes
with sources; do not apply community-pasted commands to the user's machine
without review.

## Related skills

`github-research`, `community-research`, `web-search`, `source-analysis`