scalping-strategy
Skill17 starsChanged 4 months agoApache-2.0View on GitHub
Evaluate and plan very short-horizon trades in highly liquid markets. Use when the user needs an executable scalp with latency, spread, fee, slippage, and capacity controls.
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★ 036% 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
- 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
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 55
Use a calibrated range classifier.
- Distinctive: line 96
Treat the setup as a testable hypothesis, not a prediction.
- Distinctive: line 109
Do not deploy from win rate alone.
≈ “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
Scalping Strategy
Target small, frequent profits from minimal price movements on 1m-5m timeframes.
Setup Conditions
| Factor | Requirement |
| Data | Timestamped quotes/trades plus closed bars |
| Cost gate | Expected gross edge exceeds spread, fees, slippage, and adverse selection |
| Liquidity | Tested depth, order size, fill rate, and cancellation behavior |
| Risk | Hard per-trade and session loss limits from the portfolio mandate |
| Deployment | Positive held-out expectancy in the intended venue and session |
Scalping Techniques
1. Momentum Scalping
Enter on strong momentum candles on 1m, ride for small gain, exit immediately on momentum loss.
get_indicators(indicator_code="rsi", symbol=<symbol>, exchange=<exchange>, interval="1m")
get_indicators(indicator_code="macd", symbol=<symbol>, exchange=<exchange>, interval="1m")Define an objective closed-bar momentum trigger and exit. RSI/MACD are correlated price transforms; retain them only if they improve held-out net results over a price-only baseline.
2. Level Scalping
Quick bounces at key S/R levels with tight stops.
get_candles_around_date(symbol=<symbol>, exchange=<exchange>, interval="5m", date=<date>)Identify levels on the context timeframe, define a numerical rejection on the execution timeframe, and place invalidation beyond the level plus expected stop slippage. Require the planned payoff to remain positive after costs.
3. Range Scalping
Buy support, sell resistance within a defined micro-range. Repeat until range breaks.
get_indicators(indicator_code="dmi", symbol=<symbol>, exchange=<exchange>, interval="5m")Use a calibrated range classifier; ADX alone does not confirm a micro-range. Stop applying the rule when the closed-bar invalidation or liquidity gate fails.
Workflow
1. Confirm Direction on 5m
get_indicators(indicator_code="ema", symbol=<symbol>, exchange=<exchange>, interval="5m")
get_indicators(indicator_code="dmi", symbol=<symbol>, exchange=<exchange>, interval="5m")Establish bias from higher timeframe before scalping on 1m.
2. Identify Setup on 1m
get_candles_around_date(symbol=<symbol>, exchange=<exchange>, interval="1m", date=<date>)
get_indicators(indicator_code="rsi", symbol=<symbol>, exchange=<exchange>, interval="1m")Pick one technique (momentum, level, or range) based on current conditions.
3. Mark Key Levels
draw_chart_analysis(action="create", drawing={
"type": "support",
"points": [
{"time": <touch_1>, "price": <level>},
{"time": <touch_2>, "price": <level>}
],
"options": {"text": "Scalp Level"}
})4. Report to Orchestrator
Technique selected, timestamped quote, order type, expected fill, entry, invalidation, target, total cost estimate, capacity, and context-timeframe bias.
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: Barber et al. found aggregate day-trader performance was negative and persistent profitability rare, making net-of-cost evidence and strict loss limits essential.
Key Rules
- Exclude scheduled event windows unless a separately tested event strategy and mandate apply.
- Reject markets and order sizes that fail the spread, depth, fill-rate, latency, or cost gate.
- Exit on the predeclared invalidation; do not widen risk after entry.
- Enforce the mandate's session loss and order-rate limits; pause on feed, clock, or execution anomalies.
- Compare context-aligned and context-agnostic variants rather than assuming alignment adds edge.
- Do not deploy from win rate alone; require positive net expectancy and stable tail losses.
Related Skills
- range-trading -- range scalping is a micro-timeframe application of range principles
- momentum-trading -- momentum scalping borrows directional confirmation logic
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.

