Handoff in

Use when resuming Miller-backed work from a handoff packet or validating a packet before continuing in another harness, model, or session.From its SKILL.md

Install

npx -y skills add anortham/miller --skill handoff-in

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

3 stars3 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

SKILL.md

3.4 KB, as published. Nobody here has run it

Handoff In

Read a Miller handoff packet, validate it against the current workspace, and produce a compact resume summary. Do not blindly trust stale packet context.

Inputs

If no packet path is supplied, read:

.miller/handoffs/latest.md

Packets should use packet_format: miller-handoff-v1 and live under .miller/handoffs/.

Workflow

Read the packet path and frontmatter. Extract at least:

workspace_root
workspace_id
branch
head
dirty_state
index_built_revision
index_latest_revision

Also extract the packet's changed-file list from the Changed Files section, especially the git status --short and git diff --name-only blocks.

Collect current facts:

workspace(operation="status", format="json")
workspace(operation="health")

git rev-parse --show-toplevel
git branch --show-current
git rev-parse --short HEAD
git status --short
git diff --stat
git diff --name-only

Compare packet facts to current facts:

Workspace root
Branch
HEAD
Dirty state
Exact changed-file list from git status --short
Exact tracked changed-file list from git diff --name-only
Miller index_built_revision / index_latest_revision from index.built_revision and index.latest_revision

Status	Meaning	Action
`safe-to-resume`	Same workspace root, same branch, same HEAD, matching dirty state, matching changed-file list, and Miller health is fresh enough.	Use packet impact/context and continue from `Next Action`.
`drifted-but-resumable`	Same workspace root, but branch, HEAD, dirty state, changed-file list, or Miller index revisions drifted in an explainable way.	Say what drifted, rerun Miller checks, then continue with updated facts.
`blocked`	Packet is missing, root points at a different repo, Miller health is unusable, or drift changes the product intent.	Stop and ask for the smallest needed decision.

When there is a current dirty diff, rerun:

impact(git=true)

When packet context is stale or the next action is vague, rerun:

context(query="<packet goal or next action>", token_budget=<budget>)

Resume Summary

Output a compact summary, not a dump of the whole packet:

## Handoff Intake

status: safe-to-resume | drifted-but-resumable | blocked
packet: <path>
workspace: <current root>
branch/head: <branch> <head>
drift: <none or concrete differences>
miller: <fresh/needs refresh/problem>

## Continue From

<One-paragraph session note summary.>

## Next Action

<The next command, file, test, or Miller call to run.>

Rules

Validate workspace root before using packet instructions.
Treat branch, HEAD, dirty-state, changed-file list, or Miller revision drift as a reason to re-check impact/context, not as proof the packet is useless.
Do not call Goldfish automatically.
Do not include secrets from the packet in the chat transcript.
If the packet points at .miller/handoffs/latest.md but it is missing, report blocked and ask for the packet path.