agentsclimarketplace

Handoff

Skill markoblogo/abvx-agent-skills/skills/handoff

Reviewable capability layer for coding agents. Portable skills, delivery gates, workflow patterns, and verification-first engineering.

Install
npx -y skills add markoblogo/abvx-agent-skills --skill handoff

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

  • 4 stars4 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.

What its author says it does

Copied from the file, not written here

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.

The file declares its own license as MIT. That is the author’s claim about this one file, and it is not the same thing as the license GitHub reports for the repository, which is listed with the other numbers below.

SKILL.md

1.7 KB, 291 tokens by cl100k_base, as published. Nobody here has run it

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.

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.

Gives 0 of the 12 instructions most agent orchestration skills give in 291 tokens

Counted across 742 of the 995 authors here whose files we hold, read 2026-08-06

  • run the full test suite after integrating changesin 53 of 742, across 20 files
  • reference existing artifacts by path or URLin 52 of 742, across 22 files
  • dispatch one agent per independent problem domainin 50 of 742, across 17 files
  • verify fixes do not conflictin 45 of 742, across 13 files
  • include a suggested skills section in the documentin 45 of 742, across 15 files
  • redact sensitive informationin 41 of 742, across 11 files
  • save to the temporary directory of the operating systemin 39 of 742, across 9 files
  • tailor the document to user-provided focus argumentsin 39 of 742, across 9 files
  • spot check agent changes for systematic errorsin 34 of 742, across 7 files
  • write a handoff document summarising the current conversationin 31 of 742, across 6 files
  • assign each agent a specific scopein 23 of 742, across 8 files
  • provide specific scope and clear goalin 23 of 742, across 5 files

Said here and by no other author read

  • Capture operational state not a transcript.
  • List repos branches paths URLs and servers.
  • List files changed commits PRs or releases.
  • State active hypotheses blockers or pending checks.
  • Preserve concrete dates and versions when relevant.

Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once. Length counted with cl100k_base; the agent that loads this file may tokenize it differently.

Keep looking

Skills are one crate of 328,083. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.