Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →testdouble/pairing
Build work collaboratively in reviewable pieces, handing each piece back for review before starting the next, so the person stays in the lead and steers while the work happens instead of reviewing a finished result.
Passed 5 of 13 test cases with the skill, and 4 of 13 without it.
and 7 more in the full report
6 fixed3 passed either way10 still failing4 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.
We are starting a new pairing session on a repository that has no `.han/config.md` file and no personal configuration directory. Where should the running session feedback record be created and saved?
| Checked | Without skill | With skill |
|---|---|---|
| Designates `.han/pairing/` as the default session record directory. | 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 ""find . -maxdepth 1 -name "CLAUDE.md" -type fAs 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.
Read collaborative-stop-rule.md before Step 4. It defines what a stop presents, when the pre-build ask fires, what makes a choice expensive to walk back, and what to do with the answer. The skills this one hands work to follow the same file, which is what makes a stop feel the same whoever performed it.
Two constraints from that file govern every step below and are repeated here because they are the ones most easily lost:
Resolve where the running feedback record will be written, using the output base directory from the configuration
probed above. Absent any configuration, write it beside the work under .han/pairing/.
Name the file for this run so a second run in the same repository does not overwrite the first. State the path to the person in Step 4's plan, in one clause, BECAUSE a record they cannot find is not a record.
Read the file first if it already exists. A run resuming after an interrupted session inherits the record rather than starting a new one.
test cases passed, vs 4 / 13 without
More skills from the same source and nearby in the registry, with their headline benchmark lift.