Agent skill

Perfect Storm Options Trader

by LeoYeAI in LeoYeAI/openclaw-master-skills

Autonomous but risk-bounded options trading agent spec for the "Perfect Storm" strategy (paper trading only).

MITAuto-check passedBusiness, Finance & HR

Install Perfect Storm Options Trader

skills CLI
$ npx skills add LeoYeAI/openclaw-master-skills --skill perfect-storm-options-trader -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install LeoYeAI/openclaw-master-skills perfect-storm-options-trader --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/LeoYeAI/openclaw-master-skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/perfect-storm-options-trader-v2 .claude/skills/perfect-storm-options-trader && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
perfect-storm-options-trader
GitHub stars
2.2k
Token cost
~5.5k tokens
SKILL.md length
2,112 words
Files
4
Skills in repo
1,235
Repo updated
First seen
Licence
MIT

At a glance

Autonomous but risk-bounded options trading agent spec for the "Perfect Storm" strategy (paper trading only).

  • Works in 12 steps: Purpose and Scope → Canonical Reference Files → Operating Workflow → …
  • Evaluating an OpenClaw-based discretionary options trader that scans an approved universe
  • SKILL.md covers 1. Purpose and Scope, 2. Canonical Reference Files, 3. Operating Workflow and 4. Confidence Scoring (0–100), plus 11 more sections
  • Calls node; reaches paper-api.alpaca.markets; needs APCA_API_KEY_ID and APCA_API_SECRET_KEY

What it does

Perfect Storm Options Trader is an agent skill from LeoYeAI/openclaw-master-skills. Autonomous but risk-bounded options trading agent spec for the "Perfect Storm" strategy (paper trading only). Use when configuring, operating, or evaluating an OpenClaw-based discretionary options trader that scans an approved universe, grades PS+/PS- setups, selects liquid long call/put contracts, sizes conservatively, enforces strict daily risk controls, and journals every decision. Relevant when integrating OpenClaw with Alpaca (paper) via API/MCP, when writing/validating riskconfig.yaml constraints, and when…

Its SKILL.md is about 5.5k tokens, which your agent loads only when the skill is triggered. The skill folder holds 3 other files (for example `AGENTS.md`, `_meta.json` and `risk_config_openclaw_best_practices.yaml`).

It sits in Business, Finance & HR, covering Trading and backtesting. It works with Model Context Protocol. The repository describes itself as: 🧠 Curated collection of 1209+ best OpenClaw skills — weekly updated by MyClaw.ai. The licence is MIT.

When your agent uses it

  • Evaluating an OpenClaw-based discretionary options trader that scans an approved universe
  • Grades PS+/PS- setups
  • Selects liquid long call/put contracts
  • Sizes conservatively

Example prompts

  • “Perfect Storm”
  • “/perfect-storm-options-trader”

Workflow steps

12 steps, taken from the step headings in SKILL.md.

  1. Purpose and Scope
  2. Canonical Reference Files
  3. Operating Workflow
  4. Confidence Scoring (0–100)
  5. Event Risk Protocol
  6. Daily Risk Controls and Halt Conditions
  7. Output Contract (Required for Every Evaluation)
  8. Journaling Requirements
  9. Alpaca Integration (Paper)
  10. Behavior Rules
  11. Decision Priority Hierarchy
  12. IV Context Check (Best Practice Addition)

What it can do on your machine

Read from SKILL.md and the folder at commit e5199b5. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Shell commands in SKILL.md call:

    • node

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    Hosts in commands or code, which the agent is likely to contact:

    • paper-api.alpaca.markets

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names these keys or tokens, usually read from environment variables:

    • APCA_API_KEY_ID
    • APCA_API_SECRET_KEY

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Perfect Storm Options Trader loads about 5.5k tokens when it runs. Until then it costs about 155 tokens; SKILL.md has 2,112 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~155
When it runs · the whole SKILL.md, loaded when a task matches
~5.5k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from LeoYeAI/openclaw-master-skills at commit e5199b5, republished under its MIT licence (© LeoYeAI). 2,112 words, ~5,475 tokens.

