volatility-modeling
Skill0 starsChanged 3 months agoMITView on GitHub
Volatility estimation, forecasting, and regime classification using GARCH, EWMA, realized volatility, and volatility cones
- Installs packages
2 other projects use a version of this.
Adopted by
Most recently taken up by
- IngAs8/ClaudeSkilltheir own version, first seen Sep 28, 2026
- agiprolabs/claude-trading-skillsword for word, first seen Mar 11, 2026
Other versions2 projects use a version of this.
Word for word · 1
- agiprolabs/claude-trading-skills★ 366100% same
Edited · 0
None found.
Wrote their own version · 1
- IngAs8/ClaudeSkill★ 0same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository66 other files it gives its agents.
- backtraderSkill
- birdeye-apiSkill
- coingecko-apiSkill
- cointegration-analysisSkill
- copy-tradingSkill
- correlation-analysisSkill
- cost-basis-engineSkill
- crypto-tax-exportSkill
- custom-indicatorsSkill
- defillama-apiSkill
- dex-executionSkill
- dex-pool-analysisSkill
- dexscreener-apiSkill
- exit-strategiesSkill
- feature-engineeringSkill
- fixed-incomeSkill
- helius-apiSkill
- impermanent-lossSkill
- jito-bundlesSkill
- kalshi-apiSkill
- kalshi-crypto-index-marketsSkill
- kalshi-weather-marketsSkill
- kelly-criterionSkill
- liquidity-analysisSkill
- lp-mathSkill
- market-microstructureSkill
- market-microstructure-traditionalSkill
- mean-reversionSkill
- mev-analysisSkill
- ohlcv-processingSkill
- options-pricingSkill
- pandas-taSkill
- polymarket-apiSkill
- portfolio-analyticsSkill
- position-sizingSkill
- prediction-market-strategySkill
- pumpfun-mechanicsSkill
- raptor-dexSkill
- regime-detectionSkill
- regulatory-reportingSkill
- risk-managementSkill
- rl-executionSkill
- sentiment-analysisSkill
- shredstreamSkill
- signal-classificationSkill
- slippage-modelingSkill
- solana-rpcSkill
- solanatracker-apiSkill
- solana-tx-buildingSkill
- strategy-frameworkSkill
- sybil-detectionSkill
- ta-libSkill
- tax-liability-trackingSkill
- tax-loss-harvestingSkill
- token-economicsSkill
- token-holder-analysisSkill
- trade-accountingSkill
- trade-journalSkill
- trading-visualizationSkill
- vectorbtSkill
- The first 60 shown.
The file
Files
Volatility Modeling
Volatility — the magnitude of price fluctuations — is arguably the single most important quantity in trading. It drives position sizing, stop placement, option pricing, and regime detection. This skill covers estimation, forecasting, and practical application of volatility in crypto markets.
Why Volatility Matters
| Use Case | How Volatility Is Used |
| Position sizing | Scale position inversely with vol so each trade risks a consistent dollar amount |
| Stop placement | ATR-based stops widen in high-vol regimes, tighten in low-vol |
| Strategy selection | Mean-reversion works in low vol; momentum works in high vol |
| Risk budgeting | Vol-target portfolios maintain constant portfolio-level risk |
| Regime detection | Vol regime shifts signal changing market dynamics |
| Option pricing | Implied vs realized vol gap creates trading opportunities |
Types of Volatility
Historical (Realized) Volatility
Computed from observed past returns. The most common and directly measurable form. Multiple estimators exist with different statistical efficiency.
Implied Volatility
Derived from option prices via Black-Scholes or similar models. Limited in crypto DeFi where liquid options markets are sparse, but available on Deribit for BTC/ETH.
Forecast Volatility
Predicted future volatility from models like EWMA or GARCH. Used for forward-looking position sizing and risk budgets.
Estimation Methods
1. Close-to-Close (Standard Deviation of Log Returns)
The simplest estimator. Compute the standard deviation of log returns and annualize.
import numpy as np
log_returns = np.log(closes[1:] / closes[:-1])
vol_daily = np.std(log_returns, ddof=1)
vol_annual = vol_daily * np.sqrt(365) # crypto trades 365 days- Pros: Simple, widely understood.
- Cons: Uses only close prices — ignores intraday range.
2. Parkinson (High-Low Range)
Uses the daily high-low range, which is ~5x more statistically efficient than close-to-close.
hl_ratio = np.log(highs / lows)
vol_parkinson = np.sqrt(np.mean(hl_ratio**2) / (4 * np.log(2))) * np.sqrt(365)- Pros: More efficient, captures intraday moves.
- Cons: Downward bias with discrete sampling; ignores close-to-close jumps.
3. Garman-Klass (OHLC)
The most efficient single-day OHLC estimator.
hl = np.log(highs / lows)
co = np.log(closes / opens)
gk = np.mean(0.5 * hl**2 - (2 * np.log(2) - 1) * co**2)
vol_gk = np.sqrt(gk) * np.sqrt(365)- Pros: Best efficiency among OHLC estimators.
- Cons: Assumes no drift; sensitive to opening gaps.
4. Yang-Zhang
Combines overnight (close-to-open) and open-to-close components. Handles gaps properly. Less relevant for 24/7 crypto but useful for tokens with sporadic trading.
5. EWMA (Exponentially Weighted Moving Average)
RiskMetrics approach — no parameters to estimate beyond λ.
lam = 0.94 # RiskMetrics default for daily
ewma_var = np.zeros(len(returns))
ewma_var[0] = returns[0] ** 2
for t in range(1, len(returns)):
ewma_var[t] = lam * ewma_var[t - 1] + (1 - lam) * returns[t - 1] ** 2
vol_ewma = np.sqrt(ewma_var) * np.sqrt(365)- λ = 0.94 for daily data (RiskMetrics).
- λ = 0.97 for weekly data.
- Higher λ → smoother, slower reaction to new information.
6. GARCH(1,1)
The workhorse autoregressive volatility model. Captures volatility clustering.
σ²_t = ω + α · r²_{t-1} + β · σ²_{t-1}- ω: long-run variance weight.
- α: reaction to recent shock (typically 0.05–0.15 for crypto).
- β: persistence (typically 0.80–0.90 for crypto).
- α + β < 1: stationarity constraint.
- Long-run variance: ω / (1 − α − β).
Estimated via maximum likelihood. See references/estimators.md for details.
Volatility Cones
Volatility cones show the percentile distribution of realized volatility at different lookback windows, revealing whether current vol is historically high or low.
Construction
- Get 1+ years of daily data.
- For each lookback window (5, 10, 20, 60, 120 days):
- Compute rolling realized volatility.
- Extract percentiles: 5th, 25th, 50th, 75th, 95th.
- Plot percentiles vs window length — the "cone" shape.
- Overlay current realized vol at each window.
Interpretation
- Current vol > 75th percentile: historically elevated — expect mean reversion.
- Current vol < 25th percentile: historically compressed — expect expansion.
- Cone narrowing at longer windows: vol mean-reverts over longer horizons.
See references/volatility_cones.md for full methodology and worked examples.
Crypto Volatility Characteristics
Crypto vol differs from traditional assets in important ways:
| Characteristic | Detail |
| Level | 50–150% annualized is typical; TradFi equities are 15–25% |
| Clustering | Strong — high-vol days cluster together |
| Weekday patterns | Weekend vol often lower but weekend gaps can be large |
| Volume correlation | Vol and volume are positively correlated |
| Regime dependence | Bull market vol ≠ bear market vol; ranges are different |
| Mean reversion | Vol mean-reverts more reliably than price |
| Tail risk | Fat tails — more extreme moves than normal distribution predicts |
Regime Classification by Volatility
| Regime | Annualized Vol Range | Characteristics |
| Low vol | < 40% | Range-bound, mean reversion works |
| Normal vol | 40–80% | Trending possible, balanced strategies |
| High vol | 80–120% | Strong trends or sharp reversals |
| Crisis vol | > 120% | Liquidation cascades, reduced position size |
Volatility Forecasting
EWMA Forecast
Simple and effective. The current EWMA variance estimate is the 1-step forecast. Multi-step forecasts are flat (same as 1-step).
GARCH Forecast
GARCH produces a term structure of variance forecasts:
σ²_{t+h} = V_L + (α + β)^h · (σ²_t − V_L)Where V_L = ω / (1 − α − β) is the long-run variance.
- Short-horizon forecasts reflect current conditions.
- Long-horizon forecasts converge to long-run variance.
- The speed of convergence depends on α + β (persistence).
See scripts/vol_forecast.py for a working implementation.
Practical Applications
Position Sizing with Volatility
# Vol-target position sizing
target_vol = 0.02 # 2% daily portfolio vol target
current_vol = 0.05 # 5% daily asset vol (annualized ~95%)
weight = target_vol / current_vol # = 0.40 → 40% allocationSee the position-sizing skill for complete integration.
ATR-Based Stop Placement
atr_14 = talib.ATR(highs, lows, closes, timeperiod=14)
stop_distance = 2.0 * atr_14[-1] # 2x ATR stop
stop_price = entry_price - stop_distance # for longsVol-Regime Strategy Selection
vol_percentile = current_vol_percentile(token, window=30)
if vol_percentile < 25:
strategy = "mean_reversion"
elif vol_percentile > 75:
strategy = "momentum_breakout"
else:
strategy = "balanced"Files
References
| File | Description |
references/estimators.md | Full derivations and details for all volatility estimators |
references/volatility_cones.md | Cone construction methodology and interpretation guide |
Scripts
| File | Description |
scripts/estimate_volatility.py | Multi-estimator volatility computation with cone analysis |
scripts/vol_forecast.py | EWMA and GARCH forecasting with term structure output |
Related Skills
regime-detection— Classify market regimes using volatility as a key input.position-sizing— Scale positions inversely with volatility.risk-management— Portfolio-level vol targeting and risk budgets.pandas-ta— ATR and Bollinger Bands are volatility-based indicators.custom-indicators— Build crypto-specific volatility indicators.
Dependencies
uv pip install pandas numpy scipyOptional for live data:
uv pip install httpxDoes 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.

