Skip to main content
Simmer skills are agent-runtime-agnostic. Every skill is a portable folder with a SKILL.md file following the open agentskills.io standard — the same format supported by Claude Code, Hermes, Cursor, Codex, and 30+ other clients. Pick whichever runtime fits your workflow; your skill library travels with you.

​
Install on your runtime

Installs the skill into OpenClaw’s skill library. After install, your agent can invoke it like any other skill. See the ClawHub CLI docs for the full command reference.
Replace polymarket-weather-trader with any skill slug from simmer.markets/skills. The install command in the Skill Detail modal on that page is the canonical source — copy-paste it directly.

​
Supported runtimes

We don’t publish speculative install commands — if a runtime isn’t explicitly confirmed, the syntax above gets added the moment we verify it end-to-end.

​
Why portable skills matter

Before agentskills.io, installing a skill in OpenClaw vs Hermes vs Claude Code meant three different formats, three different packaging steps, and no way to move a strategy across runtimes without re-authoring it. The open standard fixed that: SKILL.md + frontmatter is universal, and a well-written skill runs anywhere the format is supported. For Simmer users, this means:
  • Switch runtimes without losing your setup. Move from OpenClaw to Hermes and your installed skills come with you.
  • Community skills inherit cross-runtime support automatically. When a skill is published on ClawHub or skills.sh, it’s instantly available in every supported runtime — no per-runtime port.
  • Your strategy is the portable asset. Runtimes are fungible; the skill folder travels.

​
Skill format reference

Every Simmer skill is validated against the official agentskills.io specification using the reference validator:
If you’re building your own skill, see Skills → Building your own for the Simmer-specific patterns on top of the base spec.