--- name: format-guide description: "Product guide for producing documents, decks, and other deliverables — what to ask for, which format to pick, how the skills hand off to each other, and where finished work lands. Use whenever someone asks \"how do I make a document/deck/PDF\", \"how do I create a proposal/presentation\", \"which format should I use\", or any orientation question specifically about producing a deliverable. For first-time install, switching on connectors, or a general \"how do I get started\", the `getting-started` skill is the entry point. Routes to the right renderer; does not render anything itself." --- # Format Guide — getting started with your deliverables (MCP-hosted skill) This skill's full instructions are hosted on the `stromy-format` MCP server. Do not hardcode workflow logic locally — always fetch the live version from the MCP. ## Loading instructions 1. Read the main skill instructions: → call the `fs_read` tool on the `stromy-format` MCP with `path="skills/format-guide/SKILL.md"`. **Read it to the end.** `fs_read` returns one page at a time. If the result's `next_offset_chars` is not null — or the returned text ends in a `<<< PARTIAL READ … >>>` block — the body is incomplete: call `fs_read` again with `offset_chars` set to that value and concatenate, repeating until it comes back null. Do **not** start work on a partial skill body. Hard rules and anti-patterns often sit in the final third, and a partial read fails silently — it looks like a complete skill. 2. Discover reference files (and any other skill assets), then read on demand: → call `fs_list` with `path="skills/format-guide"` (and `path="skills/format-guide/references"`), → call `fs_read` with `path="skills/format-guide/references/"`. Follow the instructions returned by the MCP exactly. ## This MCP is the only correct path Produce this skill's output **only** by following the live SKILL.md fetched above and calling the `stromy-format` MCP's own tools. Do **not** substitute a local or identically-named base skill from elsewhere, and do **not** invent your own output path. A locally-produced or unbranded artifact is **wrong output, not a fallback** — it bypasses the server-side brand and quality gates.