agentleFS
Sign inStart free
claude-worldclaude-world/director-mode-lite/skills/handoff-claude/SKILL.md

handoff-claude

Skill80 starsChanged 8 months agoMITView on GitHub

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.

We split this skill into the rules it gives an agent

1 rule. About 0 are common, 0 are distinctive, and 1 is very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈0

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Use the shared session-relay workflow.

    line 9

≈ “Common” is an estimate: at least 1 in 5 of the 308,232 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

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.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free