Open source or closed source,it is your call.
A skill generated with OOMOL runs its underlying tool functions reliably in the cloud; once users install oo-cli, they can use it directly in Codex and Claude Code.
Today, when Codex or Claude Code calls your skill, it pulls the code to local and runs it there. Your algorithms, business logic, and call chains are fully exposed to the consumer.
A cloud skill runs in the cloud. Users call the interface; your code stays with you.
Servers, auto-scaling, billing, subscription management, secrets, usage analytics… Writing the core logic is 20% of the work. The other 80% is delivery infrastructure.
Cloud handles runtime, subscriptions, configuration, and data. You just write the logic.
From skill creation to cloud runtime — one complete path.
oo-cli is the best entry point for using skills inside Codex and Claude Code. Open the install guide first, then use the video on the right to see the real flow.
Show installing, searching, inspecting, and running a skill in Codex.
Tell the agent what skill you want, let Studio generate the first version, then validate it locally. You do not need to learn a platform DSL before you begin.
Show the path from prompting to local validation.
After a skill is released, Cloud handles runtime, subscriptions, configuration, and usage data. You do not need a second product layer around the same implementation.
Keep the delivery loop running through subscriptions.
Keep secrets, access, releases, and usage in one place.
Bring subscriptions, settings, and operational data into one backend.
Think of it as the GUI version of oo-cli. It uses the same skills through a more direct interface. CLI is better for workflows; GUI is better for straightforward use.
Show both the chat surface and the structured surface.
No upfront payment. Bring your own model plus 200 free Cloud Task minutes each month — enough to complete your first Studio-to-production delivery cycle.
If you already have model quota, connect it directly instead of paying for another service. We recommend starting with GLM-5.
Follow the guide and you can usually finish local validation first.
The free Cloud Task quota is often enough for scheduled jobs, lightweight automation, and delivery validation.
Use the free quota to validate the flow before you spend more.
Start by getting the usage path working in oo-cli. When you need your own skill, install Studio to generate, validate, and publish it.
