Skip to content
AssureSwarm Docs

Agent Operating Guide

/coach-troubleshoot

Diagnose a specific Canvas error or symptom against the docs: propose a fix with a confidence rating, then resolve it with a sibling skill or route to human support.

Paste an error message or describe a symptom and get a diagnosis. The skill dispatches the coach-troubleshooter helper agent to match your symptom to a known cause in the docs snapshot, then proposes a fix, commands to run, settings to check, with a confidence rating and doc citations. If the fix is something a sibling skill can do, it points you there; if the diagnosis needs a person, it routes to /coach-ticket-open. It’s read-only against Canvas: it never auto-fixes anything.

When to use

Section titled “When to use”

When you hit an error or a symptom and want to know what’s wrong: “plugin validation failed”, “schema mismatch”, “permission denied”, or “suggest_change returned a validation error”. For a conceptual question with no error attached, use /coach-ask; for the steps to do a task, use /coach-howto.

Inputs

Section titled “Inputs”
Flag Required Notes
--include-config No Attach your config and schema snapshots to the diagnosis for context. Still makes no support MCP calls.

Example

Section titled “Example”

/coach-troubleshoot suggest_change returned a validation error diagnoses a likely field- type or options mismatch, cites the doc section it matched, and offers to either re-check your schema with a sibling skill or open a bug ticket pre-filled with the diagnosis and what you tried.

Good to know

Section titled “Good to know”
  • The skill never mutates Canvas. Either you run the sibling skill it suggests, or it escalates: it does not apply the fix for you.
  • --include-config folds your config and schema snapshots into the diagnosis for better matching, but it still makes no support-side MCP calls.
  • When confidence is low or the diagnosis doesn’t match what you saw, it opens a /coach-ticket-open bug pre-filled with the attempt, so a human starts from context rather than scratch.
Section titled “Related”