staskh/ib-account
Get account summary from Interactive Brokers including cash balance, buying power, and account value. Use when user asks about their account, balance, buying power, or available cash. Requires TWS or IB Gateway running locally.
npx skills add https://github.com/staskh/trading_skills --skill ib-account
Fetch account summary from Interactive Brokers.
TWS or IB Gateway must be running locally with API enabled:
IB_PORT env var — default port when --port is omitted (e.g. IB_PORT=4001 for a Gateway container). Precedence: --port flag > IB_PORT > built-in default. Set it in the shell or a .env file.Port fallback: If the configured port fails, automatically retry on the other port.
If the retry succeeds, save to memory which account type worked (live/paper) and reuse it for all IB skill calls in this and future sessions — until the user explicitly asks for the other account.
If both ports fail, ask the user to verify that TWS or IB Gateway is running with API access enabled.
> Note: If uv is not installed or pyproject.toml is not found, replace uv run python with python in all commands below.
uv run python scripts/account.py [--port PORT] [--account ACCOUNT_ID] [--all-accounts]
--port - IB port (default: 7497 for paper trading)--account - Specific account ID to fetch--all-accounts - Fetch summaries for all managed accountsDefault behavior (no flags): fetches the first managed account only.
Always use --all-accounts unless the user asks for a specific account.
Returns JSON with:
connected - Whether connection succeededaccounts - List of account summaries, each with account ID, net liquidation, cash, buying power, etc.If not connected, explain that TWS/Gateway needs to be running.
ib-asyncAll timestamps and time-based calculations must use the America/New_York timezone. All JSON output must include generated_at (NY time string) and data_delay fields.
Take staskh/ib-account from the repository into ~/.claude/skills for personal
use, or into .claude/skills inside a project.
The agent identifies a skill by the name field in its header. Two skills with the
same name cannot sit side by side — one of them will be ignored.