fair-value-gaps
Skill17 starsChanged 4 months agoApache-2.0View on GitHub
Detect and test three-candle fair-value-gap zones. Use when the user wants an objective wick-gap definition, retracement statistics, entry, invalidation, and cost-aware validation.
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★ 033% 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
- 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
- volume-profile-tradingSkill
- vwap-tradingSkill
- skill-nameSkill
The file
We split this skill into the rules it gives an agent
3 rules. About 0 are common, 3 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈3
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 36
Identify FVG: after impulsive move using candle data:
- Distinctive: line 52
Treat the setup as a testable hypothesis, not a prediction.
- Distinctive: line 62
Test stacked gaps and higher-timeframe alignment rather than assuming directional strength.
≈ “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.
Files
Fair Value Gaps (FVG) Trading
A three-candle wick-gap convention. The pattern is observable in OHLC data; calling it inefficiency or institutional imbalance requires separate order-book/trade evidence.
Identification
Bullish FVG
- Strong bullish middle candle
- Gap between Candle 1 high and Candle 3 low
- Zone = the unfilled gap area
Bearish FVG
- Strong bearish middle candle
- Gap between Candle 1 low and Candle 3 high
- Zone = the unfilled gap area
Quality Factors
- Normalize gap size by ATR, spread, and middle-candle range.
- Record preceding swing/sweep, time-of-day relative volume, and higher-timeframe state as features.
- Calibrate thresholds and interactions; do not convert them into untested quality labels.
Workflow
- Identify FVG after impulsive move using candle data:
get_candles_around_date(symbol=<symbol>, exchange=<exchange>, interval=<interval>, date=<date>) - Mark the zone using
draw_chart_analysiswith typedemand(bullish) orsupply(bearish) - Wait for retracement into the gap
- Choose an entry rule — near boundary, midpoint, full traversal, or price confirmation; select in training data only
- Stop loss beyond the full FVG boundary
- Target the high/low of the impulse move
FVG + Order Block Confluence
Record overlap with a separately defined order-block zone and test whether it adds value over FVG alone; the labels are correlated price-derived features.
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: The three-candle definition follows the ICT convention, but independent market-microstructure research links price changes to observable order-flow imbalance and depth—not to guaranteed gap fills.
Key Rules
- Estimate touch and fill rates with a fixed horizon and competing-risk rule; do not call gaps magnets.
- Expire zones after a predeclared time and retain unfilled zones in the denominator.
- Test stacked gaps and higher-timeframe alignment rather than assuming directional strength.
- The midpoint is a coordinate, not an empirically privileged entry.
Related Skills
- order-blocks — test overlap between two explicitly defined candle-zone conventions
- premium-discount — Enter FVGs in discount for longs, premium for shorts
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.

