WorkBuddy Intelligent Diagnostic Assistant

Problem It Solves

When WorkBuddy throws errors, freezes, loses connectivity, or fails to run tasks, engineers often have to inspect proxy, connectors, logs, network, and client state manually. This skill turns that troubleshooting path into a concrete diagnostic workflow: identify the most likely failing layer first, then provide one repair action instead of a long list of guesses.

How It Works

• One-click diagnostics: run scripts/smart_diagnose.py to scan 127.0.0.1:51103, connectors, logs, network, and client detection results.
• Pattern matching: compare findings against PATTERN_DB and output the most likely root cause by priority: PS0 > PS1 > PS2.
• Symptom input: when logs are unclear, pass --symptom "white screen" to cover colloquial failure descriptions.
• Machine-readable output: --json can write structured results to a temp file or custom path for automation.
• Feedback handoff: when no known pattern matches, generate an official feedback draft and suggest loading workbuddy-guide for deeper investigation.

Boundaries and Notes

This skill is read-only: it inspects local ~/.workbuddy configuration and logs but does not modify settings, delete files, or restart services. It diagnoses the current local environment only and is intended to restore basic usability, not to replace root-cause analysis. If the WorkBuddy proxy is not running, no response on 127.0.0.1:51103 is expected and reported as a proxy issue. Review the generated feedback draft before submitting it to avoid misleading official support.