Stackbone guardrails skill

This skill tells you how to put a limit in place and how to tell why one is not firing. It holds no check catalog and no field lists: the checks and their settings are read live off the box, and everything else lives in the docs.

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. Guardrails (Home › Features) is the operator page and Guardrails (SDK › Humans) is the developer one. Take their paths from that list and get_doc them. Never type a path from memory: pages move, titles stay.
• The check catalog is not in the docs, it is on the box. Read it before you write a rule. It is the same schema the Studio form is generated from and the same one the runtime validates against, so a setting the catalog accepts is a setting that will run. A list of checks copied from a page goes stale the day a new one ships.

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).

There is nothing to write in code

A guardrail is not a function and there is no stackbone.guardrails in the SDK. It is a row in the box's own database, read on the turn that needs it, which is why an edit takes effect on the next turn with no rebuild and no restart.

There is also no CLI command for it. The only guardrail-adjacent thing the CLI does is operate the inbox, with stackbone hitl, and that decides a held turn rather than touching the rule. Everything else is Studio or the box's own API.