- name
SKILL.md
스킬 파일은 게시자의 저장소에 그대로 있습니다.
복사한 명령을 터미널에 붙여넣습니다. 이 SKILL.md가 해당 에이전트에 설치됩니다.
npx skills add testdouble/han --skill project-documentation-to-confluence -a cursor -y복사한 명령을 터미널에 붙여넣습니다. 이 SKILL.md가 해당 에이전트에 설치됩니다.
npx skills add testdouble/han --skill project-documentation-to-confluence -a claude-code -y복사한 명령을 터미널에 붙여넣습니다. 이 SKILL.md가 해당 에이전트에 설치됩니다.
npx skills add testdouble/han --skill project-documentation-to-confluence -a codex -y복사한 명령을 터미널에 붙여넣습니다. 이 SKILL.md가 해당 에이전트에 설치됩니다.
npx skills add testdouble/han --skill project-documentation-to-confluence -a grok -y복사한 메시지를 Grok Bot 채팅에 보냅니다. Bot이 GitHub에서 이 SKILL.md를 가져와 모든 Bot이 공유하는 스킬에 추가합니다.
Install this skill: https://github.com/testdouble/han/tree/HEAD/han-atlassian/skills/project-documentation-to-confluence게시자 제공
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
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, which governs precedence
between the two files, relative-path resolution, and what to do with a file that reads but cannot be used.
This skill produces project documentation with the han-documentation:project-documentation skill, lets the user review the
result, and then publishes it to a Confluence location that the user must specify. It is a thin orchestrator: the
documentation work belongs to han-documentation:project-documentation, and the publishing work belongs to
han-atlassian:markdown-to-confluence. This skill only validates its inputs, runs the documentation to a temporary
file, gets the user's review and publish choice, and hands the file to the publisher.
The five steps below are the whole skill. It does not resolve Confluence pages or call the Confluence MCP create/update
tools itself; han-atlassian:markdown-to-confluence owns all of that.
Confirm the skill has everything it needs before spending effort producing documentation:
mcp__claude_ai_Atlassian__getAccessibleAtlassianResources to
confirm the server is connected and 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 it once it is connected. Do not fall back to a local-only run; for local-only documentation, point them at
han-documentation:project-documentation. This preflight runs first so a missing server fails before any documentation is
generated.han-documentation:project-documentation verbatim in Step 2.AskUserQuestion, explaining plainly that the skill needs an exact destination because it
does not search Confluence. Do not resolve the page tree here — only confirm a location was given. Carry it through
to Step 5; han-atlassian:markdown-to-confluence resolves it.Invoke the han-documentation:project-documentation skill with the Skill tool, forwarding all provided context verbatim:
the feature name or document path argument, the scope, any known entry points, and the relevant conversation context. Do
not summarize, trim, or reinterpret the user's context; pass it through so han-documentation:project-documentation runs exactly
as it would on its own — except add one explicit instruction: it must write the resulting documentation to a file
under /tmp/ (for example /tmp/<feature-slug>.md) rather than into the project's docs directory. This keeps the
working draft out of the repo until the user decides to publish it, and because the path is explicit input it outranks
any output-directory the project or personal .han/config.md supplies (see
../../references/config-rule.md).
Let han-documentation:project-documentation complete its full process (codebase exploration, writing the doc, content audit,
information-architecture review, and verification). Capture the exact /tmp/ file path it wrote. That markdown file
is the source content for Confluence. Proceed to Step 3 once it finishes.
Tell the user the exact /tmp/ path of the generated documentation so they can open and review it before deciding
whether to publish. State plainly that the content has not been published anywhere yet.
Publishing to Confluence puts the content where other people can see it, so require an explicit choice before posting.
Ask with AskUserQuestion, restating the /tmp/ file path and the Confluence destination the user provided.
Offer three options, listing the draft option first as the recommended default:
If the user keeps it local only, stop. Report the /tmp/ doc path and state clearly that nothing was published to
Confluence. Otherwise, record the chosen publish mode (draft or live) for Step 5.
Invoke the han-atlassian:markdown-to-confluence skill with the Skill tool, forwarding:
/tmp/ markdown file path captured in Step 2,draft or live), stated explicitly so
han-atlassian:markdown-to-confluence does not re-ask.han-atlassian:markdown-to-confluence resolves the location, reads the file, creates or updates the page in the chosen
mode, handles Mermaid diagrams, and reports the resulting page URL. Relay its result to the user: the created or updated
page's URL and whether it went live or was saved as a draft. If publishing fails, report the error and confirm the
/tmp/ markdown file is unchanged and intact.
han-documentation:project-documentation ran with the full forwarded context and wrote the
documentation to a /tmp/ file whose path was captured./tmp/ path was shown to the user before any publish.han-atlassian:markdown-to-confluence created or
updated the page in the chosen mode and its URL was relayed; when the user declined, only the /tmp/ doc exists.>
---name: project-documentation-to-confluencedescription: >---# han-atlassian/skills/project-documentation-to-confluence/SKILL.mdFAQ
게시자에게서 han-atlassian/skills/project-documentation-to-confluence/SKILL.md를 다운로드하거나 경로를 복사해 저장소를 엽니다. PlugMCP는 스킬을 목록에 올릴 뿐 파일을 호스팅하지 않습니다.
게시자가 https://github.com/testdouble/han에서 관리합니다.
Claude, Cursor, Codex, Grok Build는 게시자의 저장소에서 추가한 SKILL.md를 읽을 수 있습니다. Grok Bot은 채팅에서 스킬의 GitHub 폴더 링크를 보내면 설치합니다.