Troubleshoot
Diagnose and fix a failing or misbehaving Atomic Agents app, import errors, schema...
Install
npx skills add Eigenwise/atomic-agents --skill troubleshoot -g -a claude-code -y- Repository
- Eigenwise/atomic-agents6.3k
- Category
- AI and agents
- Updated
- 6d ago
- License
- MIT
- Context cost
- Lightabout 1,405 tokens
- Runs scripts
- No, instructions only
What it does
Diagnose and fix a failing or misbehaving Atomic Agents app, import errors, schema validation failures, empty or malformed LLM output, provider role/mode errors, history and context problems, MCP transport errors. Use when the user reports an error, traceback, or wrong behavior in atomic-agents code, asks "why is my agent not working / crashing / returning garbage", or pastes a `ValidationError`, `ImportError`, or provider API error from an atomic-agents project.
Troubleshoot an Atomic Agents App
Diagnostic workflow for the "it's broken" moment. Most atomic-agents failures are one of a dozen known causes with mechanical fixes. Match the symptom, apply the fix, verify by re-running.
Workflow
- Capture the failure. Get the exact traceback or wrong-output sample plus the code that produces it (agent construction, schemas, client wiring). If the user pasted only a fragment of the error, ask for the full traceback before guessing.
- Match against the symptom table below. The quoted strings are the framework's real messages, match on them.
- Apply the fix and re-run the failing snippet. Do not declare the problem solved without a passing re-run.
- No match? Load the reference for the failing area (table at the bottom) and reason from there. For a whole-codebase audit rather than one failure, delegate to the
atomic-reviewersubagent instead.
