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
- IngAs8/ClaudeSkilledited, first seen Sep 28, 2026
Other versions1 project uses a version of this.
Word for word · 0
None found.
Edited · 1
- IngAs8/ClaudeSkill★ 038% same
Wrote their own version · 0
None found.
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 repository56 other files it gives its agents.
- candlestick-patternsSkill
- channel-tradingSkill
- cup-and-handleSkill
- double-top-bottomSkill
- flag-pennantSkill
- head-and-shouldersSkill
- triangle-patternsSkill
- wedge-patternsSkill
- altcoin-rotationSkill
- arbitrage-tradingSkill
- dca-strategySkill
- funding-rate-tradingSkill
- on-chain-analysisSkill
- breakout-tradingSkill
- gap-tradingSkill
- momentum-tradingSkill
- news-tradingSkill
- pullback-tradingSkill
- range-tradingSkill
- scalping-strategySkill
- earnings-tradingSkill
- economic-calendar-tradingSkill
- insider-activity-tradingSkill
- market-correlation-tradingSkill
- sector-rotationSkill
- sentiment-analysisSkill
- breaker-blocksSkill
- fair-value-gapsSkill
- kill-zonesSkill
- liquidity-zonesSkill
- market-structure-shiftSkill
- optimal-trade-entrySkill
- order-blocksSkill
- premium-discountSkill
- correlation-riskSkill
- drawdown-managementSkill
- leverage-managementSkill
- partial-profit-takingSkill
- position-sizingSkill
- risk-reward-ratioSkill
- stop-loss-strategiesSkill
- trailing-stopSkill
- bollinger-bandsSkill
- divergence-tradingSkill
- fibonacci-tradingSkill
- ichimoku-cloudSkill
- macd-tradingSkill
- market-regime-detectionSkill
- mean-reversionSkill
- moving-average-crossoverSkill
- multi-timeframe-analysisSkill
- rsi-divergenceSkill
- stochastic-tradingSkill
- supply-demand-zonesSkill
- vwap-tradingSkill
- skill-nameSkill
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
- Distinctive: line 30
Stop beyond VA boundary
- Distinctive: line 33
Test reversion to POC with a fixed horizon.
- Distinctive: line 43
Use an objective trigger and structural invalidation.
- Distinctive: line 91
Treat the setup as a testable hypothesis, not a prediction.
- Distinctive: line 100
Treat HVN/LVN reactions as hypotheses, not magnets, barriers, or air pockets.
- Distinctive: line 103
Test overlaps incrementally.
≈ “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.
Files
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
| Concept | Definition | Trading Use |
| POC | Bin with highest assigned volume | Descriptive mode of the profile |
| Value Area (VA) | Contiguous region containing a chosen volume share | Conventional descriptive region |
| VAH | Upper VA boundary | Resistance in ranges, breakout level in trends |
| VAL | Lower VA boundary | Support in ranges, breakdown level in trends |
| HVN | Locally high assigned-volume bin | Candidate consolidation/reaction feature |
| LVN | Locally low assigned-volume bin | Candidate 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
- 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) - Check volume indicator:
get_indicators(indicator_code="mfi", symbol=<symbol>, exchange=<exchange>, interval=<interval>) - 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.
- 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%)"} }) - 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>) - 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
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.

