agentleFS
SKE-LabsSKE-Labs/agent-trading-skills/skills/technical-strategies/volume-profile-trading/SKILL.md

volume-profile-trading

Skill17 starsChanged 4 months agoApache-2.0View on GitHub

Build and test volume-at-price profiles using POC, value area, and nodes. Use when the user has trade/tick data or needs a clearly disclosed OHLCV approximation.

1 other project uses a version of this, 1 of them edited.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

6 rules. About 0 are common, 6 are distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈6

    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:

    Stop beyond VA boundary

    line 30
  2. Distinctive:

    Test reversion to POC with a fixed horizon.

    line 33
  3. Distinctive:

    Use an objective trigger and structural invalidation.

    line 43
  4. Distinctive:

    Treat the setup as a testable hypothesis, not a prediction.

    line 91
  5. Distinctive:

    Treat HVN/LVN reactions as hypotheses, not magnets, barriers, or air pockets.

    line 100
  6. Distinctive:

    Test overlaps incrementally.

    line 103

≈ “Common” is an estimate: at least 1 in 5 of the 364,980 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

Volume Profile Trading

Volume profile describes volume assigned to price bins over a declared session/range. It does not reveal trader identity, fair value, or a guaranteed reaction.

Core Concepts

ConceptDefinitionTrading Use
POCBin with highest assigned volumeDescriptive mode of the profile
Value Area (VA)Contiguous region containing a chosen volume shareConventional descriptive region
VAHUpper VA boundaryResistance in ranges, breakout level in trends
VALLower VA boundarySupport in ranges, breakdown level in trends
HVNLocally high assigned-volume binCandidate consolidation/reaction feature
LVNLocally low assigned-volume binCandidate traversal/reaction feature

Entry Strategies

Value Area Bounce (Range Trading)

  • Buy at VAL with bullish rejection candle, target POC
  • Sell at VAH with bearish rejection candle, target POC
  • Stop beyond VA boundary

POC Magnet

  • Test reversion to POC with a fixed horizon; price position alone is not an entry
  • Combine with RSI divergence at extremes for higher probability

Value Area Breakout

  • Breakout above VAH + volume spike → long, target next HVN above
  • Breakdown below VAL + volume spike → short, target next HVN below
  • Price must close outside VA (not just wick)

LVN Breakout Play

  • Define LVN relative to neighboring bins and test traversal time versus matched control bins
  • Use an objective trigger and structural invalidation; do not assume rapid movement

Workflow

  1. Get trade/tick data when available, including venue, session, price, size, and corrections. If only OHLCV exists, disclose that volume-at-price is approximated because candle volume has no exact price allocation:
    get_candles(symbol=<symbol>, exchange=<exchange>, interval=<interval>, count=200)
  2. Check volume indicator:
    get_indicators(indicator_code="mfi", symbol=<symbol>, exchange=<exchange>, interval=<interval>)
  3. Freeze the profile specification: session/range anchor, tick/bin size, trade corrections, allocation method, value-area share (70% is conventional), expansion algorithm, and tie handling. Compute POC/VAH/VAL without using future observations.
  4. Mark levels on chart:
    draw_chart_analysis(action="create", drawing={
        "type": "support",
        "points": [
            {"time": <start_time>, "price": <poc_price>},
            {"time": <end_time>, "price": <poc_price>}
        ],
        "options": {"text": "POC ($67,250)"}
    })
    draw_chart_analysis(action="create", drawing={
        "type": "demand",
        "points": [
            {"time": <start_time>, "price": <vah_price>},
            {"time": <end_time>, "price": <val_price>}
        ],
        "options": {"text": "Value Area (70%)"}
    })
  5. Confirm with indicators:
    get_indicators(indicator_code="rsi", symbol=<symbol>, exchange=<exchange>, interval=<interval>)
    get_indicators(indicator_code="ema", symbol=<symbol>, exchange=<exchange>, interval=<interval>)
  6. Report: POC level, VA boundaries, price position (inside/above/below VA), key LVNs, trade setup

Evidence and Validation

  • Treat the setup as a testable hypothesis, not a prediction. Define thresholds, entry, invalidation, and exit before evaluating outcomes.
  • Calibrate on the same instrument, venue, session, and timeframe. Use closed candles and a held-out or walk-forward sample; record every variant tried.
  • Include spread, fees, slippage, borrow or funding, partial fills, and latency. Reject the setup when net expectancy is not positive or depends on one narrow parameter.
  • Return observed inputs, missing data, cost assumptions, entry, invalidation, exit, and a valid, watch, or no-trade status.
  • Research basis: Volume profile is a descriptive distribution. Published trading-rule evidence is limited; a recent value-area breakout test found the unfiltered signal was not economically significant.

Key Rules

  • Require enough observations for stable bins and show sensitivity to bin width; no candle count is universal.
  • Treat HVN/LVN reactions as hypotheses, not magnets, barriers, or air pockets.
  • Anchor and update profiles according to the predeclared session/event rule.
  • State whether volume is actual venue trades, consolidated, tick volume, or OHLCV-allocated approximation.
  • Test overlaps incrementally; multiple price-derived labels are not independent confluence.

Related Skills

  • supply-demand-zones — volume profile HVNs confirm S/D zone strength; LVNs identify breakout acceleration areas
  • fibonacci-trading — POC or VAL/VAH overlapping with Fib levels creates strong confluence

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.