Agent skill · operations · aiskillstore
jeo
JEO — Integrated AI agent orchestration skill. Plan with ralph+plannotator, execute with team/bmad, verify browser behavior with agent-browser, apply UI feedback with agentation(annotate), auto-cleanup worktrees after completion. Supports Claude, Codex, Gemini CLI, and OpenCode. Install: ralph, omc, omx, ohmg, bmad, plannotator, agent-browser, agentation.
Why this skill is useful
Adds a comprehensive orchestration workflow with executable scripts for planning, execution, UI feedback, and cleanup that are not available in public documentation.
What it needs
Requires agent-browser, agentation, bmad, ohmg, omc, omx, plannotator, ralph installed locally. About 9k tokens when loaded. Last updated 2026-08-07. 405 stars on the source repository.
What this skill does
JEO — Integrated Agent Orchestration Keyword: jeo · annotate · UI-review · agentui (deprecated) Platforms: Claude Code · Codex CLI · Gemini CLI · OpenCode A unified skill providing fully automated orchestration flow: Plan (ralph+plannotator) → Execute (team/bmad) → UI Feedback (agentation/annotate) → Cleanup (worktree cleanup) Control Layers JEO uses one cross-platform abstraction for orchestration: settings: platform/runtime configuration such as Claude hooks, Codex config.toml, Gemini settings.json, MCP registration, and prompt parameters rules: policy constraints that must hold on every platform hooks: event callbacks that enforce those rules on each platform The key JEO rules are: do not reopen the PLAN gate when the current plan hash already has a terminal result only a revised plan resets plangatestatus to pending do not process agentation annotations before explicit submit/onSubmit opens the submit gate The authoritative state is .omc/state/jeo-state.json. Hooks may help advance the workflow, but they must obey the state file. --- 0. Agent Execution Protocol (follow immediately upon jeo keyword detection) The following are commands, not descriptions. Execute them in order. Each step only proceeds after the previous one completes. STEP 0: State File Bootstrap (required — always first) If .omc/state/jeo-state.json does not exist, create it: <!-- NOTE: The worktrees array was removed from the initial schema as it is not yet implemented. Add it back when multi-worktree parallel execution tracking is needed. worktree-cleanup.sh queries git worktree list directly, so it works without this field. --> Notify the user: "JEO activated. Phase: PLAN. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills aiskillstore/jeo