Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →testdouble/investigate-to-confluence
Runs an evidence-based investigation of a bug, failure, or unexpected behavior with investigate and publishes the resulting investigation report to a user-specified Confluence location.
Passed 3 of 9 test cases with the skill, and 3 of 9 without it.
and 3 more in the full report
4 fixed4 passed either way11 still failing3 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.
The investigation for the GraphQL query depth limit issue has completed and generated a report file at /tmp/graphql-depth-limit.md. What must be presented to the user before soliciting their publishing decision?
| Checked | Without skill | With skill |
|---|---|---|
| Displays the exact /tmp/ file path to the user for review. | Passed | Passed |
| States explicitly that no repository code was modified. | 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 an evidence-based investigation with the core han-coding:investigate skill, lets the user review the
resulting report, and then publishes it to a Confluence location that the user must specify. It is a thin
orchestrator: the investigation work belongs to han-coding:investigate, and the publishing work belongs to
han-atlassian:markdown-to-confluence. This skill only validates its inputs, runs the investigation to a temporary
file, gets the user's review and publish choice, and hands the file to the publisher.
han-coding:investigate produces a single report file (the investigation plan: problem statement, evidence summary,
root cause analysis, planned fix, validation results, and summary). 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: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 investigation:
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 investigation, point them
at han-coding:investigate. This preflight runs first so a missing server fails before any investigation work
begins.test cases passed, vs 3 / 9 without
More skills from the same source and nearby in the registry, with their headline benchmark lift.