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

stop-loss-strategies

Skill17 starsChanged 4 months agoApache-2.0View on GitHub

Place strategic stop losses using structure, ATR, or volatility methods. Use when protecting capital, defining trade invalidation, or managing downside risk.

3 other projects use 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

8 rules. 0 are common, 8 are distinctive, and 0 are very specific to this project.

  • 0

    Common

    Most of the 3 edited versions we read keep these.

  • 8

    Distinctive

    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:

    Place below swing low (long) or above swing high (short).

    line 18
  2. Distinctive:

    Place beyond (not at) key S/R zones.

    line 26
  3. Distinctive:

    Place below key MA (20, 50, or 200).

    line 30
  4. Distinctive:

    Stop distance must follow the setup's invalidation and executable volatility/liquidity, not a universal percentage for a trade label.

    line 36
  5. Distinctive:

    Breakeven Stop: Treat moving to entry as one candidate management rule.

    line 46
  6. Distinctive:

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

    line 60
  7. Distinctive:

    Never widen total authorized loss after entry without a separately approved risk decision.

    line 69
  8. Distinctive:

    Do not assume round-number placement is inferior.

    line 70

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

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

Stop Loss Strategies

Proper stop placement protects capital while giving trades room to work.

Stop Loss Methods

1. Structure-Based (Recommended)

Place below swing low (long) or above swing high (short). Respects market structure with a clear invalidation point.

2. ATR-Based

Long example: Stop = Entry - (ATR × Multiplier); mirror for shorts. Select the ATR estimator and multiplier in training data and freeze them.

3. Support/Resistance Based

Place beyond (not at) key S/R zones. Below support for longs, above resistance for shorts.

4. Moving Average Based

Place below key MA (20, 50, or 200). Dynamic stop level, good for trend following.

5. Percentage-Based

Fixed % below entry. Simple but ignores structure -- use only as a position sizing limit.

Stop distance must follow the setup's invalidation and executable volatility/liquidity, not a universal percentage for a trade label. Recalculate quantity whenever the stop changes.

Buffer Rules

Define the buffer in ticks, spread, and/or ATR and calibrate it by instrument, session, and order type. The purpose is to represent noise and execution uncertainty; do not infer a "stop hunt" from a stopped order.

Stop Management

Initial Stop: Set at entry based on analysis. Based on the invalidation point for the trade thesis.

Breakeven Stop: Treat moving to entry as one candidate management rule. It is not risk-free after fees, spread, gaps, and slippage; compare it with the unchanged initial stop out of sample.

Trailing Stop: Locks in profits as the trade progresses (see trailing-stop skill).

Workflow

  1. Identify invalidation -- the price level where the trade thesis is wrong
  2. Choose method -- structure-based for most setups, ATR-based for volatile assets
  3. Add buffer -- use the prevalidated tick/volatility and execution buffer
  4. Choose order mechanics -- stop-market prioritizes execution; stop-limit controls price but may not fill; confirm venue trigger source
  5. Manage -- follow the predeclared static, breakeven, time, or trailing rule

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 warns that a stop price is a trigger, not a guaranteed execution price, while stop-limit orders may not execute.

Key Rules

  • Define invalidation, order type, trigger source, buffer, and quantity before entry.
  • Never widen total authorized loss after entry without a separately approved risk decision.
  • Do not assume round-number placement is inferior; test any clustering/buffer hypothesis.
  • Model gap-through, halt, rejected order, stop-limit nonexecution, and slippage risk.
  • Recalculate quantity and portfolio risk whenever the effective stop changes.

Related Skills

  • trailing-stop -- manages exits after initial stop is set
  • position-sizing -- stop distance is a direct input to position size calculation

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.