Skills vs plugins
| Skills | Plugins | |
|---|---|---|
| What they are | Trading strategies (Python scripts + SKILL.md) | Runtime extensions (TypeScript npm packages) |
| How they run | On a schedule (cron) or on-demand | Persistent background services |
| Published to | ClawHub | npm |
| Installed via | clawhub install <slug> | openclaw plugins install <name> |
| Example | polymarket-weather-trader — runs every 15 min, checks NOAA, trades | simmer-autoresearch — continuously optimizes skill config in the background |
Available plugins
| Plugin | Description | Status |
|---|---|---|
simmer-autoresearch | Autonomous skill optimization — mutates config, measures results, keeps what works | Pro |
simmer-reactor | Real-time whale activity monitor and trade reactor | Coming soon |
Install a plugin
Configure a plugin
Plugin config lives in your OpenClawplugins.json. Each plugin defines its own config schema:
SIMMER_API_KEY) are read from your agent’s environment automatically — you don’t need to duplicate them in plugin config.
Requirements
- OpenClaw agent runtime (plugins are OpenClaw extensions)
- Simmer Pro plan for premium plugins (autoresearch, reactor)
- simmer-sdk installed (
pip install simmer-sdk) for plugins that trade
