agentleFS
Kafish69Kafish69/ultimate-trader/skills/trader-exit/SKILL.md

trader-exit

Skill1 starsChanged 10 days agoMITView on GitHub

Exit Planner. Sets your stop and your target before you enter, so you know when to get out. Reads the entry from trader-entry (or a price you give), puts the stop at the opening-range midpoint by default (or the range low, your price, a percent, or a multiple of the ATR), rounds it down to the cent, and sets the target at 2R (or 1R, or your price). Refuses a stop at or above the entry, a target at or below it, or a stop too tight to survive the spread, and says why. Writes trader/plan.json for the Time Machine, the Budget Manager and Price Alerts. Long side only. Use when the user says "where's my stop", "set my stop and target", "plan the exit", "when do I get out", "stop loss", "what's my R", "risk reward", or right after /trader-entry triggers, before /trader-timemachine.

3 other projects use a version of this; 3 new projects in the last 4 weeks, against 0 the 4 before.

Adopted by

Surging: 3 new projects took it in the last 4 weeks, none the 4 weeks before.thin data

Week of Sep 13: 0 new projectsWeek of Sep 20: 0 new projectsWeek of Sep 27: 0 new projectsWeek of Oct 4: 0 new projectsWeek of Oct 11: 0 new projectsWeek of Oct 18: 2 new projectsWeek of Oct 25: 0 new projectsWeek of Nov 1: 1 new project
Sep 2026Oct 2026Nov 2026
New projects taking a version of this file each week, over the 8 weeks our latest run read: only 3 in all, so this is a hint, not a trend.

Most recently taken up by

The file

We split this skill into the rules it gives an agent

6 rules. About 0 are common, 4 are distinctive, and 2 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈4

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 2

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Run it right after /trader-entry triggers.

    line 75
  2. Distinctive:

    Use the default stop for an opening-range breakout unless the user names another.

    line 77
  3. Very specific:

    Run exit.py plan --write. Read back the entry, the stop and its rule, the target and its rule, the risk a share, reward:risk and flat by.

    line 79
  4. Distinctive:

    If it refuses, say the reason and the fix (a wider stop, a farther target).

    line 81
  5. Distinctive:

    Never move a stop further from the entry once the trade is on.

    line 111
  6. Distinctive:

    No options, margin, short selling or leverage unless the config allows it and the user confirms.

    line 131

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

trader-exit

The Exit Planner decides how a trade ends before it starts. The stop is where the setup has failed. The target is where you take what you came for. Both are set BEFORE the entry, written down and handed on, so nobody has to decide anything in the middle of a fast move. A stop is a plan, not a guarantee: a gap or a fast market can fill past it. Day trading loses most people money, and a neat plan does not change that.

${CLAUDE_SKILL_DIR} below is this skill's folder (where this SKILL.md lives).

python3 "${CLAUDE_SKILL_DIR}/exit.py" plan                          # trader/entry.json: midpoint stop, 2R target
python3 "${CLAUDE_SKILL_DIR}/exit.py" plan --stop or-mid --target 1R --write
python3 "${CLAUDE_SKILL_DIR}/exit.py" plan --stop atr:1.5           # needs the session's bars (Yahoo or --offline)
python3 "${CLAUDE_SKILL_DIR}/exit.py" plan --symbol TSLA --entry 364.18 --or-high 362.18 --or-low 354.47
python3 "${CLAUDE_SKILL_DIR}/exit.py" show                          # the current trader/plan.json

Other flags: --flat-by 15:55, --json, --now "2026-10-19 10:15" (New York time), --entry PRICE with a waiting entry.json to plan ahead, --setup level, --offline FILE (a saved Yahoo chart JSON for an ATR stop).

What it reads and writes

filewhat
trader/entry.jsonthe trigger from trader-entry: symbol, entry price, time, bar, opening range
trader/config.jsonflat_by (15:55) and min_reward_risk (1.0: a note here, trader-risk enforces it)
Yahoo chart APIonly for an atr:K stop: the session's bars up to the entry bar, free and unofficial
trader/plan.jsonwith --write: entry, stop and its rule, target and its R, risk a share, reward:risk, flat by. trader-timemachine, trader-budget and trader-alerts read it

