/exchange-connectivity
Guide the design and management of trading venue connectivity and market data infrastructure. Owns the FIX session layer (logon, heartbeats, sequence number gaps, resend and gap recovery, disconnects). Use when building or troubleshooting FIX sessions for order routing or drop
$ npx -y skills add JoelLewis/finance_skills --skill exchange-connectivity --agent claude-codeHow it fires
How this skill gets triggered: by you, by Claude, or both.
- Fires itselfAuto-invocation. Claude auto-loads it when your prompt matches the work.Auto-invocation is when the right skill fires by itself at the right moment, driven by a FLOW.md router and a hook, instead of you invoking it by name. It is the difference between a skill being installed and a skill actually getting used.Read the full definition →
- You can call itInvoke it directly when you want it.
- Slash command
/exchange-connectivity
Context preview
The summary Claude sees to decide when to auto-load this skill.
Guide the design and management of trading venue connectivity and market data infrastructure. Owns the FIX session layer (logon, heartbeats, sequence number gaps, resend and gap recovery, disconnects). Use when building or troubleshooting FIX sessions for order routing or drop
SKILL.md
exchange-connectivity.SKILL.mdname: exchange-connectivity
description: "Guide the design and management of trading venue connectivity and market data infrastructure. Owns the FIX session layer (logon, heartbeats, sequence number gaps, resend and gap recovery, disconnects). Use when building or troubleshooting FIX sessions for order routing or drop copy, integrating exchange protocols like OUCH, ITCH, PITCH, or Pillar, designing market data feed architecture (consolidated SIP vs direct feeds), handling trading halts or circuit breakers or LULD bands, planning co-location or failover and disaster recovery for exchange connectivity, implementing Rule 15c3-5 market access controls, or mapping symbology across venues and data sources. For order state machines and execution-report handling see order-lifecycle."
Exchange Connectivity
Core Concepts
Venue Connectivity Architecture
Trading venues expose electronic interfaces through which broker-dealers, market makers, and institutional participants submit orders and receive execution reports. The connectivity architecture between a firm and its execution venues is a foundational component of trading infrastructure.
**Direct Market Access (DMA):** DMA allows a firm to send orders directly to an exchange's matching engine without intermediation by another broker's order management system. The firm maintains its own FIX session (or proprietary protocol connection) with the exchange and is responsible for pre-trade risk controls. DMA is used by broker-dealers with exchange memberships and by proprietary trading firms.
**Sponsored Access:** In a sponsored access arrangement, a non-member firm routes orders to an exchange through a sponsoring broker-dealer's market participant identifier (MPID). The sponsoring broker is responsible for pre-trade risk controls under SEC Rule 15c3-5 (the Market Access Rule). Sponsored access may be "filtered" (orders pass through the sponsor's risk checks before reaching the exchange) or "unfiltered" (orders bypass the sponsor's systems and go directly to the exchange, with the sponsor relying on exchange-level risk controls). The SEC effectively prohibited unfiltered sponsored access through Rule 15c3-5, which requires the broker-dealer providing market access to implement risk management controls and supervisory procedures that are reasonably designed to prevent the entry of erroneous orders.
**FIX Protocol Connectivity:** The Financial Information eXchange (FIX) protocol is the dominant standard for order routing and execution reporting in equities, options, fixed income, and foreign exchange markets. FIX is a tag-value message format (e.g., Tag 35=D for a New Order Single, Tag 35=8 for an Execution Report). Most U.S. equity exchanges accept FIX for order entry, and FIX is the standard interface for broker-to-broker and broker-to-buy-side connectivity. FIX versions in common use include FIX 4.2 (widely supported, still in use at many venues), FIX 4.4 (added support for multi-leg instruments, allocation instructions), and FIX 5.0/FIXT 1.1 (separated transport and application layers).
**Proprietary Exchange Protocols:** Several exchanges offer proprietary binary protocols that provide lower latency than FIX due to more compact message encoding and reduced parsing overhead:
- **OUCH** — Nasdaq's order entry protocol. Binary format, supports order submission, cancellation, and replacement. Commonly used by high-frequency and low-latency participants on Nasdaq and its affiliated venues.
- **ITCH** — Nasdaq's market data dissemination protocol. Provides a full order-by-order (Level 3) view of the Nasdaq order book, including every order add, modify, cancel, and execute event. ITCH is the basis for Nasdaq's TotalView data product.
- **PITCH** — Cboe's market data protocol for the BZX, BYX, EDGX, and EDGA exchanges. Like ITCH, PITCH provides order-by-order depth-of-book data.
- **Pillar** — NYSE's integrated trading technology platform, supporting both order entry and market data across NYSE, NYSE Arca, NYSE American, and NYSE National. Pillar uses binary protocols for gateway connectivity.
- **BOE (Binary Order Entry)** — Cboe's proprietary order entry protocol, offering lower-latency order submission than FIX on Cboe equity exchanges.
**Co-location and Proximity Hosting:** Exchanges offer co-location services that allow firms to place their trading servers in the same data center as the exchange's matching engine. Co-location minimizes network latency (measured in microseconds) by reducing the physical distance between the firm's server and the exchange. Proximity hosting refers to placing servers in a data center near (but not inside) the exchange's facility, offering somewhat higher latency than co-location but often at lower cost. Major U.S. exchange data centers include the NYSE data center in Mahwah, New Jersey and the Nasdaq data center in Carteret, New Jersey.
**Connectivity Providers and Extranets:** Financial extranets are private networks that connect market participants to multiple exchanges and trading venues through a single physical connection. Major extranets include:
- **TNS (Transaction Network Services)** — Provides managed connectivity to global exchanges and trading venues.
- **IPC (now part of Atos)** — Operates the Connexus Cloud financial extranet connecting trading firms to exchanges, market data providers, and service bureaus.
- **BSO (Boldon Smart Operations)** — Offers low-latency network infrastructure for financial markets.
- **Options Technology** — Provides connectivity and managed infrastructure for trading firms.
Extranets reduce the operational burden of maintaining individual point-to-point connections to each venue but introduce a shared network dependency.
**Redundancy and Failover:** Production exchange connectivity must include redundant paths. Standard practice includes: primary and backup FIX sessions to each venue (typically on separate physical network paths), primary and secondary ne
Read more
name: exchange-connectivity description: "Guide the design and management of trading venue connectivity and market data infrastructure. Owns the FIX session layer (logon, heartbeats, sequence number gaps, resend and gap recovery, disconnects). Use when building or troubleshooting FIX sessions for order routing or drop copy, integrating exchange protocols like OUCH, ITCH, PITCH, or Pillar, designing market data feed architecture (consolidated SIP vs direct feeds), handling trading halts or circuit breakers or LULD bands, planning co-location or failover and disaster recovery for exchange connectivity, implementing Rule 15c3-5 market access controls, or mapping symbology across venues and data sources. For order state machines and execution-report handling see order-lifecycle."
Exchange Connectivity
Core Concepts
Venue Connectivity Architecture
Trading venues expose electronic interfaces through which broker-dealers, market makers, and institutional participants submit orders and receive execution reports. The connectivity architecture between a firm and its execution venues is a foundational component of trading infrastructure.
**Direct Market Access (DMA):** DMA allows a firm to send orders directly to an exchange's matching engine without intermediation by another broker's order management system. The firm maintains its own FIX session (or proprietary protocol connection) with the exchange and is responsible for pre-trade risk controls. DMA is used by broker-dealers with exchange memberships and by proprietary trading firms.
**Sponsored Access:** In a sponsored access arrangement, a non-member firm routes orders to an exchange through a sponsoring broker-dealer's market participant identifier (MPID). The sponsoring broker is responsible for pre-trade risk controls under SEC Rule 15c3-5 (the Market Access Rule). Sponsored access may be "filtered" (orders pass through the sponsor's risk checks before reaching the exchange) or "unfiltered" (orders bypass the sponsor's systems and go directly to the exchange, with the sponsor relying on exchange-level risk controls). The SEC effectively prohibited unfiltered sponsored access through Rule 15c3-5, which requires the broker-dealer providing market access to implement risk management controls and supervisory procedures that are reasonably designed to prevent the entry of erroneous orders.
**FIX Protocol Connectivity:** The Financial Information eXchange (FIX) protocol is the dominant standard for order routing and execution reporting in equities, options, fixed income, and foreign exchange markets. FIX is a tag-value message format (e.g., Tag 35=D for a New Order Single, Tag 35=8 for an Execution Report). Most U.S. equity exchanges accept FIX for order entry, and FIX is the standard interface for broker-to-broker and broker-to-buy-side connectivity. FIX versions in common use include FIX 4.2 (widely supported, still in use at many venues), FIX 4.4 (added support for multi-leg instruments, allocation instructions), and FIX 5.0/FIXT 1.1 (separated transport and application layers).
**Proprietary Exchange Protocols:** Several exchanges offer proprietary binary protocols that provide lower latency than FIX due to more compact message encoding and reduced parsing overhead:
- **OUCH** — Nasdaq's order entry protocol. Binary format, supports order submission, cancellation, and replacement. Commonly used by high-frequency and low-latency participants on Nasdaq and its affiliated venues.
- **ITCH** — Nasdaq's market data dissemination protocol. Provides a full order-by-order (Level 3) view of the Nasdaq order book, including every order add, modify, cancel, and execute event. ITCH is the basis for Nasdaq's TotalView data product.
- **PITCH** — Cboe's market data protocol for the BZX, BYX, EDGX, and EDGA exchanges. Like ITCH, PITCH provides order-by-order depth-of-book data.
- **Pillar** — NYSE's integrated trading technology platform, supporting both order entry and market data across NYSE, NYSE Arca, NYSE American, and NYSE National. Pillar uses binary protocols for gateway connectivity.
- **BOE (Binary Order Entry)** — Cboe's proprietary order entry protocol, offering lower-latency order submission than FIX on Cboe equity exchanges.
**Co-location and Proximity Hosting:** Exchanges offer co-location services that allow firms to place their trading servers in the same data center as the exchange's matching engine. Co-location minimizes network latency (measured in microseconds) by reducing the physical distance between the firm's server and the exchange. Proximity hosting refers to placing servers in a data center near (but not inside) the exchange's facility, offering somewhat higher latency than co-location but often at lower cost. Major U.S. exchange data centers include the NYSE data center in Mahwah, New Jersey and the Nasdaq data center in Carteret, New Jersey.
**Connectivity Providers and Extranets:** Financial extranets are private networks that connect market participants to multiple exchanges and trading venues through a single physical connection. Major extranets include:
- **TNS (Transaction Network Services)** — Provides managed connectivity to global exchanges and trading venues.
- **IPC (now part of Atos)** — Operates the Connexus Cloud financial extranet connecting trading firms to exchanges, market data providers, and service bureaus.
- **BSO (Boldon Smart Operations)** — Offers low-latency network infrastructure for financial markets.
- **Options Technology** — Provides connectivity and managed infrastructure for trading firms.
Extranets reduce the operational burden of maintaining individual point-to-point connections to each venue but introduce a shared network dependency.
**Redundancy and Failover:** Production exchange connectivity must include redundant paths. Standard practice includes: primary and backup FIX sessions to each venue (typically on separate physical network paths), primary and secondary ne
A collection of Claude Code skill plugins for financial services. 91 skills across 7 domain plugins teach Claude investment management, regulatory compliance, advisory workflows, trading operations, and more — so it can assist with finance questions, build
Other skills on finance-skills.
- /advisor-dashboards
Design, build, and optimize dashboards for RIA practice management with AUM tracking, revenue analytics, and KPI frameworks. Use when the user asks about tracking firm-level metrics, monitoring advisor productivity, measuring organic growth rate, analyzing client retention and
Open skill - /client-onboarding
Design and implement end-to-end client onboarding workflows from prospect intake through funded account, covering KYC verification, document collection, e-signature, and custodian submission. Use when the user asks about building a digital onboarding flow, integrating identity
Open skill - /client-reporting-delivery
Design, generate, and deliver client performance reports across all channels, covering quarterly reports, tax reporting, portal integration, and compliance review. Use when the user asks about building or redesigning report templates, choosing what to include in quarterly or
Open skill - /client-review-prep
Prepare advisors for client review meetings by assembling context packages, performance summaries, drift analysis, talking points, and meeting agendas. Use when the user asks about preparing for a client review, building a pre-meeting checklist, generating talking points for an
Open skill - /crm-client-lifecycle
Design and optimize CRM systems and client lifecycle workflows for advisory firms, covering segmentation, household management, service tiers, and retention analytics. Use when the user asks about client segmentation models, building household structures, defining service tier
Open skill - /fee-billing
Build and manage advisory fee billing operations from fee schedule design through calculation, collection, revenue recognition, and compliance disclosure. Use when the user asks about tiered or breakpoint fee schedules, billing cycle configuration, AUM valuation for billing,
Open skill

