stop-loss-strategies
Skill36 starsChanged 8 months agoMITView on GitHub
Stop-loss placement strategies for NSE/BSE equity trades. Covers structure-based, ATR-based, support/resistance-based, and moving average-based stops with buffer rules and hard limits.
- Installs packages
We split this skill into the rules it gives an agent
6 rules. 0 are common, 5 are distinctive, and 1 is very specific to this project.
0
Common
Most of the 3 edited versions we read keep these.
5
Distinctive
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 18
No dependencies required. Provide entry price and key levels manually.
- Distinctive: line 54
Place stop just below a confirmed support level:
- Distinctive: line 59
Only use levels with at least 2 historical touches.
- Distinctive: line 73
Use closing price as trigger, not intraday wicks (unless day trading)
- Distinctive: line 74
Add extra buffer if the stock has a history of stop-hunting wicks
- Distinctive: line 85
No mental stops: Use actual stop-loss orders on Groww if possible, or set hard price alerts
“Common” is measured: kept by at least 6 in 10 of the 3 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Stop-Loss Strategies
A stop-loss is not optional. Every position needs one before entry. The purpose is to cap your maximum loss — not to predict where price will go.
Prerequisites
No dependencies required. Provide entry price and key levels manually. Enhanced with Groww MCP (candles, ATR, MAs) or yfinance (pip install yfinance).
Data Needed
- Entry price: Known or planned
- Recent candles:
fetch_historical_candle_data(daily, last 60 days) or user-provided levels - ATR(14):
get_historical_technical_indicatorsfrom Groww, or calculate manually - Key S/R levels: From technical-analysis skill or swing highs/lows
- Moving averages: SMA20, SMA50, SMA200
Stop Type Selection
| Method | Best For | How to Calculate |
| Structure-based | Swing trades, clear chart patterns | Below recent swing low (long) or above swing high (short) |
| ATR-based | Volatile stocks, no clear structure | Entry - ATR(14) × 1.5 to 2.0 |
| Support/Resistance | Range-bound markets, clear levels | Below key support level + buffer |
| Moving Average | Trend-following trades | Below SMA20 (aggressive) or SMA50 (conservative) |
Structure-Based (Preferred)
Find the most recent swing low (for longs) that, if broken, would invalidate your trade thesis.
Stop = Recent swing low - buffer
Buffer = 0.5% for large-caps, 1% for mid/small-capsATR-Based
Adapts to the stock's natural volatility:
Stop (long) = Entry - ATR(14) × multiplier
Stop (short) = Entry + ATR(14) × multiplier
Multiplier: 1.5 (tight) to 2.0 (standard) to 2.5 (loose)Support/Resistance-Based
Place stop just below a confirmed support level:
Stop = Support level × (1 - buffer%)
Buffer: 0.5% large-cap, 1.0% mid/small-capOnly use levels with at least 2 historical touches.
Moving Average-Based
For trend-following positions:
Aggressive: Stop below SMA20 (for short-term trends)
Moderate: Stop below SMA50 (for medium-term trends)
Conservative: Stop below SMA200 (for long-term holds)Best when MA is clearly sloping in your direction.
Buffer Rules
- Round stop to nearest Rs.5 or Rs.10 for cleaner levels
- Use closing price as trigger, not intraday wicks (unless day trading)
- Add extra buffer if the stock has a history of stop-hunting wicks
- For illiquid stocks (avg volume < 50K/day), use wider buffers (1.5-2%)
Hard Rules
These are non-negotiable:
- Max loss per trade: 2% of capital (1% if using leverage)
- Never move stop further away — only tighten or leave unchanged
- If stop hits: exit immediately at next open. No "let me wait for close"
- Pre-set the stop: Decide before entering. Don't adjust based on emotions after entry
- No mental stops: Use actual stop-loss orders on Groww if possible, or set hard price alerts
Stop Validation
Before finalizing, check:
- Is the stop beyond normal noise? (At least 1× ATR away from entry)
- Does the position size at this stop keep risk within limits?
- Is the R:R ratio still acceptable? (→ check with risk-reward-ratio skill)
- Is the stop below a meaningful technical level, not just a round number?
Other versions3 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 3
- SKE-Labs/agent-trading-skills★ 17same name
- Shubhamkumartrichy/claude-trading-skills-india★ 7same name
- IngAs8/ClaudeSkill★ 0same name
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 repository8 other files it gives its agents.
- fibonacci-tradingSkill
- multi-timeframe-analysisSkill
- nse-trading-toolkitSkill
- position-sizingSkill
- risk-reward-ratioSkill
- rsi-divergenceSkill
- technical-analysisSkill
- trailing-stopsSkill
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.

