plugins/ibkr-trading/skills/ibkr-trading/SKILL.md
Comprehensive Interactive Brokers algotrading knowledge base covering TWS API 10.45 architecture, ib_async event-driven programming, market data subscriptions, order execution with bracket orders, historical data with pacing rules, reconnection resilience, IBC automation, and Windows production deployment. TRIGGER WHEN: building, implementing, writing, coding, creating, optimizing, or debugging IB trading systems with Python. DO NOT TRIGGER WHEN: the task is outside the specific scope of this component.
npx skillsauth add acaprino/alfio-claude-plugins ibkr-tradingInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Knowledge base for building production-grade algorithmic trading systems with Interactive Brokers TWS API and ib_async in Python.
NaN/0.0/unit/tick traps that silently mis-size or rejectisConnected(), reconnect supervisor silently stopped)For 80% of use cases, start with:
pip install ib_async (asyncio-native successor to ib_insync)reqRealTimeBars for live 5-sec bars with local aggregationtransmit=False patterndisconnectedEvent + exponential backoff reconnectionThen harden incrementally:
reqExecutions() reconciliationreqPositions()venue-boundary-failure-modes.md (async rejection ingress, tick conformance, FX-as-CFD routing, NaN-safe sizing)isConnected() gates with active probes (reqCurrentTimeAsync + timeout), defensive disconnect() after failed attempts, escalation on supervisor silence (reconnection-resilience.md)eventkit/ib_async std loggers to your sink (event-driven-data.md)order-execution.md)event-driven-data.md)tws-api-architecture.md -- TWS API 10.45, Gateway vs TWS, Client Portal, ib_async setup, clientId strategy, official docsevent-driven-data.md -- reqMktData, reqRealTimeBars, reqTickByTickData, keepUpToDate, OHLCV construction, pacing violations, historical data, session-reopen stub bars (off-grid drop + top-up, replay chronology guards), eventkit listener contracts (swallowed exceptions, handler arity, std-logger routing), dedup TTL resonance with daily market eventsorder-execution.md -- order types, bracket orders (GTC children + residual-child reaper, phantom transient Cancelled), lifecycle states, execDetails monitoring, race conditions, error codes, compliance-201 non-overridability, whatIf probing, per-clientId order visibilityreconnection-resilience.md -- daily reset, IBC automation, reconnect patterns, the isConnected() zombie blind spot (active liveness probes, defensive disconnect, decorrelated recovery layers), Gateway-log forensics, multi-client snapshot hygiene, the silent-failure review signature, heartbeat, Windows deployment, community resourcesvenue-boundary-failure-modes.md -- the silent-failure layer: async rejection ingress (errorEvent -> lifecycle), price/tick conformance (110/135, minTick from ContractDetails), FX-as-CFD routing for retail EU entities (201/200/2127/366), CFD venue params vs spot (minTick, minSize-is-precision), data-contract vs order-contract split, and NaN-safe sizing with canonical lot units and conversion-rate fallback| Decision | Default | Upgrade When | |----------|---------|-------------| | Connection target | IB Gateway | Need visual debugging -- TWS | | Python library | ib_async | Need same-day new features -- ibapi | | Live data | reqRealTimeBars (5s bars) | Need tick precision -- reqTickByTickData (max 3) | | Chart data | keepUpToDate | Network-sensitive env -- reqRealTimeBars + aggregation | | Historical data | reqHistoricalData + throttle | Bulk backfill -- chunked requests with Semaphore | | Order type | Bracket (parent+TP+SL) | Need trailing: TRAIL. Need algo: Adaptive | | Lifecycle mgmt | IBC + Task Scheduler | Docker available -- gnzsnz/ib-gateway-docker | | whatToShow | TRADES | Forex: MIDPOINT. Backtesting: ADJUSTED_LAST |
development
Quality gates for multi-reviewer code review pipelines: adversarial verification panel, completeness critic, reviewer pipeline conventions, and the context sharing pattern for parallel reviewers. TRIGGER WHEN: running /senior-review:team-review quality gates; running /senior-review:code-review Steps 4b/4c (adversarial verification and completeness check); consolidating or deduplicating findings from multiple parallel reviewers. DO NOT TRIGGER WHEN: single-reviewer style review without a consolidation phase, or generic team coordination (the upstream agent-teams skills cover that).
development
Knowledge base for pure-architecture decisions on when to unify duplicated logic into a shared abstraction versus leave it duplicated. Covers the canonical theory (Rule of Three, DRY/WET/AHA, Wrong Abstraction, Locality of Behaviour, Bounded Contexts, Tidy First options framing, CUPID vs SOLID), 12 essential-duplication patterns that justify unification, 12 wrong-abstraction patterns that justify inlining or decomposition, an operational decision frame, and a verified reading list. TRIGGER WHEN: the user is making an architectural decision about whether to centralize, extract, or remove a layer; reviewing an abstraction for premature generality; auditing scattered cross-cutting concerns; spawned by the abstraction-architect agent during /abstraction-architect:audit or as the Abstraction dimension of /senior-review:team-review or /senior-review:code-review; the user asks "should I extract this into a service" / "is this DRY enough" / "is this wrong abstraction". DO NOT TRIGGER WHEN: the task is code formatting and readability cleanup (use clean-code:clean-code), Python-specific refactoring with metrics (use python-development:python-refactor), generic dead-code removal (use senior-review:cleanup-dead-code), security review (use senior-review:security-auditor), or pure pattern-consistency review without an architecture lens (use senior-review:code-auditor).
development
Unified web frontend knowledge base covering CSS architecture, UX psychology, UI components, distinctive aesthetics, and interface design generation. TRIGGER WHEN: working on web styling, design systems, component decisions, responsive strategy, distinctive frontend aesthetics, or exploring multiple interface designs. DO NOT TRIGGER WHEN: the task is purely backend or unrelated to web frontend.
development
Stripe payments knowledge base - API patterns, checkout optimization, subscription lifecycle, pricing strategies, webhook reliability, Firebase integration, cost analysis, and revenue modeling. Loaded by stripe-integrator and revenue-optimizer agents; also consumable directly when the user asks for Stripe-specific patterns without needing an agent. TRIGGER WHEN: working with Stripe API (Payment Intents, Customers, Subscriptions, Checkout Sessions, Connect, webhooks, tax, usage-based billing), pricing strategy, or revenue modeling. DO NOT TRIGGER WHEN: payment work is non-Stripe (PayPal, Square, crypto) or the task is generic e-commerce unrelated to payments.