Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →testdouble/readability-guidance
Surfaces Han's shared Human-Readable Output Standard — the readability rule and the writing-voice profile — into the calling skill's own context, so the caller drafts in voice and runs its self-check against the current standard sourced from one canonical copy.
Passed 6 of 14 test cases with the skill, and 6 of 14 without it.
and 3 more in the full report
6 fixed4 passed either way7 still failing5 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 6 test cases the skill fixed. Same model, same prompt, with and without the skill.
Neither the personal configuration directory nor the project directory contains a .han/config.md file specifying a custom writing-voice parameter. What is the fallback writing-voice file path that should be read?
| Checked | Without skill | With skill |
|---|---|---|
| Identifies ${CLAUDE_PLUGIN_ROOT}/references/writing-voice.md as the default writing voice path. | 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.
You have invoked readability-guidance to source the shared readability standard before you draft prose. This skill
surfaces the standard into your own context and hands control back. It is a means to writing your deliverable, not the
deliverable itself: apply what it surfaces while you draft and self-check, then RETURN to the workflow that called you
and finish it.
This skill is inline — it runs in your context, not an isolated one, so the standard it surfaces stays available to you after it returns. Do not treat anything here as a stopping point or a final answer.
A structured specification, plan, phased build, work-item list, coding standard, or test plan is reader-facing whenever a human reads it end to end — to approve it, follow it, or build from it — even when downstream skills also consume it. Only an artifact consumed purely as a pipeline input, with no human reading it end to end, falls outside the standard. If a human reads your deliverable end to end, apply the standard to it.
First resolve which writing-voice profile this run uses:
.han/config.md probe supplied a writing-voice value, resolve it and check that the file exists. A
relative value resolves against the folder holding the file that declared it: the working directory for the project
file, and the personal config directory the probe reported for the personal file. A full path is used as it stands,
and a leading ~ expands to the home directory. When both files supply a value, the project file's wins.
writing-voice value, the built-in profile attest cases passed, vs 6 / 14 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.