Install or verify the oma CLI and its runtimes (bun, uv, serena) before any oma-* skill, agent, or workflow runs an `oma` command. Use when `oma` is missing from PATH, when a skill says to run `oma ...` and the shell reports "command not found", or on the first task in a fresh Cursor or Grok Bot workspace.
76
95%
Does it follow best practices?
Run evals on this skill
Adds up to 20 points to the overall score
Low
Low-risk findings worth noting
The oma-* skills in this plugin describe what to do. Several of them delegate
the mechanics to the oma CLI (oma agent spawn, oma market run,
oma recap, oma hook run, oma doctor), and code search expects the
Serena MCP binary. Marketplace installs ship the skill text, not the binaries,
so a fresh workspace may have neither.
oma ... command and command -v oma is empty.oma: command not found or serena: command not found..agents/ directory and a skill needs project state
(.agents/state/, .agents/results/, oma-config.yaml).Skip this skill when oma --version already prints a version.
Run from the repository root. Every step is idempotent; rerunning is safe.
Check: command -v oma && oma --version. If both succeed, stop here.
Provision the runtimes with the official installer in non-interactive
mode. It installs bun, uv, serena-agent, and cue when missing, and
OMA_INSTALL_NO_RUN=1 skips the interactive setup it would otherwise
launch at the end:
curl -fsSL https://raw.githubusercontent.com/first-fluke/oh-my-agent/main/cli/install.sh \
| OMA_INSTALL_NO_RUN=1 bash
export PATH="$HOME/.bun/bin:$HOME/.local/bin:$PATH"Without curl, use wget -qO- in its place. Each dependency is
best-effort: the installer warns and continues when one fails.
Install the CLI as a persistent global binary (skills call bare oma):
bun install --global oh-my-agentWire the project non-interactively. This creates .agents/ with the
default preset and leaves existing files untouched:
oma install --yesVerify: oma doctor. It reports whether serena is on PATH and whether
the project is registered. Report any warning before continuing with the
original task.
oma install --yes when the repository is not yours or when
.agents/ already exists with local changes.oma command by hand. If the CLI
cannot be installed, say so and complete only the parts of the task that do
not need it.OMA_INSTALL_NO_RUN=1 in a headless Bot:
the interactive setup reads from /dev/tty and hangs.serena is still missing after step 2, run
uv tool install -p 3.13 serena-agent@latest --prerelease=allow once, then
uv tool update-shell.0e87272
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.