markdown-to-confluencelisted
Install: claude install-skill dzivkovi/claude-skills
# markdown-to-confluence
Turn a Markdown file into a Confluence Cloud page, with ```mermaid fences rendered locally so they arrive as diagrams rather than as a wall of source, and with existing local image references resolved so they arrive as pictures rather than as dead links. Sibling of `markdown-to-pdf` (print-grade PDF) and `markdown-to-epub` (e-reader); all three render Mermaid through the same local `mmdc` step and differ only in what they do with the result.
## Step 0 - the hard dependency
**This skill does nothing without the Atlassian MCP server connected and authenticated for the target site.** Publishing happens through its `createConfluencePage` and `updateConfluencePage` tools; there is no REST fallback in this skill.
Check for `mcp__atlassian__*` tools before starting. If they are absent, stop and tell the user to connect and authorize the Atlassian MCP via `claude mcp` or `/mcp` **in an interactive session**. An agent cannot complete the OAuth flow itself, so there is no way to work around this from inside a task.
`mmdc` is needed only when the document contains mermaid fences: `npm install -g @mermaid-js/mermaid-cli`. Documents without diagrams never invoke it. The preparation script itself has no Python dependencies beyond the standard library.
## Step 1 - what the MCP already handles, and the one thing it does not
The Atlassian MCP accepts `contentFormat: "markdown"` and converts the body to native Confluence storage format on its own. Verified again