Download SKILL.mdSave it as .claude/skills/perfect-storm-options-trader/SKILL.md (or your agent's skills folder). This skill also uses 3 other files; get the full folder from GitHub.
name
perfect-storm-options-trader
description
Autonomous but risk-bounded options trading agent spec for the "Perfect Storm" strategy (paper trading only). Use when configuring, operating, or evaluating an OpenClaw-based discretionary options trader that scans an approved universe, grades PS+/PS- setups, selects liquid long call/put contracts, sizes conservatively, enforces strict daily risk controls, and journals every decision. Relevant when integrating OpenClaw with Alpaca (paper) via API/MCP, when writing/validating risk_config.yaml constraints, and when producing auditable trade decision objects (ENTER / HOLD / EXIT / SKIP).
version
2.0.0
tags
trading, options, paper-trading, alpaca, risk-management

Perfect Storm Options Trader — OpenClaw Skill v2

Paper trading only. This skill must never execute against a live brokerage endpoint. If live credentials or a live base URL are detected at any point, stop immediately and request explicit human confirmation before proceeding.


1. Purpose and Scope

This skill defines the complete behavioral, governance, and execution spec for an OpenClaw agent running the Perfect Storm (PS+/PS−) options strategy.

The agent's mandate in one sentence:

Trade only when setup quality, market regime, liquidity, and risk conditions all align strongly enough to justify premium risk. "No trade" is a valid— often preferred—output.

The agent produces one of five symbolic states per scan cycle per symbol:

StateMeaning
IGNOREFails pre-filter; stop evaluating this symbol
WATCHLISTInteresting but not yet ready; monitor next cycle
ARM_ENTRYSetup is forming; prepare contract selection and size
ENTERAll gates pass; submit limit order
EXITExisting position must be reduced or closed now

2. Canonical Reference Files

FilePurpose
references/AGENTS.mdFull strategy rulebook: universe, setup definitions, indicator stack, sizing/exit logic, journaling schema
references/risk_config.yamlHard limits: account config, per-trade risk, daily/weekly drawdown caps, option filters
scripts/alpaca.mjsMinimal Alpaca REST helper for account state, positions, orders

Always load references/risk_config.yaml at agent startup. If the file is missing or unreadable, halt and request it before doing anything else.


3. Operating Workflow

Execute these phases in strict order. Any gate failure returns the symbol to IGNORE or SKIP and logs the reason.

Phase 0 — Boot and Safety Checks
1. Load risk_config.yaml — halt if missing
2. Confirm APCA_API_BASE_URL == https://paper-api.alpaca.markets — halt if live
3. Fetch account state via scripts/alpaca.mjs account
4. Compute current portfolio heat (open positions × notional risk)
5. Check daily/weekly loss counters — halt new entries if limits hit
6. Confirm data feeds are live and spread data is fresh (< 60s)

If any safety check fails → set agent_state = HALTED, log reason, do not scan.

Phase 1 — Market Regime Classification (Gate 1)

Classify the broad market environment using SPY/QQQ as primary proxies:

RegimeSignal CharacteristicsAllowed Bias
TRENDING_BULLPrice > 20/50/200 EMA stack; ADX > 20; shallow pullbacksPS+ calls preferred
TRENDING_BEARPrice < EMA stack; ADX > 20; weak bouncesPS− puts preferred
CHOPPrice whipping around EMAs; ADX < 20; no follow-throughReduce size 50%; raise confidence threshold to exceptional_score
SHOCKVIX spike > 25%; spreads blown out; correlation breakdownHalt new entries

Default rule: If regime cannot be clearly classified → CHOP. In CHOP or SHOCK, only enter if confidence_score >= exceptional_score from risk_config.yaml (default 85).

Phase 2 — Universe Scan and Pre-Filter (Gate 2)

Start from the approved universe in references/AGENTS.md. For each symbol apply:

✓ Underlying price >= min_stock_price (config)
✓ Avg daily share volume >= min_avg_daily_share_volume (config)
✓ ATR% >= min_atr_percent (config)
✓ Relative volume >= min_relative_volume (config)
✗ Earnings within avoid_earnings_days_before days → SKIP
✗ Macro event within avoid_macro_minutes_before minutes → SKIP
✗ Abnormal spread expansion detected → SKIP

Rank survivors by setup readiness, cap at max_symbols_ranked_per_cycle.

Phase 3 — Perfect Storm Detection and Scoring (Gate 3)
PS+ Bullish Checklist

Score one point per condition met. Maximum 10 points.

  1. Higher timeframe (30m/60m) trend is bullish (price > 50 EMA, ADX rising)
  2. Execution timeframe (3m/5m/15m) trend aligns (price > 20 EMA)
  3. CCI recovering from oversold zone (< -100) and turning upward
  4. PPO / MACD momentum improving (histogram expanding in bullish direction)
  5. ADX > 20 and +DI crossing above −DI, or strengthening in that direction
  6. Price reclaiming or bouncing from key structure (VWAP, prior day high/low, S/R)
  7. Higher low visible on execution timeframe — uptrend structure intact
  8. Volume expansion on the recovery candle or breakout bar
  9. Entry is NOT after a fully extended spike (check ATR %, room to target)
  10. Options chain passes: spread ≤ config max, OI ≥ config min, volume ≥ config min
PS− Bearish Checklist (mirror)
  1. Higher timeframe trend is bearish (price < 50 EMA, ADX rising)
  2. Execution timeframe trend aligns (price < 20 EMA)
  3. CCI declining from overbought zone (> +100) and turning downward
  4. PPO / MACD momentum weakening (histogram contracting or flipping negative)
  5. ADX > 20 and −DI crossing above +DI, or strengthening in that direction
  6. Price rejecting key structure (VWAP, prior day low, R zone)
  7. Lower high visible on execution timeframe — downtrend structure intact
  8. Volume expansion on the rejection candle or breakdown bar
  9. Entry is NOT after a fully extended drop
  10. Options chain passes same liquidity checks
Scoring → Action Map
Raw ScoreNormalized (×10)Action
< 7< 70SKIP
7–870–80WATCHLIST or ENTER at reduced size
8–980–90ENTER at standard size
9–1090–100ENTER at full size (still within hard limits)
Phase 4 — Contract Selection (Gate 4)
DTE:    preferred_dte_min (7) to preferred_dte_max (21)
        0-DTE only if allow_0dte: true in config (default false)

Delta:  delta_min (0.35) to delta_max (0.60) for standard directional trades
        Tighter end (0.45–0.65) for strong trend-continuation setups
        Day-trade / fast scalp: 0.25–0.45 only if spread/fill quality excellent

OI:     >= min_open_interest (config)
Volume: >= min_option_volume (config)
Spread: bid-ask spread as % of mid <= max_bid_ask_spread_percent (config)

When multiple contracts qualify, rank by:

  1. Tightest spread
  2. Highest open interest
  3. Delta closest to target band center
  4. Cleanest fill probability (avoid strikes with fragmented chain)

Reject if option premium is so low that one tick is > 5% of premium (lottery contract risk).

Phase 5 — Position Sizing (Gate 5)

Use fixed-fraction risk logic:

max_risk_dollars = account_equity × (max_risk_per_trade_percent / 100)
contracts_raw   = floor(max_risk_dollars / (premium_per_contract × 100))
contracts       = min(contracts_raw, max_contracts_derived_from_position_pct)

Adjustments:

  • CHOP regime: × chop_size_multiplier (0.5)
  • After N consecutive losses: × reduced_size_multiplier (0.5) once reduce_size_after_consecutive_losses threshold is hit
  • Score < 80: reduce size by 25%

If contracts < 1 after adjustments → SKIP (minimum size violates risk rules).

Also check:

  • max_open_positions not exceeded
  • max_positions_per_symbol not exceeded
  • Adding this position does not push portfolio_heat > max_portfolio_heat_percent
Phase 6 — Execution Plan
Order type:    LIMIT (always)
Limit price:   mid-price of bid-ask at evaluation time, or slight edge inside mid
Chase guard:   if current ask has moved > do_not_chase_percent (3%) above
               entry plan → cancel and re-evaluate
Fill timeout:  cancel_if_not_filled_seconds (45)

Never submit a market order for options. Never re-chase a missed fill blindly.

Phase 7 — Position Management and Exit Logic
Stop Definitions (pre-define before entry, never after)

Choose the tightest applicable stop:

  1. Underlying structure stop: invalidation level on chart (break of VWAP, EMA, or key S/R) → convert to equivalent premium loss estimate
  2. Premium stop: max_option_premium_loss_percent (35%) of entry premium
  3. Time stop: if no favorable movement within time_stop_minutes_intraday (45 min) → exit
  4. End-of-day: end_of_day_flatten_intraday: true → close all intraday positions before session end
Profit Management

Partial exit and runner logic per config:

At R×1.0 → sell scale_out_fractions[0] (50%) of position
At R×2.0 → sell scale_out_fractions[1] (30%) of position
Remaining (20%) = runner — move stop to break-even at R×1.0

Only allow runner in TRENDING_BULL or TRENDING_BEAR regime, never in CHOP.

Full Exit Triggers

Exit fully on any of:

  • Stop level hit
  • Hold confirmation indicators deteriorate (PPO cross against, DI reversal, CCI adverse divergence)
  • Broad market regime shifts against the trade mid-session
  • Event risk window approaches (earnings, macro release within avoid_macro_minutes_before)
  • Spread blows out (fill quality no longer viable)
  • End-of-day rule

Do not convert an options trade into an "investment."


4. Confidence Scoring (0–100)

Map the 10-point raw checklist score to 0–100 (multiply by 10), then apply qualitative adjustments:

FactorAdjustment
Strong multi-timeframe agreement (3 TFs aligned)+5
Clean S/R confluence at entry+5
IV context favorable (IV not historically extreme for long premium)+3
Recent symbol behavior cooperative (not whippy last 3 sessions)+3
Spread exceptionally tight (< 3%)+2
Event risk within 3 days−10
Higher and execution TF in direct conflict−15
ADX < 15 (very weak trend)−10
Spread > 6% of mid−8

Cap at 100. Below min_score_to_trade (70) → SKIP.


5. Event Risk Protocol

ConditionAction
Earnings within avoid_earnings_days_before (2) daysBlock new entries on that symbol
FOMC / CPI / NFP within avoid_macro_minutes_before (30) minBlock ALL new entries
Unscheduled high-impact headline (spreads blow out > 20%)Halt new entries, tighten existing stops
Already in position as event approachesReduce size, tighten stop, or exit per config

6. Daily Risk Controls and Halt Conditions

Check after every fill and before every new entry:

daily_realized_loss    >= max_daily_loss_percent (4%)    → HALT all new entries
consecutive_losses     >= max_consecutive_losses (3)     → HALT all new entries
portfolio_heat         >= max_portfolio_heat_percent (8%) → no new entries
slippage on last trade  > max_slippage_percent (5%)      → flag; raise fill threshold

Halt conditions are sticky for the session. Manual reset required.


7. Output Contract (Required for Every Evaluation)

Every symbol evaluated in a cycle must produce a structured decision object:

json
{
  "timestamp": "ISO-8601",
  "action": "ENTER | HOLD | EXIT | SKIP | WATCHLIST",
  "symbol": "AAPL",
  "direction": "bullish | bearish",
  "setup_type": "PS+ | PS-",
  "confidence_score": 82,
  "regime": "TRENDING_BULL | TRENDING_BEAR | CHOP | SHOCK",
  "thesis": "Brief narrative: what pattern, why now, what invalidates",
  "contract_candidate": {
    "expiration": "YYYY-MM-DD",
    "strike": 185.0,
    "type": "call | put",
    "dte": 14,
    "delta": 0.48,
    "open_interest": 4200,
    "volume": 850,
    "bid": 2.15,
    "ask": 2.25,
    "spread_pct": 4.5,
    "iv": 0.32
  },
  "entry_plan": {
    "limit_price": 2.20,
    "entry_window_minutes": 15
  },
  "stop_plan": {
    "underlying_invalidation": 182.50,
    "premium_stop_pct": 35,
    "time_stop_minutes": 45
  },
  "target_plan": {
    "r1_price": 3.08,
    "r2_price": 4.40,
    "runner_stop": "break_even_after_r1"
  },
  "position_size": {
    "contracts": 2,
    "total_premium_at_risk": 440,
    "pct_of_account": 0.44
  },
  "risk_checks_passed": true,
  "blockers": [],
  "journal_note": "Setup quality A. Clean bounce off VWAP+50EMA confluence. PPO improving. ADX 24 with +DI crossing. Room to prior day high ~4.5R. No events next 4 days."
}

If action == SKIP, still populate confidence_score, regime, blockers, and journal_note. Logged skips are required for strategy improvement.


8. Journaling Requirements

Log every evaluation, including skips. Required fields per log entry:

  • timestamp, symbol, direction, setup_type
  • market regime, higher TF bias, execution TF trigger used
  • confidence score and breakdown
  • contract selected (or why no contract qualified)
  • entry price (actual fill), stop logic, target logic
  • position size and account heat at entry
  • exit timestamp, exit price, P/L realized
  • exit reason (stop / target / time / indicator / regime / event)
  • slippage at entry and exit
  • rule violations, if any (log honestly)

Also log:

  • Skipped setups that scored ≥ 60 but failed a hard filter
  • Regime changes mid-session with brief rationale
  • Halt events with trigger condition and timestamp

9. Alpaca Integration (Paper)

Use scripts/alpaca.mjs for all broker interaction.

Required Environment Variables
bash
APCA_API_KEY_ID=<your_paper_key>
APCA_API_SECRET_KEY=<your_paper_secret>
APCA_API_BASE_URL=https://paper-api.alpaca.markets
Core Commands
bash
# Health check and account state
node skills/perfect-storm-options-trader/scripts/alpaca.mjs account

# Current open positions
node skills/perfect-storm-options-trader/scripts/alpaca.mjs positions

# Open orders
node skills/perfect-storm-options-trader/scripts/alpaca.mjs orders --status open

# Place a limit order (options use OCC symbol format)
node skills/perfect-storm-options-trader/scripts/alpaca.mjs order:place \
  --symbol AAPL250117C00185000 \
  --qty 2 \
  --side buy \
  --type limit \
  --time_in_force day \
  --limit_price 2.20

# Cancel an order
node skills/perfect-storm-options-trader/scripts/alpaca.mjs order:cancel --id <order_id>
Options Symbol Format (OCC)
AAPL  250117  C  00185000
ROOT  YYMMDD  P/C  8-digit strike (×1000, zero-padded)

Example: AAPL call, Jan 17 2025, $185 strike = AAPL250117C00185000

Show full SKILL.md (840 more words)Show less
Execution Checklist Before Any Order
✓ BASE_URL contains "paper-api" — never "api.alpaca.markets"
✓ account.status == "ACTIVE"
✓ account.trading_blocked == false
✓ Buying power sufficient for order
✓ Position limit not exceeded (check open positions count)
✓ Order is LIMIT type
✓ client_order_id set to trace order in journal

10. Behavior Rules

Must Do
  • Be selective. Trade less in poor conditions.
  • Respect all hard limits in risk_config.yaml without exception.
  • Prefer no trade over a low-quality trade.
  • Log clearly and honestly, including all skips.
  • Preserve capital first; profit is secondary.
  • Validate regime before every new entry, not just at session open.
Must Not Do
  • Invent signals or fill in missing data with assumptions
  • Ignore spread or liquidity issues
  • Exceed configured max risk per trade, daily loss, or portfolio heat
  • Average down losing positions
  • Revenge trade after a loss
  • Continue trading after safety halt conditions are triggered
  • Override risk_config.yaml rules without explicit human instruction
  • Connect to a live broker endpoint
  • Treat a stalled trade as a "hold" — stale convexity is expensive

11. Decision Priority Hierarchy

When rules or conditions conflict, resolve in this order:

  1. Safety — paper-only mode, data integrity, broker state
  2. Account protection — daily loss, heat, consecutive loss limits
  3. Event risk — earnings, macro windows
  4. Market regime — trade with the dominant environment
  5. Setup confluence — PS+ / PS− quality score
  6. Contract quality — liquidity, spread, delta, DTE
  7. Execution quality — limit price, slippage, fill speed
  8. Profit opportunity — only if all above are satisfied

12. IV Context Check (Best Practice Addition)

Before entering any long premium trade, evaluate whether implied volatility makes the option attractively priced:

IV Rank (IVR) = (current IV − 52w low IV) / (52w high IV − 52w low IV)

IVR < 30   → premium is relatively cheap → favorable for long premium
IVR 30–60  → neutral; ensure setup quality is strong (score ≥ 75)
IVR > 60   → premium is expensive → require score ≥ 85 or skip

A great chart pattern with expensive premium is still a risky trade. Log IV context in every trade journal entry.


13. Portfolio Correlation Guard

Do not allow correlated positions to compound hidden directional risk:

  • Maximum 2 positions in the same sector simultaneously
  • If SPY/QQQ direct position is open, all other positions are correlated → count them as a single directional block
  • Maximum directional exposure: max_portfolio_heat_percent / 2 per direction

When in doubt, the tighter constraint applies.


14. Walk-Forward Governance

Any change to thresholds, filters, or exit logic must:

  1. Be validated on out-of-sample data before use
  2. Pass walk-forward testing across at least 3 distinct market regimes
  3. Complete a paper-trading phase with live chain data before any threshold change is promoted to the active risk_config.yaml

No live-forward parameter changes mid-session.


15. Professional Seed Watchlist (20 Stock Tickers)

This is the prioritized starting universe for each scan cycle. Symbols are grouped by category and annotated with their primary trading characteristics. The agent must still apply all liquidity, spread, and event-risk filters — this list is a starting point, not a guaranteed tradeable set.

Rank and trim to max_symbols_ranked_per_cycle (default 10) each cycle based on relative volume, ATR%, and setup readiness score.

Mega-Cap Tech / AI (highest liquidity, tightest spreads)
TickerWhy It's On The List
NVDAHighest beta AI play; massive options volume; PS setups are clean and fast
AAPLDeepest options chain in the market; spreads excellent; smooth trend behavior
MSFTStrong institutional trend structure; reliable EMA respect; liquid chain
AMZNCloud + consumer composite; strong trending periods; liquid weeklies
METAHigh ATR%; clean breakout/breakdown patterns; active options market
GOOGLStable large-cap with periodic high-momentum setups; good chain depth
Semiconductor / High-Volatility Tech
TickerWhy It's On The List
AMDCorrelated to NVDA but more volatile; excellent PS setups during momentum runs
SMCIExtremely high ATR%; fast-moving; use reduced size; spreads can widen — filter strictly
SNOWGrowth-tech with high relative moves; strong trend-or-nothing behavior
Momentum / Crypto-Adjacent
TickerWhy It's On The List
TSLAHigh retail + institutional interest; large ATR%; frequent PS+ and PS− setups
COINCrypto-correlated; explosive directional moves; requires strict spread filter
PLTRStrong narrative-driven momentum; clean structure on daily and 30m charts
Financials
TickerWhy It's On The List
JPMLiquid large-cap; sector proxy; good for regime-aligned put setups during stress
GSHigh price / active options; strong directional bias during macro moves
BACRate-sensitive; use for macro-driven setups around FOMC; very liquid chain
Defensive / Non-Correlated (reduce correlation risk)
TickerWhy It's On The List
WMTLow beta; use for isolated PS setups when broad market is choppy
KOStable trend structure; good for low-volatility swing setups
PEPSimilar profile to KO; use to diversify away from tech concentration
Energy
TickerWhy It's On The List
XOMMacro/oil-driven; useful hedge when tech is choppy; active options chain
CVXSimilar to XOM; use for sector-divergence setups or energy trend trades
ETF Overlays (regime and hedge tools)
TickerWhy It's On The List
SPYPrimary regime proxy; also tradeable directly for broad-market PS setups
QQQTech-heavy regime proxy; use when NASDAQ is the dominant trend driver
IWMSmall-cap risk-on/risk-off signal; divergence from SPY/QQQ is informative

Note: SPY, QQQ, and IWM are listed in risk_config.yaml and AGENTS.md as core ETFs. They count toward the 20-symbol scan universe but are evaluated first as regime filters before being considered as trade candidates.

Watchlist Ranking Criteria (applied each scan cycle)

Score each symbol 0–3 on each factor, sum, and take the top max_symbols_ranked_per_cycle:

Factor0123
Relative volume vs 10-day avg< 0.8×0.8–1.2×1.2–2.0×> 2.0×
ATR% (intraday)< 1.5%1.5–2.5%2.5–4.0%> 4.0%
Setup confluence score (pre-screen)< 5050–6565–80> 80
Options chain quality (spread + OI)PoorAcceptableGoodExcellent

Ties broken by options chain quality, then alphabetically.

© LeoYeAI, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 3 other files in skills/perfect-storm-options-trader-v2 of LeoYeAI/openclaw-master-skills.

  • SKILL.md
  • AGENTS.md
  • _meta.json
  • risk_config_openclaw_best_practices.yaml

Open the folder on GitHubat commit e5199b5

Compare with similar skills

Perfect Storm Options Trader next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Perfect Storm Options Trader compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Perfect Storm Options Trader this skillLeoYeAI/openclaw-master-skills2.2k—~5.5kAutomated safety check: PassMIT
Tradingview MCPatilaahmettaner/tradingview-mcp5k—~1.3kAutomated safety check: PassMIT
Dr Manhattanguzus/dr-manhattan204—~2kAutomated safety check: PassApache-2.0
Agentic Trading DeskOft3r/agentic-trading-desk306—~5.1kAutomated safety check: PassMIT
Okx Cex Marketdex-original/okx-agent-trade-kit1101 repos~2.7kAutomated safety check: PassMIT
Polymarket Tennislivetennisapi/livetennisapi-mcp152—~3kAutomated safety check: PassMIT

Similar skills

  • Tradingview MCP

    atilaahmettaner/tradingview-mcp

    AI Trading Intelligence — live prices, 30+ technical indicators, backtesting (6 strategies), walk-forward overfitting detection, trade logs, equity curves, licensed news sentiment (Marketaux), and…

    5k GitHub stars~1.3k tokensUpdated yesterday
    Business, Finance & HRAuto-check passed
  • Dr Manhattan

    guzus/dr-manhattan

    Trade prediction markets (Polymarket, Kalshi, Opinion, Limitless, Predict.fun) using a unified CCXT-style API.

    204 GitHub stars~2k tokensUpdated 2 mo ago
    Business, Finance & HRAuto-check passed
  • Agentic Trading Desk

    Oft3r/agentic-trading-desk

    Personal trading desk for short-term technical analysis on stocks/ETFs via Robinhood MCP.

    306 GitHub stars~5.1k tokensUpdated 1 mo ago
    Business, Finance & HRAuto-check passed
  • Okx Cex Market

    dex-original/okx-agent-trade-kit

    A skill your agent uses when the user asks for: price of any asset, ticker, order book, candles, OHLCV, funding rate, open interest, OI change scanner, market screener (top movers, high-volume…

    110 GitHub starsUsed in 1 repo~2.7k tokens
    Business, Finance & HRAuto-check passed
  • Polymarket Tennis

    livetennisapi/livetennisapi-mcp

    Build observe-only Polymarket and Kalshi tennis market tooling on the polymarket-tennis Python package (MIT) plus the Live Tennis API free tier.

    152 GitHub stars~3k tokensUpdated 4 days ago
    Business, Finance & HRAuto-check passed
  • Trading Signals

    roman-rr/trading-skills

    Fetches live AI crypto trading signals with entry price, stop-loss, take-profit, leverage, confidence scores, and automated verification.

    119 GitHub stars~2.2k tokensUpdated 3 days ago
    Business, Finance & HRAuto-check passed

More from LeoYeAI/openclaw-master-skills

All 1,200 skills in this repo
  • DevOps Pipeline Management

    LeoYeAI/openclaw-master-skills

    Manages pipelines on a DevOps quality and efficiency platform through its OpenAPI: list workspaces and templates, create, update, run and cancel pipelines, and read run records.

    2.2k GitHub stars~4.2k tokensUpdated 2 mo ago
    Auto-check: notes
  • Feishu Document Collaboration

    LeoYeAI/openclaw-master-skills

    Patches OpenClaw's Feishu extension so an edited document triggers an isolated agent session that reads the doc and replies inline, turning it into a live chat space.

    2.2k GitHub stars~2k tokensUpdated 2 mo ago
    Auto-check passed
  • Files Memory System

    LeoYeAI/openclaw-master-skills

    Multi-context memory management system for OpenClaw agents with group-isolated storage, global shared memory, workspace organization, and group-specific skills isolation.

    2.2k GitHub stars~3.8k tokensUpdated 2 mo ago
    Auto-check passed
  • GEO-Claw AI Visibility Agent

    LeoYeAI/openclaw-master-skills

    Runs a brand's AI-search visibility work end to end: diagnosing how AI platforms represent it, repositioning it, producing AI-optimized content and monitoring ongoing mentions.

    2.2k GitHub stars~4.7k tokensUpdated 2 mo ago
    Auto-check passed
  • Google Workspace CLI

    LeoYeAI/openclaw-master-skills

    Installs and authenticates the gws CLI, then automates Gmail, Drive, Sheets, Calendar, Docs, Chat and Tasks with ready-made recipes, persona bundles and security audits.

    2.2k GitHub stars~2.6k tokensUpdated 2 mo ago
    Auto-check: notes
  • HealthFit Health Advisors

    LeoYeAI/openclaw-master-skills

    Runs four advisor roles, a fitness coach, nutritionist, data analyst and TCM practitioner, to build a health profile and track workouts, diet and wellness over time.

    2.2k GitHub stars~4.4k tokensUpdated 2 mo ago
    Auto-check passed

Questions about Perfect Storm Options Trader

What does Perfect Storm Options Trader do?

Autonomous but risk-bounded options trading agent spec for the "Perfect Storm" strategy (paper trading only). Perfect Storm Options Trader is an agent skill from LeoYeAI/openclaw-master-skills. Autonomous but risk-bounded options trading agent spec for the "Perfect Storm" strategy (paper trading only).

When should I use Perfect Storm Options Trader?

Perfect Storm Options Trader fits situations like: evaluating an OpenClaw-based discretionary options trader that scans an approved universe; grades PS+/PS- setups; selects liquid long call/put contracts; sizes conservatively.

How do I install Perfect Storm Options Trader in Claude Code?

Run `npx skills add LeoYeAI/openclaw-master-skills --skill perfect-storm-options-trader -a claude-code`. Or copy the skill folder (skills/perfect-storm-options-trader-v2 in LeoYeAI/openclaw-master-skills) into .claude/skills/perfect-storm-options-trader in your project. Claude Code loads it when a task matches its description.

How do I install Perfect Storm Options Trader in Codex?

Run `npx skills add LeoYeAI/openclaw-master-skills --skill perfect-storm-options-trader -a codex`. Or copy the skill folder (skills/perfect-storm-options-trader-v2 in LeoYeAI/openclaw-master-skills) into .agents/skills/perfect-storm-options-trader in your project. Codex loads it when a task matches its description.

Can I use Perfect Storm Options Trader in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add LeoYeAI/openclaw-master-skills --skill perfect-storm-options-trader -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/perfect-storm-options-trader, .gemini/skills/perfect-storm-options-trader, .github/skills/perfect-storm-options-trader and .opencode/skills/perfect-storm-options-trader in your project.

What does Perfect Storm Options Trader need to run?

Going by SKILL.md and its folder, Perfect Storm Options Trader needs the command-line tools its instructions call (node) and credentials named APCA_API_KEY_ID and APCA_API_SECRET_KEY.

Does Perfect Storm Options Trader access the network?

SKILL.md names 1 domain. In commands or code: paper-api.alpaca.markets; the agent is likely to contact it when it follows the instructions. This is read from the text; nothing was executed.

Is Perfect Storm Options Trader safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Perfect Storm Options Trader use?

Perfect Storm Options Trader is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Perfect Storm Options Trader use?

About 5.5k tokens (SKILL.md is roughly 22k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Perfect Storm Options Trader?

Skills that share tags, products or a category with Perfect Storm Options Trader: Tradingview MCP (atilaahmettaner/tradingview-mcp, 5k stars), Dr Manhattan (guzus/dr-manhattan, 204 stars), Agentic Trading Desk (Oft3r/agentic-trading-desk, 306 stars) and Okx Cex Market (dex-original/okx-agent-trade-kit, 110 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Perfect Storm Options Trader?

LeoYeAI (a GitHub user) maintains it in LeoYeAI/openclaw-master-skills, which has 2,161 GitHub stars. The repository holds 1,235 skills in this directory. The repository was last updated on July 20, 2026.

Source: LeoYeAI/openclaw-master-skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.