// Generate options-only execution strategies (short straddle, iron condor). Backtest mode is intentionally disabled. Live mode uses optionsmultiorder + per-leg SL.
| name | algo-options |
| description | Generate options-only execution strategies (short straddle, iron condor). Backtest mode is intentionally disabled. Live mode uses optionsmultiorder + per-leg SL. |
| argument-hint | [template] [underlying] [expiry-date] |
| allowed-tools | Read, Write, Edit, Bash, Glob, Grep |
Create an options execution strategy.
Parse $ARGUMENTS as: template underlying expiry-date
$0 = template (short-straddle, iron-condor)$1 = underlying (e.g. NIFTY, BANKNIFTY). Default: NIFTY$2 = expiry date in DDMMMYY format (e.g. 30DEC25). REQUIRED - no auto-roll. Ask if not given.If no arguments, ask the user which template.
algo-expert/rules/options-execution.md, unified-strategy-pattern.md, and self-hosted-strategies.md.--mode backtest is passed). They use OpenAlgo's UI analyzer toggle for sandbox testing instead.09:20)15:15)1.30 for 30% premium SL)algo-expert/rules/assets/<template>/strategy.py.strategies/<template>_<underlying>/ and copy + customize.UNDERLYING, UNDERLYING_EXCH, EXPIRY_DATELOTS, LOT_SIZE (NIFTY=65, BANKNIFTY=30, FINNIFTY=60 per Apr 2026 SEBI - see lot-sizes.md)ENTRY_TIME, EXIT_TIME as dtime(H, M)SL_MULTIPLIER for short straddleOTM_NEAR, OTM_FAR for iron condor/python: requires apscheduler and pytz packages installed (covered by setup)EXPIRY_DATE before each cycle - the file does NOT auto-rollMODE=live in upload form parameters; OpenAlgo UI's analyzer toggle decides sandbox vs real| Template | Description |
|---|---|
short-straddle | Sell ATM CE + ATM PE at scheduled time, per-leg broker SL at SL_MULTIPLIER * premium, flat at EXIT_TIME |
iron-condor | OTM_NEAR short CE/PE + OTM_FAR long CE/PE wings, monitor and flat at EXIT_TIME |
The generated file checks for --mode backtest and exits:
Options backtesting is not supported in this skill pack.
Options pricing depends on volatility surfaces, time decay, and OI dynamics
that intraday OHLCV backtests don't capture well.
Use --mode live (with OpenAlgo's UI analyzer toggle for sandbox).
If the user wants to dry-run, they should:
/analyzer UI)--mode live - orders go to the sandbox, not the brokerEXPIRY_DATE = "30DEC25" is hardcoded; user must update weekly)OpenAlgo execution expert. Auto-loaded knowledge base for building algorithmic trading strategies that toggle between VectorBT backtest and OpenAlgo live execution. Triggers when user mentions OpenAlgo trading strategies, dual-mode strategies, /python self-hosted strategies, options execution (short straddle, iron condor), portfolio risk caps, or live execution with stop loss / target / trailing stop / risk management.
Validate a generated strategy and produce an upload guide for OpenAlgo's /python self-hosted strategy page. Confirms env-var reads, SIGTERM, stdout-only logging.
Run multiple strategies under one supervisor with portfolio-level risk caps (portfolio SL/TP, daily PnL limits, max concurrent positions). YAML-driven.
Verify a strategy's SL / TP / trailing stop / portfolio caps fire correctly. Uses OpenAlgo sandbox + synthetic price moves. Run this before going live.
Set up the Python environment for OpenAlgo execution skills - venv, openalgo[indicators], vectorbt, talib, scikit-learn, xgboost. Scaffolds strategies/ folder and .env.
Generate a single-file dual-mode trading strategy. Asks for indicator library and execution type. The same file runs `--mode backtest` (VectorBT) and `--mode live` (OpenAlgo). Upload-ready for OpenAlgo /python self-hosted.