Draft the requested content, then publish it as a Gryz document or note using publish_document or create_note, and return the resulting link. Use when the user asks to "publish this to Gryz", "post this as a doc", or "save this and give me a link to share". Do NOT use when the user only wants the draft and has not asked for it to be published or saved anywhere — drafting and publishing are two separate steps; only take the second if asked.

# Publish to Gryz Draft the requested content, then actually publish it — the loop-closer skill. ## When to use - "Publish this to Gryz", "post this as a doc", "save this and give me a link to share", or the user has already been drafting with another skill (structured-doc-drafting, clear-writing) and now wants the result shared. ## Do NOT use for - Drafting alone, when the user hasn't asked for it to be saved or shared anywhere. Drafting and publishing are two separate steps — only take the publish step when asked. Don't publish a draft the user hasn't approved. ## How to publish 1. **Confirm the content is ready.** If this follows a drafting step, make sure the user has actually seen and approved the draft before publishing it — don't auto-publish the first draft. 2. **Choose the right tool:** - `publish_document` for content meant to be shared or read as a standalone page — a report, a changelog, a public writeup. Ask (or infer from context) whether it should be `public` (shareable link) or `restricted` (private to the dashboard). - `create_note` for something meant to stay in the user's private working notes rather than be shared — check `list_notes` first for a related note to update instead of creating a duplicate. 3. **Publish once.** Each `publish_document` call creates a new document — don't call it twice for the same content "just in case." 4. **Return the link.** After publishing, give the user the resulting URL and slug plainly — that's the whole point of this skill. 5. **Mention retention/visibility** briefly if it's not obvious (e.g. "this public link expires in 30 days on your plan" for a lower tier) so the user isn't surprised later. ## Examples **Flow:** user asks to "write a short changelog entry for the new dark mode toggle and publish it." 1. Draft the changelog entry (short, user-facing impact stated plainly). 2. Show the draft, confirm it's what they want. 3. Call `publish_document` with `content_type: "markdown"`, `visibility: "public"`. 4. Reply: "Published — here's the link: https://gryz.ai/d/abc123/."