bash \"${CLAUDE_PLUGIN_ROOT}/scripts/han-config-dir.sh\" 2>/dev/null || echo \"$HOME/.claude\"cat .han/config.md 2>/dev/null || echo \"\"As your first action, use the Read tool on .han/config.md inside the personal config directory path above. A read\nthat returns no file is no personal configuration: continue silently. When that file or the project .han/config.md\nprobe supplies content, apply it per config-rule.md, which governs precedence\nbetween the two files, relative-path resolution, and what to do with a file that reads but cannot be used.
This skill takes one local Markdown file and publishes it to a Confluence location that the user must specify —\ncreating a new page or updating an existing one through the Atlassian MCP server. It owns everything about the posting\nitself: the MCP preflight, resolving the destination, reading the file, the create-or-update call, and reporting the\nresult. It does not write the Markdown; the caller supplies an existing file.
\nCallers that supply an explicit publish mode and location (for example\nhan-atlassian:project-documentation-to-confluence) run this skill straight through without re-asking. Invoked on its\nown with pieces missing, it asks for them and defaults to a safe unpublished draft.
This skill cannot run without a configured and connected Atlassian MCP server.
\nConfirm the server is reachable by calling mcp__claude_ai_Atlassian__getAccessibleAtlassianResources to retrieve the\ncloud ID(s). If the tool is not available, the call errors, or it returns no accessible resources (typically an\nauthentication or configuration problem), stop immediately. Tell the user this skill requires the Atlassian MCP\nserver 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\nresolving the location in Step 2.
\nResolve the Markdown file path from the arguments or conversation. Read it and confirm it exists and has content. If no\nfile path was provided, or the path does not resolve to a readable file, ask the user for the path with\nAskUserQuestion and do not proceed without one. This is the exact content that will be posted; do not rewrite,\nsummarize, or restructure it.
A body may legitimately contain embedded Confluence storage macros mixed into the Markdown — for example, an\norchestrating skill such as han-atlassian:plan-a-feature-to-confluence rewrites its cross-page links into title-based\npage-link macros (the <ac:link><ri:page ri:content-title=\"...\"/>…</ac:link> form, link body included) before handing\nthe file over. Post these verbatim along with the rest of the body; do not strip or escape them.
This skill does not search Confluence for the right place. A typical Confluence instance is large and full of\nduplicate or similarly-named pages, so guessing the destination is unreliable. The user must name the exact location.
\nAskUserQuestion to request it, and explain plainly that the skill\nneeds an exact destination because it does not search Confluence. Offer both accepted forms (a page URL, or a space\nplus parent page). This is required: do not proceed without a location./pages/<id>/ segment and call\nmcp__claude_ai_Atlassian__getConfluencePage to confirm it exists and to read its space and title. Then determine\nthe intent: update that page, or create a new child page under it. If the user did not already say, ask\nwith AskUserQuestion.mcp__claude_ai_Atlassian__getConfluenceSpaces to resolve the space ID from the\nkey or name. If a parent page was named, find it with mcp__claude_ai_Atlassian__getPagesInConfluenceSpace or\nmcp__claude_ai_Atlassian__getConfluencePageDescendants (or by page ID/URL) to get the parent page ID. With no\nparent, the new page is created at the space root.create a new page, or update an existing one), and the intended page title. If\nupdating, default the title to the existing page's title unless the user asked to rename it.The publish mode controls whether the page goes live or is saved as an unpublished draft.
\ndraft or live), use it. A caller that already confirmed the choice with\nthe user (such as han-atlassian:project-documentation-to-confluence) passes the mode through; do not ask again.draft so nothing is published live unintentionally. The user can re-run for\nlive, or you may confirm with AskUserQuestion whether to save a draft (recommended default) or publish live now.Read the Markdown file from Step 1 and publish it with the Atlassian MCP server. The Confluence MCP tools accept\nMarkdown directly via contentFormat: \"markdown\", so post the document body as-is — no manual conversion to\nstorage/XHTML is needed. Any embedded storage macros (such as the ac:link page-link macros described in Step 1) ride\nalong in the same body; post them verbatim.
Apply the publish mode from Step 3 with the create/update tool's status parameter: draft → status: \"draft\"\n(unpublished draft), live → status: \"current\" (immediately visible). Confirm the exact field against the tool's\ninput schema when you call it, and use whatever the tool exposes for draft-vs-published.
mcp__claude_ai_Atlassian__createConfluencePage with the cloud ID, space ID, title, the\nmarkdown body, contentFormat: \"markdown\", the chosen status (\"draft\" or \"current\"), and the parent page ID\nwhen one was resolved.mcp__claude_ai_Atlassian__getConfluencePage first to read the current page (for its version\nand existing content), then call mcp__claude_ai_Atlassian__updateConfluencePage with the cloud ID, page ID, title,\nthe markdown body, contentFormat: \"markdown\", and the chosen status. If the user chose draft for a page that is\nalready published and the tool cannot hold an unpublished draft over a live page, do not silently publish it live:\ntell the user, and ask whether to publish the update live or keep the changes local only.Diagram note: Markdown produced by Han's documentation skills emits Mermaid diagrams in fenced mermaid code\nblocks. Confluence does not render Mermaid natively without a Mermaid macro, so these blocks publish as code, not\nrendered diagrams. Leave them intact — do not silently strip them — and tell the user the diagrams posted as Mermaid\nsource, in case their space has a macro that renders them or they want to convert them by hand.
On success, report the created or updated page's URL, and state whether it was published live or saved as a draft. For a\ndraft, make clear the user still needs to review and publish it in Confluence. On failure, report the error and confirm\nthe source Markdown file is unchanged and intact.
\n