Agent skill

Handoff

by imbue-ai in imbue-ai/sculptor

Hand off the current work to a fresh agent — either a new agent in the SAME workspace, or a new workspace — seeded with a summary of the current context.

MITAuto-check passedAgent Workflows

Install Handoff

skills CLI
$ npx skills add imbue-ai/sculptor --skill handoff -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install imbue-ai/sculptor handoff --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/imbue-ai/sculptor.git skills-src && mkdir -p .claude/skills && cp -r skills-src/sculptor/sculptor-experimental/skills/handoff .claude/skills/handoff && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
handoff
GitHub stars
238
Token cost
~1.3k tokens
SKILL.md length
650 words
Files
1
Skills in repo
29
Repo updated
First seen
Licence
MIT

At a glance

Hand off the current work to a fresh agent — either a new agent in the SAME workspace, or a new workspace — seeded with a summary of the current context.

  • Works in 5 steps: Choose the destination → Pre-flight: commit uncommitted work… → Compose the handoff prompt → …
  • Agent Workflows work in your project
  • SKILL.md covers Step 1 — Choose the destination, Step 2 — Pre-flight: commit…, Step 3 — Compose the handoff… and Step 4 — Create the handoff, plus 1 more section
  • Calls git

What it does

Handoff is an agent skill from imbue-ai/sculptor. Hand off the current work to a fresh agent — either a new agent in the SAME workspace, or a new workspace — seeded with a summary of the current context.

Its SKILL.md is about 1.3k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in Agent Workflows. The repository describes itself as: Build product with grounded, parallel coding agents. The licence is MIT.

When your agent uses it

  • Agent Workflows work in your project

Example prompts

  • “/handoff”

Workflow steps

5 steps, taken from the step headings in SKILL.md.

  1. Choose the destination
  2. Pre-flight: commit uncommitted work (new-workspace mode only)
  3. Compose the handoff prompt
  4. Create the handoff
  5. Report back

What it can do on your machine

Read from SKILL.md and the folder at commit f847102. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Shell commands in SKILL.md call:

    • git

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md. Its commands use git, which can reach the network depending on how they are called.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Handoff loads about 1.3k tokens when it runs. Until then it costs about 40 tokens; SKILL.md has 650 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~40
When it runs · the whole SKILL.md, loaded when a task matches
~1.3k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from imbue-ai/sculptor at commit f847102, republished under its MIT licence (© imbue-ai). 650 words, ~1,284 tokens.

Download SKILL.mdSave it as .claude/skills/handoff/SKILL.md (or your agent's skills folder).
name
handoff
description
Hand off the current work to a fresh agent — either a new agent in the SAME workspace, or a new workspace — seeded with a summary of the current context.
when_to_use
Invoke when the user wants to continue the current work with a fresh agent — e.g. "hand this off", "start fresh but keep the context", or when the current…
user_invocable
true

Handoff

ARGUMENTS: $ARGUMENTS

Hand off the current work to a fresh agent, seeded with a summary of the current context. $ARGUMENTS (if provided) describes what the new agent should focus on next; if empty, infer it from the recent conversation.

This skill uses the sculpt CLI. The agent shell already has SCULPT_WORKSPACE_ID (current workspace) and SCULPT_PROJECT_ID set.

Step 1 — Choose the destination

The handoff can land in one of two places:

  • New agent, same workspace — shares this workspace's filesystem and branch, so it picks up exactly where this one left off (including uncommitted changes).
  • New workspace — a fresh, isolated workspace on its own auto-named branch cut from the current branch, for continuing the work in a clean checkout.

If $ARGUMENTS already makes the choice clear (e.g. it mentions "new agent", "same workspace", or "new workspace"), use that. Otherwise, ask the user which one with your question tool — mcp__sculptor__ask_user_question if it's available, otherwise the built-in AskUserQuestion — and wait for the answer before creating anything. (The tool call raises the "waiting for input" status that alerts the user; don't ask in plain text.)

Step 2 — Pre-flight: commit uncommitted work (new-workspace mode only)

Skip this step if the user chose "new agent, same workspace" — the same workspace shares this working tree, so uncommitted work is visible to the new agent as-is.

For new workspace mode, the new workspace is cut from a commit on the current branch in the project's on-disk git repo. Anything not committed won't be visible to the new agent. Walk the user through it so they're never surprised.

Run from the repo root:

bash
git status --porcelain

