markdown-to-confluence

## Project Context

- personal config directory: !`bash "${CLAUDE_PLUGIN_ROOT}/scripts/han-config-dir.sh" 2>/dev/null || echo "$HOME/.claude"`
- project .han/config.md: !`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
that returns no file is no personal configuration: continue silently. When that file or the `project .han/config.md`
probe supplies content, apply it per [config-rule.md](../../references/config-rule.md), which governs precedence
between the two files, relative-path resolution, and what to do with a file that reads but cannot be used.

# 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 Source Markdown File

Resolve the Markdown file path from the arguments or conversation. Read it and confirm it exists and has content. If no
file path was provided, or the path does not resolve to a readable file, ask the user for the path with
`AskUserQuestion` and do not proceed without one. This is the exact content that will be posted; do not rewrite,
summarize, or restructure it.

A body may legitimately contain embedded Confluence storage macros mixed into the Markdown — for example, an
orchestrating skill such as `han-atlassian:plan-a-feature-to-confluence` rewrites its cross-page links into title-based
page-link macros (the `<ac:link><ri:page ri:content-title="..."/>…</ac:link>` form, link body included) before handing
the file over. Post these verbatim along with the rest of the body; do not strip or escape them.

## Step 2: Resolve the Target Confluence Location (required)

**This skill does not search Confluence for the right place.** A typical Confluence instance is large and full of
duplicate or similarly-named pages, so guessing the destination is unreliable. The user must name the exact location.

1. **Find a location in the request.** Check the arguments and conversation for either of:
   - a **Confluence page URL** (to update that page, or to create a child page under it), or
   - a **space** (key or name) plus an optional **parent page** (title, ID, or URL).
2. **If no location was provided, ask for one.** Use `AskUserQuestion` to request it, and explain plainly that the skill
   needs an exact destination because it does not search Confluence. Offer both accepted forms (a page URL, or a space
   plus parent page). This is required: do not proceed without a location.
3. **Resolve the location concretely now, so failures surface early.** Use the cloud ID from Step 0 for every call.
   - **From a page URL:** extract the page ID from the `/pages/<id>/` segment and call
     `mcp__claude_ai_Atlassian__getConfluencePage` to confirm it exists and to read its space and title. Then determine
     the intent: **update that page**, or **create a new child page under it**. If the user did not already say, ask
     with `AskUserQuestion`.
   - **From a space (+ parent):** call `mcp__claude_ai_Atlassian__getConfluenceSpaces` to resolve the space ID from the
     key or name. If a parent page was named, find it with `mcp__claude_ai_Atlassian__getPagesInConfluenceSpace` or
     `mcp__claude_ai_Atlassian__getConfluencePageDescendants` (or by page ID/URL) to get the parent page ID. With no
     parent, the new page is created at the space root.
4. **Record the resolved target:** cloud ID, space (ID + human name), parent page ID (if any), existing page ID (if
   updating), the **mode** (`create` a new page, or `update` an existing one), and the intended page **title**. If
   updating, default the title to the existing page's title unless the user asked to rename it.

## Step 3: Determine the Publish Mode

The publish mode controls whether the page goes live or is saved as an unpublished draft.

- If the caller supplied an explicit mode (`draft` or `live`), use it. A caller that already confirmed the choice with
  the user (such as `han-atlassian:project-documentation-to-confluence`) passes the mode through; do not ask again.
- If no mode was supplied, **default to `draft`** so nothing is published live unintentionally. The user can re-run for
  `live`, or you may confirm with `AskUserQuestion` whether to save a draft (recommended default) or publish live now.

## Step 4: Publish to Confluence

Read the Markdown file from Step 1 and publish it with the Atlassian MCP server. The Confluence MCP tools accept
Markdown directly via `contentFormat: "markdown"`, so post the document body as-is — no manual conversion to
storage/XHTML is needed. Any embedded storage