CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

data-routing

The single ROUTER for every data need. Load this skill BEFORE any backtest, data-fetch, or research task to pick the best available source/tool, honour auth (env) requirements, and avoid ban-risk providers.

Quality

80%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./agent/src/skills/data-routing/SKILL.md
SKILL.md
Quality
Evals
Security

Data Routing (Router)

This is the one router. It maps (a) every registered backtest data source to its markets / auth / skill, and (b) every research data need to the concrete tool that serves it, its market, and the env key it requires. Source names below are a strict subset of backtest.loaders.registry.VALID_SOURCES (enforced by tests/test_data_routing_sources_subset.py).

Source Overview

Every name here is a registered OHLCV/backtest source in VALID_SOURCES. "Runner-internal" sources are selected by the backtest runner, not authored as a per-source skill.

SourceMarketsAuth (env key)NetworkSkill
tushareA-shares, funds, futures, macroYes (TUSHARE_TOKEN)China networktushare
akshareA-shares, US, HK, futures, macro, forexNoUnrestrictedakshare
yfinanceUS, HK, Canada (TSX/TSXV) stocks, ETFsNoNeeds Yahoo accessyfinance
okxCrypto (OKX exchange)NoNeeds okx.com accessokx-market
nobitexCrypto, IRT/Toman-quoted pairs (BTC-IRT, USDT-IRT — Iran market premium)NoNeeds apiv2.nobitex.ir accessdata-routing (explicit *IRT routing only)
wallexCrypto, TMN/Toman-quoted pairs (USDT-TMN, BTC-TMN — Iran market premium)NoNeeds api.wallex.ir accessdata-routing (explicit *TMN routing only; truly serves 1m/1h/1d)
ccxtCrypto (100+ exchanges)NoNeeds exchange accessccxt
baostockA-shares (free daily/min)NoChina networkdata-routing
tencentA-shares, HK, US (never-banned)NoUnrestricteddata-routing
mootdxA-shares (retired 2026-10: TDX servers stopped answering the client protocol; explicit source="mootdx" only)NoChina networkdata-routing
futuA/HK/US via OpenD gatewayYes (OpenD running)Local gatewaydata-routing (runner-internal)
mt5Forex & metals (your broker's MT5 feed)Yes (running, logged-in MT5 terminal; optional ~/.vibe-trading/mt5.json)Local terminal (Windows)data-routing (runner-internal)
tickerallForex & metals (same broker MT5 feed, hosted)Yes (TICKERALL_API_KEY + TICKERALL_ACCOUNT_ID; read-only)Hosted API (any OS, no terminal)data-routing (runner-internal; explicit source=tickerall only)
localUser CSV/parquet on diskNoOfflinedata-routing (runner-internal)
eastmoneyA-shares, HK, US equitiesNo (IP-throttled)Unrestricteddata-routing
sinaUS equities (daily OHLCV)No (IP-throttled)Unrestricteddata-routing
stooqUS equities (daily OHLCV)NoUnrestricteddata-routing
yahooUS, HK, Canada (TSX/TSXV) equitiesNo (IP-throttled)Needs Yahoo accessdata-routing
finnhubUS equitiesYes (FINNHUB_API_KEY)Unrestricteddata-routing
alphavantageUS equitiesYes (ALPHAVANTAGE_API_KEY)Unrestricteddata-routing
tiingoUS equitiesYes (TIINGO_API_KEY)Unrestricteddata-routing
fmpUS equitiesYes (FMP_API_KEY)Unrestricteddata-routing
gildataA-shares (前复权 dailies), HK equities (raw), CN indicesToken + market quotes enabled in Settings; only when the user requests source="gildata", no fallbackGildata MCP APIdata-routing

Capability → Tool Routing

Pick the tool by the data need. "Market" is the universe the tool covers; "Env key" is required only where listed (no key listed = free / no auth).

Data needToolMarketEnv key
OHLCV price barsget_market_dataA-share / US / HK / Canada / crypto / futures / forexper-source (see Source Overview)
Fund flow (资金流向)get_fund_flowA-share, HK, US—
Dragon-tiger (龙虎榜)get_dragon_tigerA-share—
Northbound flow (北向资金)get_northbound_flowA-share—
Margin trading (融资融券)get_margin_tradingA-share—
Block trades (大宗交易)get_block_tradesA-share—
Shareholder count (股东户数)get_shareholder_countA-share—
Lockup expiry (限售解禁)get_lockup_expiryA-share—
Sector / board taxonomy (板块)get_sector_infoA-share—
Sell-side research reportsget_research_reportsA-share—
Stock newsget_stock_newsA-share, US, HK—
SEC filings (EDGAR)get_sec_filingsUS—
Financial statementsget_financial_statementsA-share, US, HK—
Options chainget_options_chainUS—
Stock profile / fundamentalsget_stock_profileUS—
Market screenscreen_marketA-share—
Symbol searchsearch_symbolA-share, US, HK, Canada, crypto/index/FX—
Macro / FRED seriesget_macro_seriesMacro (US/global)FRED_API_KEY
OTC fund NAV (场外基金净值)get_fund_navCN off-exchange fundsGILDATA_TOKEN + fund_nav opt-in
China macro / industry EDB (宏观行业)get_cn_macro_seriesCN macro/regional/industryGILDATA_TOKEN + macro_series opt-in
CN announcements (公告检索)get_cn_announcementsA-share / HK / fundGILDATA_TOKEN + announcements opt-in
Broker research (券商研报)search_broker_reportsA-share / HKGILDATA_TOKEN + broker_reports opt-in
iWenCai NL search (问财)iwencai_searchA-shareVIBE_TRADING_IWENCAI_KEY

Notes:

  • get_financial_statements reads US statements from SEC EDGAR companyfacts (ticker -> CIK -> XBRL concepts) and A-share/HK statements from the Eastmoney datacenter report API (per-market F10 report names).
  • get_stock_news routes A-share (SH/SZ/BJ) to an Eastmoney news client and US (.US) / HK (.HK) to a Yahoo search client; a failure on one upstream is returned as an error envelope, never raised, so a single bad symbol never aborts a batch.

Decision Tree

Backtest scenario (writing config.json)

Use source: "auto" — the runner routes by symbol pattern and falls back across same-market sources automatically. Only set a concrete source when the user asks.

Analysis / research scenario

  1. Identify the data need, then read the Capability table for the tool + env key.
  2. If the need is plain OHLCV, call get_market_data and let source fallback run.
  3. Set any required env key before calling a key-gated tool; if it is missing, report the missing key rather than failing silently.

Source priority (for OHLCV by market)

  • A-shares: tencent (never banned) > tushare (TUSHARE_TOKEN) > baostock / akshare > eastmoney (throttled).
  • US stocks: stooq / yahoo > tiingo / finnhub / fmp / alphavantage (key-gated) > sina / eastmoney (throttled) > yfinance.
  • HK stocks: tencent (never banned, daily) > eastmoney / yahoo > futu (local OpenD) > akshare (Eastmoney-backed, daily only) > yfinance > tushare (TUSHARE_TOKEN) / longbridge (key-gated).
  • Canada (TSX/TSXV): yahoo > yfinance > local; use Yahoo's canonical .TO / .V suffixes (for example TD.TO, PNG.V).
  • Crypto: okx (single exchange) > ccxt (multi-exchange).
  • Futures / macro: tushare > akshare.
  • Forex / metals: mt5 (local MetaTrader 5 terminal, Windows) > akshare. TickerAll (source="tickerall") is a hosted, no-terminal alternative to the same broker feed (any OS) — opt-in and explicit-only: it never joins this automatic chain, so a user's broker credential is used only when deliberately requested.

Symbol Format Reference

MarketFormatExamples
A-sharesNNNNNN.SZ/SH/BJ000001.SZ, 600000.SH, 430139.BJ
US stocksTICKER.USAAPL.US, MSFT.US
HK stocksNNNNN.HK00700.HK, 09988.HK
Canada TSX / TSXVTICKER.TO / TICKER.VTD.TO, BBD-B.TO, PNG.V
CryptoSYMBOL-USDTBTC-USDT, ETH-USDT
FuturesXXNNNN.EXCHANGECU2406.SHFE
ForexXXX/YYYUSD/CNY, EUR/USD

Ban-Risk & Fallback Notes

  • Prefer never-banned sources: tencent has no observed IP ban; reach for it first for A-share OHLCV when no token is set.
  • Eastmoney rate-limits by IP and must be throttled. Every Eastmoney-backed tool/loader routes through the shared per-host throttle; do not hammer it. On a throttle/timeout, fall back to the same-market source above (tencent/baostock).
  • Sina / Yahoo also throttle by IP — same per-host wrapper, same fallback rule.
  • Key-gated sources need their env key (FINNHUB_API_KEY, ALPHAVANTAGE_API_KEY, TIINGO_API_KEY, FMP_API_KEY, FRED_API_KEY, VIBE_TRADING_IWENCAI_KEY, TUSHARE_TOKEN). If the key is absent the tool/loader is unavailable — route to a free same-market source instead of erroring out.
  • A single failing symbol or transient HTTP error is reported inside the envelope; it never aborts the surrounding batch.

Data Verification Discipline

When a number will drive a conclusion (valuation, screening, report), do not trust a single source. Cross-check it:

  • Verify material figures across ≥2 independent sources before citing them. Prioritize original disclosures (company annual/quarterly reports, exchange filings) over third-party aggregators.
  • Flag any deviation >1% between sources as a ⚠️ caliber mismatch — usually a definition difference (GAAP vs Non-GAAP, consolidated vs parent-only, currency, TTM vs annual). Do not silently pick one; state both and which you adopt.
  • Use the financial_rigor tool's cross_validate command to do this exactly: pass {source: value, ...} and it returns the median consensus + per-source deviation + an all_consistent flag at a configurable tolerance (default 2%).
  • Mark unverified numbers as "single-source" or "estimate" — never present an uncorroborated figure as established fact.

This discipline is what separates analysis from aggregation.

Gildata research and OTC funds

When the user has enabled the corresponding feature and configured a Gildata token, use its tool for China macro observations, announcements and broker reports. Inspect the returned api_names; routing is vendor-selected. Rows retain vendor order and explicitly report truncation. Narrow the topic or date window to retrieve omitted records. When declaring a macro observation, reference its actual field, for example call_id::rows[0].value, and preserve the returned unit and date. Indicator codes are identifiers, not measurements.

get_fund_nav reads OTC fund NAV history with an exact vendor-code match. Exchange-listed ETF/LOF prices still use the OHLCV loaders. Unit, accumulated and adjusted NAV are different measures; name the one actually reported. Missing NAV values remain missing. NAV rows never enter the OHLCV backtest loader.

Repository

HKUDS/Vibe-Trading

Path

agent/src/skills/data-routing/SKILL.md

Last updated
First committed

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.