How do I install the Okhp3 Session Handoff skill?

Run npx skillmds@latest add okhp3/okhp3-session-handoff in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Okhp3 Session Handoff safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Okhp3 Session Handoff?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Okhp3 Session Handoff free to use?

Yes. Installing skills from SkillMD is free. This skill is licensed under MIT.

Who published Okhp3 Session Handoff?

OKHP3 (@okhp3) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Okhp3 Session Handoff by okhp3 — Agent Skill

Name: Okhp3 Session Handoff
Author: OKHP3

Okhp3 Session Handoff

Create a durable continuation record when work pauses, becomes blocked, crosses a machine, or crosses an agent host. Use after substantial work or when the owner asks for a handoff. Record changed files, reasoning, evidence tiers, validation, limitations, and the exact next action without relying on chat memory.

OKHP3 f11a24e 3 files · 3.4 KB Updated Sep 17, 2026

File contents

okhp3-session-handoff

OverKill Hill P³ · overkillhill.com · github.com/OKHP3

Inputs and output

Require a project root, handoff destination, objective, and current work inventory. Return the handoff path, source boundary, status, next action, evidence ledger, checks, limitations, and owner decisions. If the destination is not identified, return BLOCKED rather than guessing.

Run okhp3-artifact-validation first when practical. Write a dated Markdown record under the user-approved handoff destination, using a collision-safe filename, containing:

source host and date;
objective and current status;
changed files or artifact inventory;
why non-obvious decisions were made;
confirmed, inferred, proposed, and unknown conclusions where relevant;
checks run, real results, and checks not run;
known defects, limitations, and owner decisions needed;
exact next action and the files needed to resume.

Keep paths relative. Do not claim that another copy has received or applied the handoff unless that destination was directly inspected.

When new evidence changes an existing handoff, add a dated addendum if the same handoff remains the natural continuity record. Preserve the earlier conclusion and explain why it changed. Do not rewrite history to make the record look consistently correct.

About

Built by Jamie Hill · OverKill Hill P³ Published at github.com/OKHP3 Part of the OKHP3/skillz Agent Skill library. MIT License -- free to use, fork, and adapt. A nod to the source is appreciated.

---name: okhp3-session-handoffdescription: Create a durable continuation record when work pauses, becomes blocked, crosses a machine, or crosses an agent host. Use after substantial work or when the owner asks for a handoff. Record changed files, reasoning, evidence tiers, validation, limitations, and the exact next action without relying on chat memory.license: MIT---# okhp3-session-handoff**OverKill Hill P³** · [overkillhill.com](https://overkillhill.com) · [github.com/OKHP3](https://github.com/OKHP3)## Inputs and outputRequire a project root, handoff destination, objective, and current workinventory. Return the handoff path, source boundary, status, next action,evidence ledger, checks, limitations, and owner decisions. If the destinationis not identified, return `BLOCKED` rather than guessing.Run `okhp3-artifact-validation` first when practical. Write a dated Markdownrecord under the user-approved handoff destination, using a collision-safefilename, containing:- source host and date;- objective and current status;- changed files or artifact inventory;- why non-obvious decisions were made;- confirmed, inferred, proposed, and unknown conclusions where relevant;- checks run, real results, and checks not run;- known defects, limitations, and owner decisions needed;- exact next action and the files needed to resume.Keep paths relative. Do not claim that another copy has received or applied thehandoff unless that destination was directly inspected.When new evidence changes an existing handoff, add a dated addendum if the samehandoff remains the natural continuity record. Preserve the earlier conclusionand explain why it changed. Do not rewrite history to make the record lookconsistently correct.## AboutBuilt by [Jamie Hill](https://overkillhill.com) · [OverKill Hill P³](https://overkillhill.com)Published at [github.com/OKHP3](https://github.com/OKHP3)Part of the [OKHP3/skillz](https://github.com/OKHP3/skillz) Agent Skill library.MIT License -- free to use, fork, and adapt. A nod to the source is appreciated.

Frequently asked questions