catalyst-debug
Installation
SKILL.md
Diagnose a Catalyst failure
Goal: end this skill with a named cause and the line of evidence that proves it, or an explicit statement of what you could not see and why. "Try restarting it" is not a diagnosis, and neither is a plausible story with no read behind it.
Everything here goes through the Catalyst MCP server, the catalyst_* tools. If they are
missing or refuse with NOT_AUTHENTICATED, that is a connection problem, not the failure
you were sent to debug: the catalyst-setup skill covers it.
1. Route by symptom
| Symptom | Start with | Then |
|---|---|---|
| A workflow run failed, or hangs | catalyst_get_workflow_run |
section 3 |
| An app never became ready | catalyst_get_app |
section 4 |
| An agent does not answer | catalyst_get_agent |
section 5 |
| A component will not connect | catalyst_get_component |
section 6 |
| Nothing named — "is anything broken?" | catalyst_list_projects, then the project |
below |