claude-world/director-mode-lite / skills/handoff-grok
handoff-grok
VerifiedContinue a task in xAI Grok Build using the shared Director handoff packet. Use when the user says to use Grok, requests a Grok review, or wants Grok Build to take over work started in Claude Code or Codex CLI.
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 1.4 KB |
SKILL.md
View on GitHub---
name: handoff-grok
description: Continue a task in xAI Grok Build using the shared Director handoff packet. Use when the user says to use Grok, requests a Grok review, or wants Grok Build to take over work started in Claude Code or Codex CLI.
user-invocable: true
---
# Handoff to Grok Build
Use the `session-relay` workflow so Grok receives the goal, decisions, Git
state, verification, and next steps without relying on another vendor's native
session ID.
```bash
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 <claude|codex> --to grok \
--goal "..." --summary "..." --next "..."
"$RELAY" continue --to grok
```
The second command prints an interactive Grok command. Add `--run` only when
the user wants it launched immediately, or `--headless` for `grok -p`.
Grok automatically reads Claude-compatible project assets (skills, rules,
`CLAUDE.md`, MCP servers, and hooks), and its `/import-claude` command copies
`~/.claude` settings. Neither carries a conversation: Grok Build 1.0.62 has no
`grok import` command, so the portable packet is the session format.
Grok's approvals, permission rules, sandbox, network access, and hook trust stay
under Grok's native configuration. This skill does not change them.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| reverse-engineer-anythingmorluto/reaReverse engineer native, managed, Electron/JavaScript, packaged, firmware, and browser targets with REA, and build agent environments (AgentEnv bundles) of web applications from a live instance or a capture, and of Linux desktop apps with a task from a request. Use shipped-artifact or requested runtime evidence to explain features, compare versions, decompile code, or guide a reconstruction. Skip REA for ordinary source-repository architecture analysis. | Stars: 472k | Updated | Claude CodeCodex | Verified | Install |
| diagnosing-superpowersobra/superpowersUse when a superpowers session went wrong and your human partner wants to know why — repeated work, ignored plans, stumbles, poor results, a skill that didn't fire, "it took too long", "why is it so expensive", "what is it doing" — or wants to build a bug report for the superpowers maintainers, for the current session or a past one identified by id or path, on any harness. | Stars: 323k | Updated | Claude CodeCodex | Verified | Install |
| dispatching-parallel-agentsobra/superpowersUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies | Stars: 323k | Updated | Claude CodeCodex | Verified | Install |
| executing-plansobra/superpowersUse when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is available | Stars: 323k | Updated | Claude CodeCodex | Verified | Install |