← Back to Skills Marketplace
347
Downloads
0
Stars
2
Active Installs
1
Versions
Install in OpenClaw
/install oh-my-openagent
Description
Configure and operate oh-my-openagent (OmO), the OpenCode plugin that adds multi-agent orchestration, skills, hooks, MCPs, and multi-provider model routing....
Usage Guidance
This skill appears coherent for configuring a local multi-agent plugin, but it enables powerful capabilities: shell execution, file read/write, background/continuous loops, and MCP servers that can be started with environment variables. Before installing or enabling it: (1) inspect the upstream repository and release artifacts on the listed homepage; (2) back up your OpenCode config and auth.json and inspect auth.json for sensitive tokens; (3) do not provide broad provider credentials unless you trust the code — prefer provider-specific, least-privilege keys; (4) restrict agent/tool permissions (disable bash/webfetch/skill_mcp or limit tools per-agent) and disable automatic background/continuation features until tested; (5) if possible, test in an isolated environment (VM/container) first. If you want, I can produce a checklist of specific config flags to change to minimize risk (e.g., disable background tasks, restrict tools for Sisyphus, refuse automatic MCP env interpolation).
Capability Analysis
Type: OpenClaw Skill
Name: oh-my-openagent
Version: 1.0.0
The skill bundle provides documentation and configuration for 'oh-my-openagent,' a multi-agent orchestration system. It describes a highly capable environment with access to over 40 tools, including shell execution (bash/interactive_bash), file system manipulation, and access to sensitive provider authentication tokens in '~/.local/share/opencode/auth.json'. While these risky capabilities are plausibly required for the stated purpose of a coding assistant, the broad permissions and the installation of external packages via 'bunx' (SKILL.md) warrant a suspicious classification according to the provided criteria, despite the lack of clear evidence of malicious intent or data exfiltration.
Capability Assessment
Purpose & Capability
Name/description, SKILL.md, and the reference files are coherent: the files document agents, categories, hooks, tools, providers, and configuration locations that an OmO plugin legitimately needs. There are no required env vars, binaries, or install steps bundled with the skill that are unrelated to the stated functionality.
Instruction Scope
SKILL.md and the reference docs describe reading/writing local OpenCode config files (~/.config/opencode/, ~/.local/share/opencode/auth.json) and running the installer (bunx). The instructions do not themselves command the agent to exfiltrate secrets, but they explicitly reference local auth storage and describe many tools (read/write/bash/webfetch/skill_mcp) and autonomous features (background tasks, /ralph-loop). Because the skill documents these powerful capabilities, an agent implementing OmO could legitimately access local configs and start background/autonomous tasks — review any runtime tool calls or MCP declarations before enabling.
Install Mechanism
This is an instruction-only skill with no install spec or code files to write/execute. The SKILL.md suggests running 'bunx oh-my-opencode install' (a reasonable project install command) or manual edits to config files. No remote downloads or extract/install steps are embedded in the skill package itself.
Credentials
The skill declares no required environment variables or credentials (proportional). However, the documentation references provider authentication stored locally (~/.local/share/opencode/auth.json) and shows examples of MCP entries that accept API keys from environment variables. The skill does not itself demand unrelated secrets, but OmO's ability to spawn MCP servers and use provider tokens means users should not expose broad credentials without review.
Persistence & Privilege
always:false and default autonomous invocation behavior are appropriate. The skill describes long-running/background/continuation mechanisms (todo continuation, ralph-loop, ulw-loop, background tasks, MCP servers) which are powerful. This is coherent with a multi-agent orchestration plugin, but gives broad runtime reach—users should control which agents/tools are allowed and avoid enabling global always-on behaviors unless intended.
How to Use
- Make sure OpenClaw is installed (local or Docker)
- Run the install command in chat:
/install oh-my-openagent - After installation, invoke the skill by name or use
/oh-my-openagent - Provide required inputs per the skill's parameter spec and get structured output
Version History
v1.0.0
oh-my-openagent 1.0.0
- Initial release introducing a multi-agent orchestration plugin for OpenCode.
- Adds 11 specialized agents, 8 configurable task categories, and automatic multi-provider model routing.
- Includes over 40 built-in hooks, specialized skills, tools, and MCP (Multi-Channel Provider) integrations.
- Offers flexible configuration for models, agents, categories, and provider priorities via local config files.
- Supports advanced features like slash commands, provider authentication, and deep customization for agent roles and behaviors.
Metadata
Frequently Asked Questions
What is Oh-my-openagent?
Configure and operate oh-my-openagent (OmO), the OpenCode plugin that adds multi-agent orchestration, skills, hooks, MCPs, and multi-provider model routing.... It is an AI Agent Skill for Claude Code / OpenClaw, with 347 downloads so far.
How do I install Oh-my-openagent?
Run "/install oh-my-openagent" in the OpenClaw or Claude Code chat to install it in one step — no extra setup required.
Is Oh-my-openagent free?
Yes, Oh-my-openagent is completely free, licensed under MIT-0. You can download, install and use it at no cost.
Which platforms does Oh-my-openagent support?
Oh-my-openagent is cross-platform and runs anywhere OpenClaw / Claude Code is available (cross-platform).
Who created Oh-my-openagent?
It is built and maintained by enjoyer (@kolyanberoks-23loud); the current version is v1.0.0.
More Skills