crypto-liquidity-flow
Skill0 starsChanged 4 months agoMITView on GitHub
Concepts and signals for crypto liquidity-flow analysis — ETF flows, derivatives, on-chain, liquidations, and dominance/rotation. Use when designing a liquidity-flow data pipeline or interpreting where capital is moving.
In this repository11 other files it gives its agents.
- advanced-sql-timescaleSkill
- backtesting-disciplineSkill
- fastapi-best-practicesSkill
- llm-integrationSkill
- market-microstructureSkill
- qdrant-vector-dbSkill
- redis-patternsSkill
- risk-managementSkill
- senior-prompt-engineerSkill
- strategy-optimizationSkill
- websocket-realtimeSkill
The file
Files
Crypto Liquidity Flow
Liquidity flow = where is capital actually moving, across the layers that drive crypto price. Track them together; any one in isolation misleads.
The layers (and what each tells you)
- Spot ETF flows — net creations/redemptions are slow, sticky institutional demand. Sustained inflows are a structural tailwind; sharp outflows precede risk-off. Lags price, but confirms trend conviction.
- Derivatives (funding + OI) — perp funding shows positioning crowding; open interest shows whether moves are driven by new positions or unwinds. Extreme one-sided funding + stacked OI = squeeze fuel.
- Liquidations — forced flow. Clusters mark where leverage breaks; cascades produce sharp wicks and spike cross-asset correlation toward 1.
- On-chain — exchange in/outflows (coins leaving exchanges = accumulation), stablecoin supply (dry powder), and large-holder movement.
- Dominance & rotation — BTC.D / ETH.D and stablecoin dominance reveal risk appetite rotating between BTC, ETH, alts, and cash.
Reading the flow
- Confluence over single signals. ETF inflows + falling exchange balances + rising OI on rising price = a high-conviction structural bid. One signal alone is noise.
- Lead/lag awareness. On-chain and ETF flows lead; funding and liquidations are coincident/reactive. Don't treat a lagging confirmation as a fresh signal.
- Regime sensitivity. In a crash, correlations converge and "diversified" liquidity dries up simultaneously — model that, don't assume independence.
Building a liquidity-flow pipeline
- Real data only — pull from exchange/ETF/on-chain sources; never mock
values in a path that feeds decisions. (See
backtesting-discipline.) - Point-in-time — store metrics as-reported; on-chain and funding get revised. Don't backfill revised values into historical analysis.
- Cache with sane TTLs — refresh cadence ≥ source update frequency; stale
liquidity data is worse than none. (See
redis-patterns.) - Aggregate into a single view — combine layers into one normalized snapshot so downstream consumers reason about flow, not raw feeds.
Pairs with [[market-microstructure]] (order flow / CVD / funding mechanics) and [[risk-management]] (correlation spikes in cascades).
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.

