Stackbone CLI skill

This skill tells you how to drive the stackbone CLI: the order of operations, the conventions every command obeys, and the loops you run. It holds no flag tables: every flag, output shape and exit code lives in the docs, one page per command.

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 (area cli). It returns every CLI page under its section with a one-line description. How to find the page below says which page a task needs; take its path from that list and get_doc it. Never type a path from memory: pages move, titles stay.
• Before you run a command with a flag you have not verified in this session, read its page.
• When you do not know which command does something, search_docs with the question in plain words and area: "cli".
• stackbone <command> --help is the local truth for the installed version. When the docs and the binary disagree, the binary wins.

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 call the CLI