handoff
Create compact handoff documents for another agent, session, or human to continue work. Use when a task is long-running, context is about to compact, work must pause, an audit needs resumable state, or the user asks for a handoff, continuation note, checkpoint, or next-session br
Install
npx skills add https://github.com/markoblogo/abvx-agent-skills/tree/main/skills/handoff
claude plugin marketplace add https://llmmart.ai/marketplace.json && claude plugin install markoblogo-abvx-agent-skills@llmmart
git clone https://github.com/markoblogo/abvx-agent-skills.git
The skills CLI installs just this skill, for any of its supported agents. Claude Code installs the whole markoblogo/abvx-agent-skills collection as a plugin from our marketplace. Git is the plain clone.
Skill manifest
Handoff
Capture operational state, not a transcript. The next agent needs facts, paths, decisions, and next actions.
When To Use
Use for:
- long-running audits;
- multi-repo publication work;
- paused implementation;
- debugging sessions with active hypotheses;
- research with source ledgers;
- job/client-search workflows;
- context compaction or thread transfer.
Handoff Contents
Include:
- objective and current status;
- repos, branches, important paths, URLs, and local servers;
- decisions made and why;
- files changed, commits, PRs, or releases;
- commands already run and their result;
- active hypotheses, blockers, or pending checks;
- suggested skills for the next session;
- exact next steps in priority order.
Closeout Receipt
When the handoff follows completed project work, include:
changed: files, commits, PRs, or artifacts that matter
verified: checks and results, or why verification was unavailable
skipped_with_reason: docs, memory, cleanup, or rules intentionally not updated
follow_up: bounded next actions only
Link to existing evidence instead of repeating it. Separate local checks from push, CI, deployment, and public availability. Do not turn closeout into cleanup authority: retain temporary files and old plans unless removal was approved. Memory changes require an explicit user request; a handoff is not that request.
Compression Rules
- Link to artifacts instead of copying them.
- Do not duplicate full diffs, logs, PRDs, plans, or source docs.
- Preserve concrete dates and versions when relevant.
- Redact secrets, credentials, private contacts, and unnecessary personal data.
- Separate confirmed facts from assumptions.
Output Location
If creating a file, write it outside the project unless the user asks for an in-repo artifact. Use the OS temp directory or a clear handoff/ location approved by the repo conventions.
Final Response
Tell the user where the handoff lives, what it covers, and what the next agent should do first.
Files (abvx-agent-skills)
-
agents
-
openai.yaml 180 B
Loading…
-
-
SKILL.md 2.4 KB
--- name: handoff description: Create compact handoff documents for another agent, session, or human to continue work. Use when a task is long-running, context is about to compact, work must pause, an audit needs resumable state, or the user asks for a handoff, continuation note, checkpoint, or next-session brief. license: MIT metadata: abvx_status: experimental abvx_origin: adapted --- # Handoff Capture operational state, not a transcript. The next agent needs facts, paths, decisions, and next actions. ## When To Use Use for: - long-running audits; - multi-repo publication work; - paused implementation; - debugging sessions with active hypotheses; - research with source ledgers; - job/client-search workflows; - context compaction or thread transfer. ## Handoff Contents Include: - objective and current status; - repos, branches, important paths, URLs, and local servers; - decisions made and why; - files changed, commits, PRs, or releases; - commands already run and their result; - active hypotheses, blockers, or pending checks; - suggested skills for the next session; - exact next steps in priority order. ## Closeout Receipt When the handoff follows completed project work, include: ```text changed: files, commits, PRs, or artifacts that matter verified: checks and results, or why verification was unavailable skipped_with_reason: docs, memory, cleanup, or rules intentionally not updated follow_up: bounded next actions only ``` Link to existing evidence instead of repeating it. Separate local checks from push, CI, deployment, and public availability. Do not turn closeout into cleanup authority: retain temporary files and old plans unless removal was approved. Memory changes require an explicit user request; a handoff is not that request. ## Compression Rules - Link to artifacts instead of copying them. - Do not duplicate full diffs, logs, PRDs, plans, or source docs. - Preserve concrete dates and versions when relevant. - Redact secrets, credentials, private contacts, and unnecessary personal data. - Separate confirmed facts from assumptions. ## Output Location If creating a file, write it outside the project unless the user asks for an in-repo artifact. Use the OS temp directory or a clear `handoff/` location approved by the repo conventions. ## Final Response Tell the user where the handoff lives, what it covers, and what the next agent should do first. -
SKILL_CARD.md 1.3 KB
Loading…
Comments (0)
Sign in to join the conversation.
Reviews (0)
No reviews yet.
No comments yet.