Menu
Triage and resolve issues reported by beta users across FlowInCash and Crispi apps
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Diagnose and fix Express.js error handling issues across all apps (FlowInCash, Crispi, MicroApps)
Recover MCP servers when they fail to respond, lose connection, or return protocol errors
Diagnose and recover Plaid banking sync failures in FlowInCash
Debug and fix FlowInCash purchase decision queue and traffic-light evaluation system
Based on SOC occupation classification
| name | user-troubleshoot |
| description | Triage and resolve issues reported by beta users across FlowInCash and Crispi apps |
| version | 1.0.0 |
| tags | ["support","troubleshooting","users","beta"] |
Use this skill when Bob forwards a user-reported issue or monitoring detects user-facing errors.
| Symptom | Likely Cause | First Check |
|---|---|---|
| "Balance is wrong" | Plaid sync stale | Last sync timestamp |
| "App won't load" | API server down | Express logs |
| "ChatGPT tool broken" | MCP server crashed | See mcp-protocol-recovery |
| "Goals disappeared" | goal-tracker restarted | Expected (in-memory) |
| "Can't sign in" | Auth token expired | Auth service logs |
When fixing: state the cause, what you'll change, which project. Run tests, commit.
When escalating to Bob: include what user reported, what you found, 2-3 possible causes ranked by likelihood. Never contact users directly — all communication goes through Bob.
