volatility

Compute annualized historical volatility and rank it within a lookback window to generate position signals.

Updated Jun 12, 2026
One-click install
npx skills add https://github.com/GGwujun/SigmX --skill volatility-ggwujun
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: volatility
Source: https://github.com/GGwujun/SigmX/tree/main/agent/src/skills/volatility
Command: npx skills add https://github.com/GGwujun/SigmX --skill volatility-ggwujun

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Volatility regime detection and automated trading signals to exploit mean-reversion, helping traders enter during low-volatility regimes and exit or short during high-volatility regimes.

Core Features & Use Cases

  • HV-based signal generation: computes annualized historical volatility and ranks it over a lookback window to produce actionable long/short/neutral signals.
  • Platform compatibility: works with any OHLCV dataset (stocks, crypto, futures) and can be integrated into backtests or live strategies.
  • Use Case: a fund can automate volatility-mean-reversion decisions across hundreds of instruments, reducing manual monitoring and enabling rapid deployment.

Quick Start

Command an AI assistant to run the Volatility Strategy on your OHLCV dataset with hv_window=20, lookback=120, low_pct=20, high_pct=80, and annualize=252.

Frequently Asked Questions about volatility

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I generate mean-reversion trading signals from historical volatility?

Mean-reversion trading signals are generated by computing annualized historical volatility, ranking it within a lookback window, and outputting long, short, or neutral positions based on low and high percentile thresholds.

Can I use historical volatility signals on cryptocurrency OHLCV data?

Historical volatility signals work directly on cryptocurrency OHLCV data, as well as equities and futures, applying the same volatility regime ranking logic across different asset classes.

What is the best way to automate volatility regime detection across multiple assets?

Automating volatility regime detection involves applying an annualized historical volatility calculation with a set lookback window and percentile thresholds to multiple OHLCV datasets, producing actionable entry and exit signals.

How do I configure historical volatility parameters for a backtesting framework?

Historical volatility parameters for a backtesting framework are configured using hv_window, lookback, low_pct, high_pct, and annualize settings to calibrate volatility ranking and signal generation.

Does this volatility strategy require any specific dependencies or libraries?

This volatility strategy operates with no specific dependencies required, processing OHLCV data directly to produce mean-reversion signals for integration into existing backtesting or live trading systems.