Options Strategies

Compare option candidates and score components, with funding, expiry and assignment risks.

Release preview: the matching backend has not been verified in production. Do not claim this structured workflow is live; unsupported servers must fail closed. Retained legacy runner commands remain compatible.

Before running

Read access and evidence rules. Python 3.9+ is the only runtime dependency; no separate CLI or sibling Skill installation is required. Resolve <skill-dir> to the directory containing this file.

Ask for ticker, strategy preference and expiry if relevant. Use an explicit expiry when requested. Compare only returned candidates; a missing cash requirement or multiplier is unknown, not zero. Explain assignment, downside and event risk. Never infer a live executable fill or a complete multi-leg strategy from a single-leg candidate list. For the option-strategies.v1 rollout, add --workflow --lang zh (or en). A public, key-free preflight checks server support before the allowance-consuming request. Preserve resultId, scorerSourceRevision, partial status, missingData and riskFlags. Group candidates by strategy, never rank different strategy scores together or call them profit probabilities. Show reference capital, expiry breakeven and downside from economics when available; missing economics is unknown. The multiplier is a market-configuration assumption, not a verified deliverable. The USD $1-per-side fee is an illustrative assumption, not a broker quote or an all-in cost; fees and slippage are not included in the score. Short calls do not assume the user owns shares, and uncovered loss is unlimited. Do not present unknown quote times as live or replace them with generatedAt. Present data limitations in the user's language. This opt-in format requires the matching backend deployment; the default legacy command remains available.

Run

python3 "<skill-dir>/scripts/run.py" options NVDA --strategy all --limit 3 --confirm-usage --workflow --lang en

This example contains --confirm-usage. Use that flag only after the user has approved allowance consumption. Require ALPHAGBM_API_KEY in the environment, never in a prompt.