agentleFS
SKE-LabsSKE-Labs/agent-trading-skills/skills/risk-management/trailing-stop/SKILL.md

trailing-stop

Skill17 starsChanged 4 months agoApache-2.0View on GitHub

Lock in profits with dynamic trailing stop strategies. Use when riding winner trends, protecting open profits, or managing exits systematically.

1 other project uses a version of this, 1 of them edited.

Adopted by

Most recently taken up by

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

    Use a predeclared moving average and exit condition.

    line 26
  2. Distinctive:

    Test start conditions such as immediate, an R-multiple, elapsed bars, or a new objective swing.

    line 38
  3. Distinctive:

    Treat the setup as a testable hypothesis, not a prediction.

    line 64
  4. Distinctive:

    Never loosen the authorized trailing stop.

    line 73
  5. Distinctive:

    Do not override the rule using hindsight.

    line 76

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

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

Trailing Stop Strategies

Trailing stops lock in profits while allowing trades to run.

Trailing Methods

1. ATR Trail (Recommended)

Long example: Trailing Stop = Highest High - (ATR × multiplier); mirror for shorts. Declare ATR lookback, multiplier, update frequency, and whether intrabar or closed-bar highs apply.

2. Structure Trail

Move stop below each new swing low (long) or above each new swing high (short). Lets the trade breathe while locking in structure.

3. Moving Average Trail

Use a predeclared moving average and exit condition. Treat any period as a candidate parameter and prevent look-ahead by updating from available bars only.

4. Chandelier Exit

Trail from highest high by ATR multiple. Classic exit strategy, good for trending markets.

5. Fixed Distance Trail

Move stop by fixed amount (pips/%). Simple but can be too static -- prefer ATR or structure.

When to Start Trailing

Test start conditions such as immediate, an R-multiple, elapsed bars, or a new objective swing. These labels do not imply conservative/aggressive risk without the resulting payoff distribution.

Hybrid Approach

Combine methods for staged exit management:

  1. Fixed initial stop
  2. Optional, tested transition rule
  3. One precisely defined trailing method
  4. Time or terminal exit for any remaining quantity

Exit Scenarios

Price ActionTrailing Action
New high/lowMove stop up/down
ConsolidationKeep stop same
Predefined reversal triggerApply the specified update
Objective structure breakExit or update as predeclared

Workflow

For each bar or tick, update the high-water mark and stop exactly once under the chosen rule; never lower a long trail or raise a short trail. Record trigger price versus fill price and handle gaps, partial fills, halts, and venue-specific trailing-order semantics.

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 SEC stop-order bulletin explains trailing-stop mechanics and warns that short-term fluctuations can trigger an order and execution can differ from the stop.

Key Rules

  • Freeze lookbacks, multipliers, start condition, update clock, and terminal exit before entry.
  • Never loosen the authorized trailing stop; account for order replacement races.
  • Compare the trail against fixed-target, time-exit, and unchanged-stop baselines.
  • Model trigger/fill gaps, fees, stop-limit nonexecution, and partial fills.
  • Do not override the rule using hindsight; an emergency risk-off action must be logged separately.

Related Skills

  • stop-loss-strategies -- initial stop placement determines when trailing begins
  • partial-profit-taking -- combine trailing stops with partial exits for optimal capture

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.