oh-my-grok

oh-my-grok (OMG)

Multi-agent orchestration for Grok Build, ported from oh-my-claudecode (OMC).

OMG bundles OMC's orchestration skills and agent personas, rebranded and re-pathed for Grok (namespaces, env vars, and config dirs all point at Grok instead of Claude Code). Grok Build reads Claude-compatible plugins natively, so OMG installs and runs as a first-class Grok plugin.

Status: v0.1 — capability layer ported, engine layer pending. The 31 skills and 19 agents are ported and Grok-namespaced. The Node runtime (the omc CLI, lifecycle hooks, HUD, MCP bridge, tmux workers) is preserved verbatim under engine-reference/ and is not yet active — see PORTING.md for the roadmap and which skills depend on it.

What's inside

Layer	Path	Count	Status
Skills	skills/	31	Ported + Grok-namespaced
Agents	agents/	19	Ported
Plugin manifest	.claude-plugin/	—	Grok-native
Engine runtime	engine-reference/	53 scripts + bridge	Reference only (not active)

Install

Grok Build consumes this as a plugin:

grok plugin install /Users/kevintaylor/Documents/GitHub/oh-my-grok --trust
grok plugin list

Or via minikev (it installs OMG into Grok automatically when enabled):

export MINIKEV_GROK_USE_OMG=1
minikev grok

Once installed, skills are available under the oh-my-grok: namespace, e.g. /oh-my-grok:ultrawork, /oh-my-grok:plan, /oh-my-grok:deep-dive.

Relationship to OMC

Grok already reads OMC plugins with zero config, so this is not required to get OMC's behavior in Grok. OMG exists to be Grok-first: a clean namespace (oh-my-grok:), Grok paths (~/.grok/, $GROK_PLUGIN_ROOT), and a future runtime whose workers spawn grok rather than claude.

Upstream credit: all skills and agents derive from Yeachan-Heo/oh-my-claudecode (MIT). See LICENSE.