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.
86%
Does it follow best practices?
Run evals on this skill
Adds up to 20 points to the overall score
Medium
Suggest reviewing before use
The skill prompts the agent to compromise the security or integrity of the user’s machine by modifying system-level services or configurations, such as obtaining elevated privileges, altering startup scripts, or changing system-wide settings.
The skill pipes a remote installer script into bash and has the agent modify PATH, run `uv tool update-shell` (which edits shell rc files), and write provider HOME configuration, but it never asks for sudo, system-file edits, new user accounts, or SSH/service changes, and the tools it installs are a known project's CLI and runtimes.
The skill fetches instructions or code from an external URL at runtime, and the fetched content directly controls the agent’s prompts or executes code. This dynamic dependency allows the external source to modify the agent’s behavior without any changes to the skill itself.
The skill instructs an inbound setup fetch that is executed: `curl ... raw.githubusercontent.com/first-fluke/oh-my-agent/main/cli/install.sh | bash`. The publisher is an individual-owned GitHub repository, not a recognized vendor or foundation, and the mutable `main` branch has no enforced digest or signature, so it is common/reputable unofficial and rated medium.
first-fluke/oh-my-agent
2bd468c
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.