agentleFS
ShubhamkumartrichyShubhamkumartrichy/claude-trading-skills-india/skills/trailing-stops/SKILL.md

trailing-stops

Skill64 starsChanged 16 days agoMITView on GitHub

Trailing-stop plans that lock in profit on NSE/BSE positions: the R-multiple ladder (hold → breakeven at 1R → ATR trail at 2R → structure trail at 3R+), plus ATR, structure, moving-average and chandelier trails, with GTT/SL execution realities for Indian brokers. risk.py trail computes the recommended ratcheted stop.

1 other project uses a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

3 rules. About 0 are common, 2 are distinctive, and 1 is very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈2

    Distinctive · estimate

    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
  1. Distinctive:

    Before results, Budget or RBI policy days, tighten to the 1.5 × ATR level or book partial profits.

    line 56
  2. Very specific:

    Tax-aware trailing: if a delivery position is a few weeks from turning long-term (over 12 months), a slightly looser trail may be worth it …

    line 58
  3. Distinctive:

    Don't overtighten: a trail closer than about 1 ATR gets hit by ordinary pullbacks.

    line 65

≈ “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.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Trailing Stops

Trail to protect open profit while giving the trend room. The stop only moves in the trade's favour.

Calculator

python3 ../position-sizing/scripts/risk.py trail --entry 750 --stop 720 --highest-close 845 \
    --atr 14 --swing-low 805 --highest-high 850 --sma20 812 --current-stop 760

It reports R gained, the ladder stage, every candidate level, and the recommended stop (never below --current-stop). Get ATR, SMA20/EMA50 and the latest swing low from ta.py summary.

The R-multiple ladder (default)

1R = entry − initial stop.

StageOpen profitStop ruleWhy
Fresh0 – 1RKeep the initial stopTrailing early gets shaken out by noise
Early≥ 1RMove to breakeven (entry; add costs for true breakeven)The trade can no longer lose money
Building≥ 2RHighest close − 1.5 × ATR(14)Gives room while banking most of the move
Runner≥ 3RBelow the latest higher low (structure)Follows the trend's own rhythm

Take the highest qualifying level (the tightest) and never lower it.

Individual methods

MethodRuleBest for
ATR trailHighest close − k × ATR (k 1.5 tight / 2 standard / 3 loose)Trending but volatile stocks
StructureBelow each new higher lowClean stair-step trends
MA trailDaily close below SMA20 (fast) / EMA50 (steady) / SMA200 (positional) → exitSmooth grinders
ChandelierHighest high − 3 × ATRExplosive runners, momentum names
Partial + trailBook 30–50% at 2R or the 127.2% Fib, trail the restResults-season or event-heavy names

Execution in India

  • Update daily after the close using the official close (30-min VWAP), not intraday wicks. Modify the GTT for delivery holdings, or re-place the SL each morning because SL orders expire daily.
  • For F&O positions, trail on the underlying or futures chart and execute with SL-limit orders. Brokers' old bracket/cover orders with trailing are largely discontinued.
  • Before results, Budget or RBI policy days, tighten to the 1.5 × ATR level or book partial profits. A gap can jump past any trail.
  • Tax-aware trailing: if a delivery position is a few weeks from turning long-term (over 12 months), a slightly looser trail may be worth it because the tax rate drops from 20% to 12.5%. Quantify it with indian-tax-for-traders.

Rules

  1. A ratchet: up only (longs), down only (shorts).
  2. Evaluate on daily closes; exit in the closing session or at the next open when breached.
  3. Don't overtighten: a trail closer than about 1 ATR gets hit by ordinary pullbacks.
  4. Choose the method before the trade and stick to it.

Output

Gained: x.xR → stage: [..]
Candidates: breakeven ₹.. | ATR(1.5x) ₹.. | structure ₹.. | chandelier ₹.. | SMA20 ₹..
New stop: ₹S (locks +y.yR) → update GTT trigger ₹S / limit ₹S−b
Next review: after today's close; event risk: [results on dd-mmm]

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.