Matt Pocock / skills/productivity/handoff/SKILL.md
Handoff
A compact continuation note that points to existing artifacts, records the next focus and asks the agent to redact sensitive content.
Source reviewed · reviewed · Named sources were inspected. No runtime results are established by this label.
01 / Task fit
Where it may help.
These are intended uses indicated by the upstream material. They are not measured outcomes.
- Continuing a multi-session task
- Passing a bounded review to a fresh agent
What it is
Handoff turns the current conversation into a continuation note for a fresh agent. It favors links to plans, issues and diffs over copying their contents, and it lists skills the next agent may need.
Why you might use it
Use it when a task will continue in a new session and the next agent needs the current decision state. It can reduce repeated orientation, but the note still needs an owner, a reachable location and a review for omissions or secrets.
Put it in context.
Illustrative requests and outputs to review. These examples are separate from the recorded evaluation below.
Continue a synthetic code review
Example request
Create a handoff for the next session to review the CSV export. Reference docs/export-plan.md and the current diff; list remaining access checks and replace credentials with placeholders.
What to look for. A short continuation note with the next review objective and references to the source artifacts.
Before you rely on it. The default temporary location is not durable, and referenced paths must exist for the receiving agent.
Transfer a content QA task
Example request
Prepare a handoff focused on checking the next ten public review pages. Record the agreed rubric, pages already checked and unresolved findings without duplicating the rubric file.
What to look for. A focused next-step note that distinguishes completed checks from open work.
Before you rely on it. A model summary can omit failures or turn assumptions into decisions. Reconcile it with the actual work list.
02 / Setup & access
What it asks of your environment.
Requirements
- A host that exposes the current conversation and can write a text file.
- Access to the existing artifacts the handoff references; receiving agent access is a separate requirement.
- No external service or account is required by the entrypoint.
Permissions & data access
- Read the conversation and relevant artifacts; write to the OS temporary directory.
- Suggested future skills may bring their own permissions. The handoff does not authorize those tools.
Instructions alone do not enforce a sandbox. The agent host, connected tools and approvals determine what the skill can actually read, change or send.
03 / Things to check
Security concerns & practical limits.
These concerns follow from the reviewed sources. They describe possible exposure or required review; they are not confirmed vulnerabilities.
Higher attention
Redaction is an instruction, not a control
The guide tells the model to remove secrets and personal information but has no scanner or validator. Review a handoff before moving it to another agent or storage system.
Review before use
Temporary paths do not make a durable handoff
The requested OS temporary location can be cleaned up or unavailable to another machine. Copy an approved handoff into the intended durable project location before relying on it.
Review before use
References and suggested skills need rechecking
A receiving agent may lack referenced files or may load a different skill version. Verify access and inspect suggested skills before following them.
Limits and nuances
- Instruction-only entrypoint: no handoff was written from real conversation data and no fresh-agent continuation or redaction test was run.
- Temporary-folder persistence, file permissions, path portability and host support for invocation metadata were not tested.
04 / Review record
What we checked. What’s still open.
Recorded review scope
- skills/productivity/handoff/SKILL.md
- LICENSE
Not tested or established
- Instruction-only entrypoint: no handoff was written from real conversation data and no fresh-agent continuation or redaction test was run.
- Temporary-folder persistence, file permissions, path portability and host support for invocation metadata were not tested.
- Review date
- Source revision
49dd158d1076134a641b33efb035946536778336- Our relationship
- Explored. Investigated through the recorded review. No use or replication is claimed.
Upstream content can change after review. A repository revision identifies source scope; it does not prove that every script, dependency or runtime behavior was tested. How freshness is handled.
Recorded evaluation / Source review
Results with their limits attached.
Completed 5 bounded source checks covering requirements, workflow boundaries and practical security concerns. No skill workflow was executed.
- Passed
- 5
- Failed
- 0
- Total recorded
- 5
These counts refer to the cases in this report. They are not a benchmark against other skills. A source review does not establish runtime behavior.
Read the evidence reportThe report provides the case definitions, observations and baseline scope. Missing baselines or untested behaviors remain limitations.
Recorded environment
- Pinned public UTF-8 sources; exact Git blob contents fetched through GitHub and recorded with SHA-256.
- Windows 11; Python 3.12.10 source-condition verification. No account, private document or live business data.
Recorded commands (2)
Commands document this evaluation. They are not setup instructions for your environment.
Read each pinned file listed in sourceManifest.python build-guide-reviews.py — verify the recorded source conditions and reconcile report counts.Findings from this evaluation
Higher attention
Redaction is an instruction, not a control
The guide tells the model to remove secrets and personal information but has no scanner or validator. Review a handoff before moving it to another agent or storage system.
Needs attention
Temporary paths do not make a durable handoff
The requested OS temporary location can be cleaned up or unavailable to another machine. Copy an approved handoff into the intended durable project location before relying on it.
Needs attention
References and suggested skills need rechecking
A receiving agent may lack referenced files or may load a different skill version. Verify access and inspect suggested skills before following them.
Evaluation limitations
- Instruction-only entrypoint: no handoff was written from real conversation data and no fresh-agent continuation or redaction test was run.
- Temporary-folder persistence, file permissions, path portability and host support for invocation metadata were not tested.
05 / Reuse & discovery
License, attribution & popularity.
MIT
Repository MIT license text inspected at this revision. Preserve its copyright and permission notice when redistributing covered source; separate dependencies and services can have their own terms.
Why it is in this collection
skills.sh displayed 1.0M installs for this named skill on the observation date. Rounded directory telemetry; not verified unique users, a quality score or measured growth.
1,000,000 skill installs on skills.sh
- Scope
- Directory listing for mattpocock-handoff; not the whole repository
- Observed
- Time window
- Individual listing says Installs; reporting window not independently established
Popularity and inclusion do not establish quality, compatibility or security. Counts belong to their named metric and date; they are not a current ranking.
06 / Follow the evidence
Go to the original.
- Pinned skill instructions github.com
- Pinned repository license github.com
- Dated directory popularity context www.skills.sh
IonBin’s source notes are independent assessments. Upstream authors retain their work and attribution. This page does not install or execute the skill.