Stops and targets

stopwhere it goes
or-midthe opening-range midpoint (the default for an opening-range breakout)
or-lowthe opening-range low: wider, so fewer shares for the same max loss
price:Xyour price
pct:XX percent under the entry
atr:KK times the 14-bar ATR under the entry, on the session's bars up to the entry bar. With fewer than 14 bars by then it averages all of them and says so

A level setup has no opening range to lean on, so it needs a stop you name.

  • Rounding. The stop rounds AWAY from the entry to the cent (down, for a long). Risk = entry minus stop. Target = entry + R x risk, rounded half up to the cent. 2R by default; 1R, 1.5R or price:X also work.
  • Refused, with the reason. A stop at or above the entry. A target at or below it. A risk under 0.05% of the price: too tight to survive the spread, normal wiggle would stop you out. An entry.json that has not triggered (unless you give --entry). A short: v2 plans longs only.
  • Flat by. 15:55 by default (or flat_by in the config). Out by then, win or lose, no overnight hold. On a 1:00 p.m. early close it moves up to 12:55. An entry at or after the flat-by time is refused.

Steps

  1. Run it right after /trader-entry triggers. Before that, --entry PRICE plans ahead at the level you expect.
  2. Use the default stop for an opening-range breakout unless the user names another. A level setup needs one: ask.
  3. Run exit.py plan --write. Read back the entry, the stop and its rule, the target and its rule, the risk a share, reward:risk and flat by.
  4. If it refuses, say the reason and the fix (a wider stop, a farther target). Never loosen anything on your own.
  5. Say once that the stop is a plan, not a guarantee.
  6. Hand off to /trader-timemachine to replay the plan, then /trader-budget to size it to the max loss per trade. Offer /trader-alerts for the stop, the target and the flat-by time. Claude can keep entry.py watch running in the background or on a /loop until a setup triggers, then come here.

Example: the reel

TSLA, Monday 2026-10-19. The entry is 364.18 at 10:15 AM (the 10:10 bar, bar 8) and the opening range is 354.47 to 362.18. exit.py plan --stop or-mid --target 1R --write:

Exit plan: TSLA long, Mon 2026-10-19, opening-range breakout on 5-minute bars
  Entry         $364.18 at 10:15 AM (bar 8)
  Stop          $358.32  opening-range midpoint: ($362.18 + $354.47) / 2 = $358.325, rounded down
  Target        $370.04  1R (one times the risk)
  Risk a share  $5.86 (1.61% of the entry)
  Reward:risk   1.0
  Flat by       15:55 ET, win or lose: no overnight hold

The default 2R target would be 364.18 + 2 x 5.86 = 375.90. trader-budget then sizes it: a $50 max loss per trade buys floor(50 / 5.86) = 8 shares.

Rules

  • The stop and the target are set before the entry, never after.
  • Never move a stop further from the entry once the trade is on.
  • Plain numbers only: entry, stop, target, risk a share, reward:risk. It never prints a P&L or a return.
  • Nothing here promises winning trades or money. A 1R target is not a prediction that the price gets there.
  • Long side only. v2 plans longs only.

What it never does

It never places an order, never sizes a position, never widens a stop to make a plan pass, and never calls a stop a guarantee.

Safety

  • Education and tooling, not financial advice. A PASS is a rules check, not a recommendation.
  • Paper trading by default ("paper": true). Going live is the user's own decision, in their own config.
  • Nothing in this pack places an order except trader-broker, and only when all three hold: trader-risk passed that exact order today, the user typed an explicit yes for that one order in the chat, and the user clicked Allow once on Claude's own card because the order tool is set to "Needs approval" (Customize > Connectors > tool permissions). Never set an order tool to "Always allow".
  • No options, margin, short selling or leverage unless the config allows it and the user confirms.
  • Broker keys live in environment variables or the Claude Desktop config, never in the chat.

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.