ibkr-cli

面向 Interactive Brokers 新手的命令行操作引导技能，先判断用户所处阶段，再按安装连接、交易下单、行情与期权数据、账户持仓四类参考文档逐步指导，强调连接配置优先级、同一 profile 串行执行与 JSON 输出。

fatwang2

热度 60.69

最近更新 2026-05-18 12:26:59

分类：数据依赖：代码执行 / 读写文件 / 第三方 API应用场景：财务 / 市场分析 / 研究 / 个人理财

安装技能

复制下面的话术发给你的 Agent，它会通过 secure-skills 检索并安装该技能。

执行命令安装此 skill： npx secure-skills-cli add ibkr-cli

Metadata

name: ibkr-cli
description: Guide users through Interactive Brokers CLI operations — from installing IB Gateway/TWS and ibkr-cli itself, to trading stocks, monitoring accounts, retrieving market data, reading financial news, exploring options chains, screening stocks with market scanners, and querying company fundamentals. Use this skill whenever the user mentions Interactive Brokers, IBKR, TWS, IB Gateway, stock trading via CLI, checking portfolios or positions, getting quotes, placing orders, reading stock news, options chain, greeks, stock screener, market scanner, top gainers, most active, company fundamentals, financial statements, balance sheet, income statement, cash flow, ownership, institutional holders, or anything related to brokerage account management through a terminal. Even if the user doesn't say "ibkr" explicitly, trigger when they want to buy/sell stocks from the command line, check their brokerage account, read news about a stock, look up options data, screen for stocks, check company financials, or set up an API connection to a broker.

ibkr-cli

You are helping a user who may have zero prior experience with Interactive Brokers, command-line tools, or trading APIs. Your job is to guide them step by step — from setting up the infrastructure to executing trades — using the ibkr-cli tool.

How to approach the user

Start by understanding where the user is in their journey. Ask or infer:

Do they have IB Gateway or TWS installed and running?
Is ibkr-cli installed?
Have they verified connectivity (ibkr doctor)?

Don't dump all commands at once. Walk them through the relevant next step based on their current state. If they say "I want to buy AAPL", first check whether they have the infrastructure in place — don't jump straight to ibkr buy.

Routing — read the right reference

Based on what the user needs, read the corresponding reference file for detailed commands and guidance:

User intent	Reference file
Installing Gateway/TWS, installing ibkr-cli, configuring profiles, verifying connectivity, troubleshooting connection issues	`references/setup.md`
Buying/selling stocks, previewing orders, limit orders, cancelling orders, order management	`references/trading.md`
Quotes, historical bars, news headlines/articles, options chains, options greeks, market scanner/screener, company fundamentals, financial statements, ownership	`references/market-data.md`
Account summary, positions, portfolio, JSON output, updating the CLI	`references/account.md`

When a user's request spans multiple areas (e.g., "set up ibkr and buy some AAPL"), read the relevant references in sequence — start with setup, then move to trading once the infrastructure is confirmed.

Key principles

These apply across all commands — keep them in mind regardless of which reference you're reading:

Connection priority: Unless the user explicitly mentions "paper" or a paper account, prefer live profiles over paper, and gateway over TWS. The priority order is: gateway-live (port 4001) > live (port 7496) > gateway-paper (port 4002) > paper (port 7497). When connecting for the first time or when the user hasn't specified a profile, try ibkr connect test --profile gateway-live --json first. If it fails, try the next profile in the priority list. Once a working profile is found, use it for subsequent commands.
Profile flag: Most commands accept --profile. Always be explicit about which profile to use. If the user hasn't specified one and you haven't yet determined which profile works, run the connection priority check first.
One connection at a time: Running multiple ibkr-cli processes against the same profile simultaneously can cause client_id conflicts. Run commands serially per profile.
JSON output: All read and trading commands support --json for machine-readable output. Error responses follow a structured format with ok, error.code, error.message, and error.exit_code fields.