markdown-to-confluence

# Markdown to Confluence This skill takes one local Markdown file and publishes it to a Confluence location that **the user must specify** — creating a new page or updating an existing one through the Atlassian MCP server. It owns everything about the posting itself: the MCP preflight, resolving the destination, reading the file, the create-or-update call, and reporting the result. It does not write the Markdown; the caller supplies an existing file. Callers that supply an explicit publish mode and location (for example `han-atlassian:project-documentation-to-confluence`) run this skill straight through without re-asking. Invoked on its own with pieces missing, it asks for them and defaults to a safe unpublished draft. ## Step 0: Atlassian MCP Preflight (hard requirement) This skill cannot run without a configured and connected Atlassian MCP server. Confirm the server is reachable by calling `mcp__claude_ai_Atlassian__getAccessibleAtlassianResources` to retrieve the cloud ID(s). If the tool is not available, the call errors, or it returns no accessible resources (typically an authentication or configuration problem), **stop immediately**. Tell the user this skill requires the Atlassian MCP server to be installed, configured, and authenticated, and that they can re-run the skill once it is connected. If more than one cloud / site is accessible, note which sites are available; you will confirm the correct one while resolving the location in Step 2. ## Step 1: Confirm the...