pullback-trading
Skill17 starsChanged 4 months agoApache-2.0View on GitHub
Enter trends on price retracements to key levels. Use when trading with the trend, finding high R:R entries, or timing entries in established trends. Trend confirmation via EMA slope (no ADX).
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★ 043% 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
- 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
- volume-profile-tradingSkill
- vwap-tradingSkill
- skill-nameSkill
The file
We split this skill into the rules it gives an agent
5 rules. About 0 are common, 5 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈5
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 54
Use an objective swing rule for HH/HL or LH/LL structure.
- Distinctive: line 86
Treat the setup as a testable hypothesis, not a prediction.
- Distinctive: line 96
Treat deeper retracement as a continuous risk feature, not a law at 61.8%.
- Distinctive: line 97
Put invalidation beyond the structural pullback extreme plus a calibrated volatility/tick buffer, then resize the position.
- Distinctive: line 98
Test trend age and pullback sequence out of sample rather than assuming the first is best.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 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
Pullback Trading
Enter established trends during temporary retracements for optimal risk/reward.
Identification
Pullback Levels
| Level | Depth | Trend Strength |
| 20/50 EMA | Dynamic | Strong (shallow) |
| Normalized retracement band | Shallow/moderate/deep | Calibrate by instrument and regime |
| Previous S/R flip | Variable | Structure-based |
Entry Confirmation (require before entering)
- Reversal candlestick pattern (hammer, engulfing)
- Momentum indicator turning in trend direction
- Volume decrease during pullback, increase on resumption
Workflow
1. Confirm Trend on Higher Timeframe
get_indicators returns one indicator per call — fetch each separately:
get_candles(symbol=<symbol>, exchange=<exchange>, interval=<htf_interval>, count=120)
get_indicators(indicator_code="ema_21", symbol=<symbol>, exchange=<exchange>, interval=<htf_interval>, count=120)
get_indicators(indicator_code="ema_50", symbol=<symbol>, exchange=<exchange>, interval=<htf_interval>, count=120)Then measure a five-bar EMA50 slope and normalize it by price or ATR. Five bars is a modeling choice, not a canonical horizon:
execute python3 -c "ema50=[<...>]; s=(ema50[-1]-ema50[-5])/ema50[-5]*100; print(f'htf_ema50_slope_pct={s:.3f}')"Define bullish and bearish stack rules plus slope thresholds from training data, then freeze them. Track bars since the trend trigger as a candidate maturity feature; do not label the first pullback highest probability without held-out evidence.
2. Get Price Data and Identify Pullback
get_candles(symbol=<symbol>, exchange=<exchange>, interval=<primary_interval>, count=60)Use an objective swing rule for HH/HL or LH/LL structure. Measure retracement as a continuous percentage of the prior impulse and test bands; moving averages, prior swings, and Fibonacci coordinates are candidate reference levels.
3. Check Momentum at Pullback Level
get_indicators(indicator_code="rsi_21", symbol=<symbol>, exchange=<exchange>, interval=<primary_interval>, count=20)
get_indicators(indicator_code="macd_fast", symbol=<symbol>, exchange=<exchange>, interval=<primary_interval>, count=20)Cite RSI / MACD as a 3-5 value progression (latest value alone is folklore):
- Uptrend pullback example:
RSI21 47.8 (62.4 → 55.1 → 49.0 → 47.8). Define any RSI band and MACD sign rule before testing; neither 50 nor a Fibonacci ratio is a natural boundary. - Downtrend pullback: mirror — RSI pulling up from low extreme toward 50, MACD histogram shrinking from negative toward zero but NOT crossing into positive.
4. Mark Entry Zone
draw_chart_analysis(action="create", drawing={
"type": "demand",
"points": [
{"time": <pullback_start>, "price": <fib_38>},
{"time": <pullback_end>, "price": <fib_62>}
],
"options": {"text": "Pullback Entry Zone (38-62%)"}
})5. Report to Orchestrator
Trend direction and strength, pullback depth (which Fib level), confirmation signals, entry level, stop below pullback low, target at previous swing high/low.
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 technical-analysis evidence review finds mixed results and recurring data-snooping and transaction-cost problems; calibrate pullback rules rather than treating ratios as natural laws.
Key Rules
- Require the predeclared trend and retracement conditions before evaluating an entry.
- Define reversal confirmation numerically and use a closed bar.
- Treat deeper retracement as a continuous risk feature, not a law at 61.8%.
- Put invalidation beyond the structural pullback extreme plus a calibrated volatility/tick buffer, then resize the position.
- Test trend age and pullback sequence out of sample rather than assuming the first is best.
- Compute EMA slope via
execute; do NOT call ADX / DMI / Supertrend (API-billed, not in the free whitelist)
Related Skills
- momentum-trading -- pullbacks occur within momentum moves
- breakout-trading -- test pullbacks to an objectively defined breakout level
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.

