market-data-engine

To collect and store OHLCV market data in SQLite, this Skill fetches forex, indices, metals, energy, and crypto data via yfinance and tvdatafeed, then writes it to dedicated SQLite tables across intervals from 1m to weekly.

Backfilling historical market data across multiple intervals is handled by fetching OHLCV records from yfinance and tvdatafeed, covering 1m through weekly timeframes, and persisting them directly into a SQLite schema for querying.

Yes, this data collection workflow supports both crypto and forex OHLCV snapshots by utilizing yfinance and tvdatafeed as data sources, harmonizing the results, and storing them in a unified SQLite database for analysis.

You can calculate currency strength rankings using yfinance and tvdatafeed data because this Skill collects currency indices and snapshots, storing the results in SQLite to enable quick portfolio bias checks and analysis.

Using SQLite for fragmented market data provides local storage but may face concurrent write limitations during large backfills; this Skill mitigates fragmentation by harmonizing OHLCV, snapshots, and currency strength into dedicated tables.

Yes, you need both yfinance and tvdatafeed to fetch equity indices and metals data comprehensively, as this Skill relies on both dependencies to source and harmonize OHLCV data before writing it to SQLite.