Stackbone integrations skill

This skill tells you how to wire a workspace to the outside: what to set up first, which surface can set it up, and what each step commits you to. It holds no connector catalog and no field lists: which providers exist, which events they fire and which errors they answer with live in the docs and on the box.

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 with list_docs. Integrations, Trigger events and Destinations (Home › Features) are the three pages behind this skill. Take their paths from that list and get_doc them. Never type a path from memory: pages move, titles stay.
• The connector catalog is not in the docs, it is on the box. Which connectors are registered here, which accounts are connected and which operations each one exposes is read live from the provider's own OpenAPI document. A list read from a doc is a list from another release.
• Every destination fact is on the Destinations page: the kinds, what a binding is keyed by, what a redeploy does to it, the refusal codes.

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.

Reach the box

Connections, trigger links and bindings are box state, so point your client at the box once: