Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →testdouble/code-overview-to-confluence
Produces a progressive-disclosure overview of unfamiliar code or a pull request's changes with code-overview and publishes the resulting overview to a user-specified Confluence location.
Passed 2 of 8 test cases with the skill, and 1 of 8 without it.
and 2 more in the full report
4 fixed1 passed either way18 still failing2 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 4 test cases the skill fixed. Same model, same prompt, with and without the skill.
A developer generates an overview for `src/cli.ts` target destination `TOOLS` page `54321`, but decides 'No, keep it local only' at the confirmation prompt. What happens to the scratch file?
| Checked | Without skill | With skill |
|---|---|---|
| Keeps the local scratch file intact when publishing is declined. | Passed | Passed |
| Confirms to the user that nothing was uploaded to Confluence. | Missed | Passed |
The instructions your model reads when the skill loads.
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 runs a progressive-disclosure code overview with the core han-coding:code-overview skill, lets the user
review the resulting overview, and then publishes it to a Confluence location that the user must specify. It is a
thin orchestrator: the overview work belongs to han-coding:code-overview, and the publishing work belongs to
han-atlassian:markdown-to-confluence. This skill only validates its inputs, runs the overview to a scratch file, gets
the user's review and publish choice, and hands the file to the publisher.
han-coding:code-overview produces a single scratch file (the overview: what the code does, how it flows, where to
start, and — in PR mode — what changed and what to watch when reviewing). It does not produce companion artifacts, so
this skill publishes that one file as a single Confluence page — the single-page sibling of
han-atlassian:investigate-to-confluence and han-atlassian:project-documentation-to-confluence, not the
parent-plus-children tree of han-atlassian:plan-a-feature-to-confluence.
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 on an overview:
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 a local-only overview, point them at
han-coding:code-overview. This preflight runs first so a missing server fails before any overview work begins.small, medium, or large). All of this — together with the relevant conversation context — is
forwarded to han-coding:code-overview verbatim in Step 2. A target is not required: with none given,test cases passed, vs 1 / 8 without
Published skills whose descriptions closely match this one, with their headline benchmark lift.
More skills from the same source and nearby in the registry, with their headline benchmark lift.