pairing
100 / 100 · Low risk
Fine to try.
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. Use when someone says to pair with them on something, asks to collaborate rather than direct, wants to review as it goes, or wants to guide the work piece by piece — on code, on a design decision, or on writing. For a test-first build it runs tdd, for restructuring it runs refactor,…
What this skill can do
We found nothing in the files we read that matches our rules. That does not prove the skill is safe: see the limits of static scanning.
Install
Paste this into your terminal. It downloads exactly the version we scanned, not whatever is newest.
if [ -e ~/.agents/skills/'pairing' ] || [ -L ~/.agents/skills/'pairing' ]; then echo 'A skill folder named pairing already exists — not replacing it' >&2; false; else d=$(mktemp -d) && git clone --quiet --filter=blob:none --no-checkout 'https://github.com/testdouble/han' "$d" && git -C "$d" checkout --quiet 'abba73a773528905a8f3d15956029394746e5c7f' -- 'han-core/skills/pairing' && mkdir -p ~/.agents/skills && cp -R "$d"/'han-core/skills/pairing' ~/.agents/skills/'pairing' && rm -rf "$d"; fi
Codex reads ~/.agents/skills directly. For Claude Code, Cursor, Copilot, Gemini CLI, Antigravity or OpenCode, also link it. For Claude Code: ln -s ~/.agents/skills/'pairing' ~/.claude/skills/'pairing' (other agents: ~/.cursor/skills, ~/.copilot/skills, ~/.gemini/skills, ~/.gemini/config/skills, ~/.config/opencode/skills). Or install through the finder skill, which does both.
Badge for your README
[](https://zalavijaysinh.github.io/skilltrust/repos/testdouble/han/)
Score history
| Date | Version | Score |
|---|---|---|
| 2026-11-07 | abba73a | 100 |