Stackbone debug skill

This skill tells you how to locate the cause of a failure in a Stackbone workspace. It holds no error catalog: the meaning of each code, status and message lives in the docs, and you read it from there once you have the code in hand.

Where the facts live

The docs are served over MCP as the stackbone-docs server (https://docs.stackbone.ai/mcp, public, tools search_docs, get_doc, list_docs). stackbone docs prints the connection details.

• Start the session with list_docs. It returns every page under its area and section. How to find the owner page below says which page a code or a symptom belongs to; take its path from that list and get_doc it. Never type a path from memory: pages move, titles stay.
• Once you hold an error code, read the page that owns it: its error section says what the code means and what to check next.
• Once you hold a message with no code, search_docs with the message verbatim, then with the symptom in plain words.
• Do not explain a code from memory. Codes are stable but their causes and the next command change between releases.

No stackbone-docs tools in your session? Fetch https://docs.stackbone.ai/llms.txt: the same index, one line per page with its title, its description and a link to its raw markdown. Pick the page by title and fetch that link. https://docs.stackbone.ai/llms-full.txt is every page in one file (~700 KB).

How to use this skill