How do I install the Handoff Claude skill?

Run npx skillmds@latest add claude-world-director-mode-lite/handoff-claude in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Handoff Claude safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Handoff Claude?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Handoff Claude free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Handoff Claude?

claude-world (@claude-world-director-mode-lite) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Handoff Claude by claude-world-director-mode-lite

Name: Handoff Claude
Author: claude-world

Handoff Claude

Continue a task in Claude Code through a portable Director handoff packet. Use when work started in Codex CLI or Grok Build should move to Claude, or when a fresh Claude session needs the current decisions and verification evidence.

claude-world Updated Sep 22, 2026

File contents

Handoff to Claude Code

Use the shared session-relay workflow. Claude starts a new native session and reads the same vendor-neutral packet used by Codex and Grok.

ROOT="${CLAUDE_PROJECT_DIR:-${GROK_WORKSPACE_ROOT:-}}"
[[ -n "$ROOT" ]] || ROOT="$(git rev-parse --show-toplevel 2>/dev/null || pwd)"
RELAY="$ROOT/.director-mode/bin/director-relay"
[[ -x "$RELAY" ]] || RELAY="$HOME/.claude/bin/director-relay"

"$RELAY" create \
  --from <codex|grok> --to claude \
  --goal "..." --summary "..." --next "..."

"$RELAY" continue --to claude

The second command only prints the interactive command. Add --run when the user explicitly wants to launch it, or --headless for a one-shot claude -p continuation.

Claude Code's own --continue and --resume remain the right tools for resuming a Claude-native history. Use a Director packet when the source is another CLI, when a concise checkpoint is preferable, or when the workflow may later move again.

Profiles created with CLAUDE_CONFIG_DIR can still isolate authorized Claude accounts, but profile credentials, permissions, plugins, MCP configuration, and session histories are not copied into the packet.

Frequently asked questions