Ibkr Options Assistant
ReviewAudited by ClawScan on May 14, 2026.
Overview
This appears to be a coherent IBKR trading assistant that clearly discloses broker access and opt-in order execution, but users should treat it as high-impact because it can access account data and can submit real trades if enabled.
Install only if you are comfortable letting the agent access your IBKR-connected market and account data. Start with paper or read-only Gateway settings, keep trading disabled unless you intentionally want live order placement, and review any command that would use `trade.py` before allowing it to run.
Findings (4)
Artifact-based informational review of SKILL.md, metadata, install specs, static scan signals, and capability signals. ClawScan does not execute the skill or run runtime probes.
General stock or portfolio questions may cause the agent to query the user's IBKR/Gateway setup even when the user did not explicitly request IBKR.
The skill intentionally gives broad tool-selection instructions for financial questions, causing the agent to prefer IBKR-connected scripts over other sources.
Fire **even if the user doesn't mention IBKR** ... For stock prices, always use `market_quote.py`. **Never** web-search a stock price
Use this skill only when you want IBKR-backed answers, and explicitly tell the agent not to access IBKR for unrelated financial questions.
If trading mode is enabled and a confirmed command is run, mistakes in symbols, quantities, expiries, or order type could place or cancel real broker orders.
The artifacts disclose a powerful order-placement CLI with real financial impact, while also documenting explicit safety gates and guardrails.
`trade.py` — opt-in order execution for stocks, single-leg options, multi-leg combos (BAG/ComboLeg), futures, and FX. **Dual-gate safety**: refuses to place orders unless both `IBKR_TRADING_ENABLED=1` is set AND `--confirm-trade` is passed.
Keep `IBKR_TRADING_ENABLED` unset by default, use paper or read-only mode for testing, review dry-run previews, and only enable live trading for exact user-approved orders.
The agent can read sensitive portfolio, position, and P&L information from the IBKR account available to the local Gateway session.
The skill relies on the user's logged-in IBKR Gateway session and configuration, which grants access to brokerage account data and optional trading authority.
Read IBKR config from env vars (`IBKR_HOST`, `IBKR_PORT`, `IBKR_CLIENT_ID_BASE`, `IBKR_MARKET_DATA_TYPE`) ... only `trade.py` can [place orders], and only when both `IBKR_TRADING_ENABLED=1` and `--confirm-trade` are present
Use a paper account or read-only IBKR sub-user where possible, keep Gateway localhost-only, and avoid enabling trading permissions except when needed.
Local files may contain trading history or rules that influence future analysis, and their contents may be brought into the agent's context.
The documentation states that the toolkit reads and writes local persistent trading journals, alert rules, and Flex statement files under the user's home directory.
读写 `~/.ibkr_wheel_journal.json`、`~/.ibkr_alerts.yaml`、`~/.ibkr_flex/*.csv`
Protect these files with normal local file permissions, review imported Flex/alert files before use, and do not let untrusted parties modify them.