← Back to Skills Marketplace
1081
Downloads
1
Stars
4
Active Installs
3
Versions
Install in OpenClaw
/install opencode-omo
Description
Turn coding requests into completed work. Plan with Prometheus, execute with Atlas, and iterate with Sisyphus in OpenCode.
README (SKILL.md)
OpenCode + Oh-My-OpenCode Operator
This skill is an operating guide for using OpenCode as your coding runtime, with Oh-My-OpenCode orchestration through Sisyphus, Prometheus, and Atlas.
What this skill gives you
- One-shot delivery with
ulwfor focused coding requests. - Plan-to-execution workflow via
@planand/start-work. - Repeatable defaults so code quality stays consistent across runs.
Core rules
- Do not edit code directly outside OpenCode unless explicitly asked.
- Prefer Sisyphus-first execution for coding tasks.
- For complex work: plan with Prometheus (
@plan) then execute with Atlas (/start-work).
Quick start
Verify Oh-My-OpenCode plugin
cat ~/.config/opencode/opencode.json | grep "oh-my-opencode"
If the command returns output, the plugin is installed.
You can also run the bundled checker:
./scripts/check-omo.sh
Run one-shot coding (Sisyphus + ultrawork)
opencode run --agent sisyphus "ulw implement JWT auth in this service and add tests"
Or use the bundled helper:
./scripts/run-ulw.sh "implement JWT auth in this service and add tests"
Start interactive OpenCode (Sisyphus)
opencode --agent sisyphus
Inside OpenCode:
- Use
@plan "..."to invoke Prometheus planning. - Use
/start-workto let Atlas execute the plan.
Failure handling
- If the agent asks clarifying questions mid-implementation, answer them in plan mode (Prometheus) and re-run execution.
- If you need more determinism, re-run with
ulwand a smaller, explicit request.
Integration with other skills
- agent-selfie: pair structured coding workflows with generated visual assets.
- gemini-image-gen: use the same workflow discipline for image generation automations.
- agentgram: publish progress updates, findings, and demos produced from your workflow runs.
Changelog
- v0.3.0: Added bidirectional ecosystem links and bundled workflow helper scripts.
- v0.2.0: Reworked positioning, quick start, and metadata for clearer marketplace onboarding.
- v0.1.0: Initial release with Sisyphus/Prometheus/Atlas workflow guidance.
Usage Guidance
This skill reads your OpenCode config and tells you to run local helper scripts and to invoke an OpenCode agent — those actions can execute arbitrary code in your environment. Before using it: 1) verify the opencode and clawhub binaries come from trusted sources and check their documentation; 2) inspect any ./scripts/*.sh helpers and ~/.config/opencode/opencode.json for unexpected behavior (network calls, credentials, destructive file ops); 3) run commands in an isolated environment (container or throwaway VM) first; 4) avoid running in sensitive repositories or on production systems until you're confident of the scripts' behavior. If the author can provide the helper scripts or more detail about what the opencode agent does and what the scripts perform, re-run this evaluation — that information would raise confidence and could change the verdict to benign.
Capability Analysis
Type: OpenClaw Skill
Name: opencode-omo
Version: 0.3.0
The skill is designed to guide an AI agent in using the OpenCode development environment. It includes instructions for verifying plugin installation by reading `~/.config/opencode/opencode.json` and executing local helper scripts (`./scripts/check-omo.sh`, `./scripts/run-ulw.sh`). These actions are consistent with a development-focused skill for setup and workflow management, and there is no evidence of data exfiltration, malicious execution, persistence, or prompt injection attempts to subvert the agent's core purpose or steal sensitive information. The file access is limited to a configuration file relevant to the skill's operation, and script execution is for bundled local scripts.
Capability Assessment
Purpose & Capability
Name/description describe an OpenCode orchestration helper; the declared required binaries (opencode, git, clawhub) are coherent with that purpose. It is instruction-only (no code bundled), which matches a documentation/operational guide style.
Instruction Scope
The SKILL.md directs the agent/user to read ~/.config/opencode/opencode.json (a user config path not listed in required config paths) and to run local scripts (./scripts/check-omo.sh, ./scripts/run-ulw.sh) and commands that invoke opencode agents (e.g., opencode run --agent sisyphus...). Running those scripts or agent commands can execute arbitrary code in the current environment; the instructions do not include safety checks, explicit validation steps, or guidance to inspect script contents first. This is scope creep relative to a purely read-only helper and presents an execution risk.
Install Mechanism
No install spec is provided; the skill is instruction-only. This is the lowest-risk install mechanism because nothing from the skill is written to disk by default.
Credentials
The skill does not request environment variables, credentials, or declared config paths. The only requirements are binaries (opencode, git, clawhub), which are proportionate to the described functionality. However, the instructions still access a user config file (~/.config/opencode/opencode.json) even though it wasn't declared under required config paths.
Persistence & Privilege
always is false and the skill is user-invocable. It does not request persistent platform-level privileges or to modify other skills. (Note: autonomous invocation of skills is the platform default; that by itself is expected.)
How to Use
- Make sure OpenClaw is installed (local or Docker)
- Run the install command in chat:
/install opencode-omo - After installation, invoke the skill by name or use
/opencode-omo - Provide required inputs per the skill's parameter spec and get structured output
Version History
v0.3.0
- Added integration links to other ecosystem skills (agent-selfie, gemini-image-gen, agentgram) using ClawHub URLs.
- Documented use of bundled helper scripts for verifying installation and running workflows.
- Updated changelog to reflect new integrations and scripts.
- Bumped metadata version to 0.3.0.
v0.2.0
- Updated marketplace positioning and improved quick start instructions.
- Revised metadata structure and homepage URL for compatibility.
- Expanded usage section with workflow details and integration examples.
- Added versioned changelog for easier tracking.
- No functional command changes; documentation and onboarding focus.
v0.1.0
Initial release: OpenCode + Oh-My-OpenCode operator guide (Sisyphus-first).
Metadata
Frequently Asked Questions
What is Opencode Omo?
Turn coding requests into completed work. Plan with Prometheus, execute with Atlas, and iterate with Sisyphus in OpenCode. It is an AI Agent Skill for Claude Code / OpenClaw, with 1081 downloads so far.
How do I install Opencode Omo?
Run "/install opencode-omo" in the OpenClaw or Claude Code chat to install it in one step — no extra setup required.
Is Opencode Omo free?
Yes, Opencode Omo is completely free (open-source). You can download, install and use it at no cost.
Which platforms does Opencode Omo support?
Opencode Omo is cross-platform and runs anywhere OpenClaw / Claude Code is available (cross-platform).
Who created Opencode Omo?
It is built and maintained by 김덕환 (@iisweetheartii); the current version is v0.3.0.
More Skills