jev-control-plane

Installation
SKILL.md

Jev Control Plane

Use this skill to operate Jev for the coding-agent environment that loaded it. The harness returns decisions; optional host integrations apply selected results. Loading this Agent Skill alone does not register or activate those integrations. Report the exact host, profile, runtime mode, hook trust, and observed result before claiming automatic behavior.

When to use this skill

Use it when installing or configuring Jev for one runtime, checking or toggling that runtime's profile, selecting a backend, or invoking an approved routing, pruning, or review command. Jev is optional. Keep each profile isolated and fail closed when a selected operation has no usable backend.

Select the current agent profile

Identify the coding-agent runtime that loaded this skill, not its model/provider. Set JEV_AGENT to one current canonical host ID: claude, jeo, jeopi, pi, omp, gjc, codex, opencode, agy, kimi, grok, cursor, crush, antigravity, or aside. The host list is intentionally separate from provider/model names.

Guide aliases normalize to canonical hosts: claude-code → claude, jeo-code → jeo, oh-my-pi → omp, antigravity-cli → agy, and kimi-code-cli → kimi. AGY means the Antigravity CLI; it is distinct from the Antigravity IDE (antigravity). Grok Build is explicit-selection-only: set JEV_AGENT=grok (or JEO_SKILLS_AGENT=grok during setup); never infer it from PATH, because an installed grok may be Superagent rather than Grok Build.

Use the explicitly assigned profile, otherwise the current host's profile in ~/.agents/jev/agents.json, otherwise the host ID itself. Aside instead requires a selected account and defaults to aside-u<account>. Set that exact value as JEV_PROFILE in this session. Keep independent accounts/configurations separate (for example aside-u0 or claude-work). If the host or assignment is unknown, stop Jev work rather than choosing the first installed CLI. A selected missing/disabled profile never falls back to jeopi, another profile, or legacy configuration.

The controller's --agent is the canonical host identity; standalone setup's --agent is the skill installation destination. --profile always selects Jev state. See the shared host table for each destination, storage root, and verified Jev boundary; it is the source of truth for AGY, Kimi Code, and Grok Build distinctions.

After a successful per-host setup, the guide creates or updates that canonical host's ~/.agents/jev/agents.json binding through the existing controller configure --agent <host> --profile <profile> --backend <selected> --apply path. It preserves custom host fields, other host entries, and saved per-profile keys; configuration-only binding is not native hook registration.

Installs
6
GitHub Stars
60
First Seen
Oct 24, 2026