om — agent playbook

This is the umbrella skill markdown for the OpenMarket CLI (om). Any shell-capable LLM client reads these files to learn how to drive the binary.

One binary, seven jobs:

• Market data: om points, om markets, om symbols, om coins, om exchanges, om normalized-symbols, om block-sizes, om tenors, om enum, om usage, om subscribe, om polymarket, om metric. Calls the OpenMarket Data API at https://api.openmarket.xyz via the bundled SDK. om metric get computes any registered scalar metric (price, volume, funding_rate, open_interest, plus indicators like RSI / MACD / EMA / BB / ATR / Stoch) for a symbol on-demand; same metric registry the alert engine uses, so values match what an alert would fire on.
• WRUN packages: om install installs WRUN packages from local paths, GitHub repos, or registry tarballs; om wrun ... scaffolds, validates, builds, exports, installs, lists, removes, upgrades, and configures WRUN indicator packages. Installed outputs become metric ids like wrun/@scope/name/output that work with metric lookup, alerts, and chart adds (om collab indicator add --type wrun/...). See marketplace.md for the registry workflow and agent-native authoring.
• Alert engine: om alert ... to author alerts as JSON files under ~/.openmarket/alerts/ (typed conditions OR custom-script conditions backed by files under ~/.openmarket/scripts/), optional Hyperliquid or Polymarket auto-execution via on_fire.execute, om service install to install a launchd/systemd daemon that watches them, om alert watch to tail fire events in real time.
• News / text-event feeds: om news ... manages three products behind one capability-gated surface — alerts (name a trigger, get pinged when it happens), briefs (name a subject, get a few story cards a day), and streams (ready-made feeds from Synoptic's marketplace). Acquiring any of them auto-attaches a per-feed event-watch, so what they carry reaches journals and notification channels. See news.md.
• Event watches: om event-watch ... manages persistent event-stream monitors; om event-journal ... retrieves their local Markdown event journals on demand. See event-watches.md.
• Research studies: om research study runs strictly correlational event studies over accepted event-watch rows and one asset's candles. Use it to inspect event anchors and pre/post returns, never as a trade signal. See research.md.
• Collab bridge: om collab ... to inspect and mutate OpenMarket chart workspaces through a persistent WebSocket the daemon holds open to collab-service. Commands are grouped by resource (session / workspace / chart / indicator / drawing) — the same shape kubectl and docker use so the surface scales as new server-side actions ship. Reads: om collab session status, om collab workspace list, om collab workspace state --workspace <id>. Mutations: om collab chart layout (multi-chart grid — 3x1/2x2/...), om collab chart symbol / chart interval / chart plot-type (per-pane), om collab chart sync (symbol/interval/crosshair sync), om collab indicator add (RSI/MACD/EMA/...), om collab drawing add (TrendLine, FibonacciRetracement), om collab chart view (set the visible time range — ephemeral). See chart-actions.md for the full workflow. A grid/layout request is a chart layout change FIRST, then per-pane chart symbol.
• Strategies: om signal + om strategy wire a signal (over a watched event stream or a market metric) to automated trading on Polymarket or Hyperliquid — a signal emits a direction/conviction view, a strategy binds it to a pinned market + sizer, and the daemon evaluates enabled strategies each tick (observe / paper / dry_run / live). Author, then om strategy resume; the daemon acts (no foreground strategy-run command). See strategy.md.

The same om binary owns all of these surfaces. There is no separate "data", "wrun", "runner", "research", or "collab" CLI.