If the output is non-empty, list the affected paths (just the paths, not the diffs) and ask with your question tool:

You have N uncommitted change(s). Commit them before handing off?

  • Yes, commit them — write a concise commit message inferred from the conversation and run git add -A && git commit -m "<msg>". Surface the message you used in your next text reply so the user can amend if they want.
  • No, leave them — the new agent won't see those changes.

Do not prompt for a push. The new workspace shares the user repo's .git, so committed work is visible to it locally — pushing to origin is a separate concern (CI, MR linkage, code-review visibility) the user can do when they're ready, and Sculptor's in-workspace diff display doesn't require origin connectivity either (origin/* refs are seeded locally at workspace creation).

Show full SKILL.md (247 more words)Show less

Step 3 — Compose the handoff prompt

Write a self-contained prompt so the new agent can continue without access to this conversation:

  • A summary of the task and the current state of the work.
  • Key context: relevant files, decisions made, what is done, what remains, and anything already tried that didn't work.
  • The next concrete step(s) to take (from $ARGUMENTS or the inference above).

Summarize; don't dump the whole transcript.

Step 4 — Create the handoff

New agent, same workspace — the new agent shares this workspace's branch and files, so reference them by path; it can see them (and uncommitted changes) directly:

bash
sculpt agent create \
  -w "$SCULPT_WORKSPACE_ID" \
  --name "<short task name>" \
  --json \
  --prompt "<the prompt from step 3>"

New workspace — first get the current branch, then create a workspace + agent based off it:

bash
git rev-parse --abbrev-ref HEAD   # the source branch

sculpt run \
  --strategy worktree \
  --branch "<current-branch>" \
  --name "<short task name>" \
  --json \
  "<the prompt from step 3>"

--strategy worktree --branch <current> creates the new workspace on a fresh, auto-named branch cut from the current branch — the same mechanism the UI uses — so the committed work carries over.

Use sculpt run, not sculpt workspace create. sculpt run creates the workspace, its agent, and the git worktree in one step. sculpt workspace create only registers a workspace record — no agent, no checkout — so it renders as a blank screen in the UI. To add an agent to an already-empty workspace, run sculpt agent create -w <ws_id> -p "...".

Add -m sonnet (or another model) to override the default model.

Step 5 — Report back

Parse the JSON output and tell the user the new agent ID (and the new workspace ID, when a new workspace was created) so they can switch to it.

© imbue-ai, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in sculptor/sculptor-experimental/skills/handoff of imbue-ai/sculptor.

Open the folder on GitHubat commit f847102

Compare with similar skills

Handoff next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Handoff compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Handoff this skillimbue-ai/sculptor238—~1.3kAutomated safety check: PassMIT
MCP Server Builderanthropics/skills180k63 repos~2.3kAutomated safety check: PassApache-2.0
Hook Development for Claude Code Pluginsanthropics/claude-plugins-official38k10 repos~4.1kAutomated safety check: NotesApache-2.0
Using Superpowersfarm-fe/farm5.6k35 repos~1.4kAutomated safety check: PassMIT
Executing Plans Inlineobra/superpowers297k2 repos~5.1kAutomated safety check: PassMIT
Skill CreatorAzure/azqr79689 repos~8.2kAutomated safety check: PassApache-2.0

Similar skills

  • MCP Server Builder

    anthropics/skills

    Official

    Guides the design and implementation of Model Context Protocol servers in TypeScript or Python, from tool naming and error messages to evaluation.

    180k GitHub starsUsed in 63 repos~2.3k tokens
    Agent WorkflowsAuto-check passed
  • Hook Development for Claude Code Plugins

    anthropics/claude-plugins-official

    Official

    Explains how to write Claude Code plugin hooks, both prompt-based checks and bash commands, for events such as PreToolUse, Stop and SessionStart.

    38k GitHub starsUsed in 10 repos~4.1k tokens
    Agent WorkflowsAuto-check: notes
  • Using Superpowers

    farm-fe/farm

    A skill your agent uses when starting any conversation - establishes how to find and use skills, requiring Skill tool invocation before ANY response including clarifying questions

    5.6k GitHub starsUsed in 35 repos~1.4k tokens
    Agent WorkflowsAuto-check passed
  • Executing Plans Inline

    obra/superpowers

    Has the agent carry out an implementation plan itself, task by task in the current session, keeping a ledger, proving each step with a test and ending with one whole-branch review.

    297k GitHub starsUsed in 2 repos~5.1k tokens
    Agent WorkflowsAuto-check passed
  • Skill Creator

    Azure/azqr

    Official

    Create new skills, modify and improve existing skills, and measure skill performance.

    796 GitHub starsUsed in 89 repos~8.2k tokens
    Agent WorkflowsAuto-check passed
  • Claude Code Agent Development

    anthropics/claude-plugins-official

    Official

    Explains how to write agents for Claude Code plugins: the markdown file with YAML frontmatter, trigger descriptions, model and color settings, and system prompt design.

    38k GitHub starsUsed in 7 repos~2.8k tokens
    Agent WorkflowsAuto-check passed

More from imbue-ai/sculptor

All 29 skills in this repo
  • Auto QA Iphone

    imbue-ai/sculptor

    QA the Sculptor mobile web UI on a real iOS Simulator, driven headlessly from a Mac.

    238 GitHub stars~3.1k tokensUpdated yesterday
    Auto-check passed
  • Measure React Renders

    imbue-ai/sculptor

    Compare React component render counts between origin/main and the current branch during a user-defined UI scenario (e.g.

    238 GitHub stars~603 tokensUpdated yesterday
    Auto-check passed
  • Post PR To Slack

    imbue-ai/sculptor

    Post a one-line PR announcement to a Slack channel, and mark it :merged: when the PR merges.

    238 GitHub stars~1.6k tokensUpdated yesterday
    Auto-check passed
  • Batch Claude Runner

    imbue-ai/sculptor

    Run Claude programmatically against collections of files in the codebase.

    238 GitHub stars~308 tokensUpdated yesterday
    Auto-check passed
  • Build Sculptor Extension

    imbue-ai/sculptor

    Build or modify a Sculptor extension — a runtime ESM module loaded into the Sculptor UI.

    238 GitHub stars~3.4k tokensUpdated yesterday
    Auto-check passed
  • Code Review Checklist

    imbue-ai/sculptor

    Review a set of code changes against Sculptor's review categories and produce a markdown findings table.

    238 GitHub stars~3.6k tokensUpdated yesterday
    Auto-check passed

Categories

Questions about Handoff

What does Handoff do?

Hand off the current work to a fresh agent — either a new agent in the SAME workspace, or a new workspace — seeded with a summary of the current context. Handoff is an agent skill from imbue-ai/sculptor. Hand off the current work to a fresh agent — either a new agent in the SAME workspace, or a new workspace — seeded with a summary of the current context.

When should I use Handoff?

Handoff fits situations like: agent Workflows work in your project.

How do I install Handoff in Claude Code?

Run `npx skills add imbue-ai/sculptor --skill handoff -a claude-code`. Or copy the skill folder (sculptor/sculptor-experimental/skills/handoff in imbue-ai/sculptor) into .claude/skills/handoff in your project. Claude Code loads it when a task matches its description.

How do I install Handoff in Codex?

Run `npx skills add imbue-ai/sculptor --skill handoff -a codex`. Or copy the skill folder (sculptor/sculptor-experimental/skills/handoff in imbue-ai/sculptor) into .agents/skills/handoff in your project. Codex loads it when a task matches its description.

Can I use Handoff in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add imbue-ai/sculptor --skill handoff -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/handoff, .gemini/skills/handoff, .github/skills/handoff and .opencode/skills/handoff in your project.

What does Handoff need to run?

Going by SKILL.md and its folder, Handoff needs the command-line tools its instructions call (git).

Does Handoff access the network?

SKILL.md contains no URLs. Its commands use git, which can reach the network depending on how they are called. This is read from the text; nothing was executed.

Is Handoff safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Handoff use?

Handoff is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Handoff use?

About 1.3k tokens (SKILL.md is roughly 5.1k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Handoff?

Skills that share tags, products or a category with Handoff: MCP Server Builder (anthropics/skills, 180k stars), Hook Development for Claude Code Plugins (anthropics/claude-plugins-official, 38k stars), Using Superpowers (farm-fe/farm, 5.6k stars) and Executing Plans Inline (obra/superpowers, 297k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Handoff?

imbue-ai (a GitHub organization) maintains it in imbue-ai/sculptor, which has 238 GitHub stars. The repository holds 29 skills in this directory. The repository was last updated on October 9, 2026.

Source: imbue-ai/sculptor on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.