venue-expert
Skill40 starsChanged 8 months agoApache-2.0View on GitHub
This skill should be used when the user asks about "market microstructure", "exchange mechanics", "order book", "auction", "NBBO", "Reg NMS", "trading venue", "halt", "LULD", "tick size", "maker-taker", "price-time priority", "SIP", "direct feed", "TRF", "wholesaler", "PFOF", "best execution", "trade-through", "ISO", "opening cross", "closing cross", "NOII", "ITCH", "OUCH", or mentions specific exchanges (Nasdaq, NYSE, CME, Binance, SHFE, DCE, CZCE, CFFEX, INE, etc.).
We split this skill into the rules it gives an agent
4 rules. About 0 are common, 3 are distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈3
Distinctive · estimate
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 89
Start at the most specific applicable level.
- Distinctive: line 102
When debugging trading system issues:
- Distinctive: line 105
Feed issues: - Check sequence gaps, timestamp alignment, halt state handling
- Distinctive: line 106
Auction issues: - Verify order type eligibility, cutoff times, NOII parsing
≈ “Common” is an estimate: at least 1 in 5 of the 308,232 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Venue Expert
Hierarchical microstructure knowledge base for trading venues. Primary use cases: research, debugging, and building trading systems.
Purpose
Provide deep venue-specific expertise for:
- Quants building execution models and alpha signals
- Developers implementing feed handlers and order entry
- Researchers studying market microstructure
- Debuggers diagnosing trading system issues
Hierarchy Model
Knowledge is organized in an inheritance hierarchy:
Asset Class (equity, futures, crypto, fx)
|
v
Geography (amer, emea, apac)
|
v
Exchange (nasdaq, nyse, cme, binance)Each level inherits concepts from its parent. Exchange-level files assume familiarity with geo-level and asset-class-level concepts.
Current Coverage
Implemented paths:
equity/- Equity market fundamentalsequity/amer/- US equity market structure (Reg NMS, NBBO, SIP, TRF)equity/amer/nasdaq/- Nasdaq-specific mechanics (ITCH, OUCH, crosses)futures/- Futures market fundamentalsfutures/apac/- APAC futures overviewfutures/apac/china/- Chinese futures (CTP, 5 exchanges, regulatory)futures/apac/china/shfe/- SHFE metals/energyfutures/apac/china/dce/- DCE ferrous/agriculturalfutures/apac/china/czce/- CZCE agricultural/chemicalsfutures/apac/china/cffex/- CFFEX financial futuresfutures/apac/china/ine/- INE internationalized products
Planned paths:
equity/amer/nyse/- NYSE mechanicsequity/emea/lse/- London Stock Exchangefutures/amer/cme/- CME Groupcrypto/binance/- Binance exchange
Navigation
Context Detection
Route to appropriate depth based on query specificity:
| Query Pattern | Target File |
| Generic equity concepts | equity/equity.md |
| US market structure, Reg NMS, NBBO | equity/amer/equity_amer.md |
| Nasdaq-specific (ITCH, NOII, crosses) | equity/amer/nasdaq/nasdaq.md |
| Generic futures concepts | futures/futures.md |
| APAC futures overview | futures/apac/futures_apac.md |
| Chinese futures, CTP, 夜盘 | futures/apac/china/futures_china.md |
| SHFE-specific (metals, CloseToday) | futures/apac/china/shfe/shfe.md |
| DCE-specific (iron ore, stop orders) | futures/apac/china/dce/dce.md |
| CZCE-specific (3-digit years, UpdateMillisec=0) | futures/apac/china/czce/czce.md |
| CFFEX-specific (index futures, restrictions) | futures/apac/china/cffex/cffex.md |
| INE-specific (crude oil, foreign access) | futures/apac/china/ine/ine.md |
Drill-Down Behavior
Start at the most specific applicable level. Reference parent concepts without repeating them. For example, when discussing Nasdaq auctions, assume familiarity with US equity auction concepts from equity_amer.md.
Reference Organization
Each level has a references/ directory with subdirectories:
regulatory/- Rules, regulations, compliance guidancespecs/- Protocol specifications, data formats
Reference files provide deep detail on specific topics. Load them when queries require specification-level precision.
Debugging Checklist
When debugging trading system issues:
US Equity
- Feed issues - Check sequence gaps, timestamp alignment, halt state handling
- Auction issues - Verify order type eligibility, cutoff times, NOII parsing
- Execution issues - Validate tick/lot compliance, fee tier, priority rules
- Regulatory issues - Confirm trade-through protection, best execution logic
Chinese Futures (CTP)
- Data issues - DBL_MAX validation (1.7976931348623157e+308), CZCE UpdateMillisec=0, night replay filtering
- Session issues - TradingDay vs ActionDay semantics, 21:00 reset, trading breaks (10:15-10:30)
- Order issues - CloseToday/CloseYesterday (SHFE/INE), cancel-replace queue loss, DCE stop orders
- Auth issues - 看穿式监管 AppID/AuthCode, CTP version ≥6.3.15, physical machine required
- Gap issues - CTP has NO replay; reconnection gaps are permanent data loss
File Index
Content Files
Equity:
equity/equity.md- Equity market fundamentalsequity/amer/equity_amer.md- US equity market structureequity/amer/nasdaq/nasdaq.md- Nasdaq exchange mechanics
Futures:
futures/futures.md- Futures market fundamentalsfutures/apac/futures_apac.md- APAC futures overviewfutures/apac/china/futures_china.md- Chinese futures (main)futures/apac/china/shfe/shfe.md- SHFE specificsfutures/apac/china/dce/dce.md- DCE specificsfutures/apac/china/czce/czce.md- CZCE specificsfutures/apac/china/cffex/cffex.md- CFFEX specificsfutures/apac/china/ine/ine.md- INE specifics
Reference Files
US Equity References:
equity/amer/references/regulatory/sec_reg_nms.md- Reg NMS overviewequity/amer/references/regulatory/finra_rules.md- FINRA rulesequity/amer/references/regulatory/rule_605_606.md- Disclosure rulesequity/amer/references/specs/sip_specs.md- SIP specifications
Nasdaq References:
equity/amer/nasdaq/references/specs/itch_protocol.md- ITCH 5.0 specequity/amer/nasdaq/references/specs/ouch_protocol.md- OUCH 4.2/5.0 specequity/amer/nasdaq/references/specs/totalview.md- TotalView productequity/amer/nasdaq/references/regulatory/nasdaq_rules.md- Nasdaq rulebook
Futures References:
futures/references/spreads.md- Calendar/inter-commodity spread mechanics (CME/ICE)futures/references/flow_interpretation.md- Flow analysis framework (when flow signals direction)
Chinese Futures References:
futures/apac/china/references/specs/ctp_market_data.md- CTP struct specificationfutures/apac/china/references/specs/data_quality_checklist.md- Validation checklistfutures/apac/china/references/specs/failure_modes.md- Failure mode catalogfutures/apac/china/references/models/queue_position.md- Queue estimation modelsfutures/apac/china/references/models/trade_direction.md- Trade direction inferencefutures/apac/china/references/models/causal_analysis.md- Causal identification frameworkfutures/apac/china/references/models/cross_product_analysis.md- Cross-product patternsfutures/apac/china/references/models/spreads.md- Chinese spread execution (CTP, legging risk)futures/apac/china/references/regime_changes.md- Regime change database
In this repository14 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- 97-devSkill
- alpha-squadSkill
- anti-ai-slopSkill
- arxiv-searchSkill
- bug-huntersSkill
- chain-systemSkill
- cost-statusSkill
- datetimeSkill
- dev-expertsSkill
- golang-proSkill
- mft-research-expertsSkill
- polars-expertiseSkill
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

