agentleFS
krzysukrzysu/market-skills/skills/market-volume/SKILL.md

market-volume

Skill3 starsChanged 4 months agoMITView on GitHub

Computes volume analysis: volume ratio vs SMA(20), OBV trend, volume regime classification (CLIMAX / HIGH / NORMAL / LOW). Use for volume confirmation of price moves, divergence detection, and regime filtering. Supports any yfinance ticker.

The file

We split this skill into the rules it gives an agent

1 rule. About 0 are common, 1 is distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Use it to confirm a move (volume supports the trend), not as a standalone entry trigger.

    line 20

≈ “Common” is an estimate: at least 1 in 5 of the 372,429 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

market-volume

Volume analysis skill: measures current volume relative to its 20-period average, tracks On-Balance Volume (OBV) trend, and classifies the volume regime.

When NOT to use

  • This is a context/confirmation skill, not a directional signal — volume confirms or rejects price moves, it never says which way to trade. Pair with market-trend for direction.
  • A CLIMAX reading can mean exhaustion (trend ending), not continuation — do not read high volume as bullish by itself.
  • Use it to confirm a move (volume supports the trend), not as a standalone entry trigger.

Quick Start

uv run skills/market-volume/scripts/run.py AAPL --json

Flags

FlagDefaultNotes
TICKER (positional)—Required. Supports provider:ticker (e.g. hl:LIT, yf:AAPL).
--jsonhumanEmit JSON to stdout.
--source=PROVIDERauto-detectForce a data provider (see README).
--interval=INTERVAL1d1m/2m/5m/15m/30m/1h/2h/4h/8h/12h/1d/3d/1wk/1M.
--period=PERIOD1y1d/5d/1mo/3mo/6mo/1y/2y/5y/10y/ytd/max.

Both timeframe flags are validated — bad values exit 2 with a friendly error. Defaults give daily candles over 1y (~250 bars), enough for SMA(20)-volume baseline and OBV slope. For intraday (--interval=1h), bump --period to 6mo or 1y; yfinance caps hourly at ~2y and anything sub-hour at ~60d.

What it returns

  • volume_ratio — current volume divided by SMA(20) of volume
  • obv_trend — whether OBV is rising or falling relative to its SMA
  • obv_divergence — bullish/bearish divergence between price and OBV
  • regime — CLIMAX / HIGH / NORMAL / LOW volume classification

Volume Regime Interpretation

RegimeRatio RangeMeaning
CLIMAX>= 2.5x avgPotential exhaustion — trend may be ending
HIGH1.5–2.5x avgStrong participation — confirms the move
NORMAL0.5–1.5x avgTypical activity — neutral
LOW< 0.5x avgLow interest — breakouts may fail

Edge Cases

  • OBV divergence requires 56+ candles of data to compute reliably.
  • Volume ratio over 5.0x can indicate news events or data anomalies — still reported but flagged as extreme.
  • Context skill: no directional score or signal — volume confirms or rejects price moves.
  • Best used with market-trend for trend-aware volume analysis.

Output envelope (AXI)

--json output follows the canonical AXI envelope — {data, count, errors, help[]}. Default schema is the per-skill minimal fields (3-6 essentials); pass --fields=<csv> to project or --full for the full payload. count is the item count, help[] is contextual next-step command templates. Lib.py return shapes (L1Result / L2Result / L3Result / L3Idea / RegimeSignal) are unchanged — the envelope wraps them at the scripts/run.py boundary.

Home view (no-arg mode)

No-arg mode prints the home view from $XDG_DATA_HOME/market-skills/<skill>_last.json (last successful run). Errors are not cached.

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.