
trader-exit
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.
- Installs
- 91
- Last 24h
- +16
- Trending rank
- #6726
- Security
- Not audited
Install
Works with every agent the skills CLI supports.
npx skills add https://github.com/jakeschincariol/day-trader-skill --skill trader-exit- 01
Install
Run the command in your project. The CLI asks which agents to install for.
- 02
Describe the task
Ask your agent for something this skill covers. It loads trader-exit automatically when relevant.
- 03
Review the result
The agent follows the SKILL.md steps, scripts and references bundled with the skill.
SKILL.md
The instructions your agent reads when the skill is triggered.
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
| file | what |
|---|---|
trader/entry.json | the trigger from trader-entry: symbol, entry price, time, bar, opening range |
trader/config.json | flat_by (15:55) and min_reward_risk (1.0: a note here, trader-risk enforces it) |
| Yahoo chart API | only for an atr:K stop: the session's bars up to the entry bar, free and unofficial |
trader/plan.json | with --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
| stop | where it goes |
|---|---|
or-mid | the opening-range midpoint (the default for an opening-range breakout) |
or-low | the opening-range low: wider, so fewer shares for the same max loss |
price:X | your price |
pct:X | X percent under the entry |
atr:K | K 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.
2Rby default;1R,1.5Rorprice:Xalso 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_byin 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
- Run it right after
/trader-entrytriggers. Before that,--entry PRICEplans ahead at the level you expect. - Use the default stop for an opening-range breakout unless the user names another. A level setup needs one: ask.
- 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. - If it refuses, say the reason and the fix (a wider stop, a farther target). Never loosen anything on your own.
- Say once that the stop is a plan, not a guarantee.
- Hand off to
/trader-timemachineto replay the plan, then/trader-budgetto size it to the max loss per trade. Offer/trader-alertsfor the stop, the target and the flat-by time. Claude can keepentry.py watchrunning in the background or on a/loopuntil 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.
FAQ
What does the trader-exit skill do?
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.
How do I install trader-exit?
Run npx skills add https://github.com/jakeschincariol/day-trader-skill --skill trader-exit in your project. The skills CLI detects the agents you use and copies the skill into the right folder. For Claude Code you can also place the skill folder at ~/.claude/skills/trader-exit/ (personal) or .claude/skills/trader-exit/ (project).
Which AI agents can use trader-exit?
Any agent that supports the open Agent Skills format (a folder with a SKILL.md file), including Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, Windsurf, Cline, OpenCode and more.
Is trader-exit safe to install?
No partner security audit is available yet. Skills can run commands and scripts, so read the SKILL.md and any bundled files before installing.
Who maintains trader-exit?
It is published by jakeschincariol in jakeschincariol/day-trader-skill. It has 91 recorded installs.
More from jakeschincariol/day-trader-skill
trader-scanner
jakeschincariol/day-trader-skill
Chart Scanner. Scans thousands of charts for setups: opening-range breakouts, flags, oversold bounces. Builds the list of US-listed common stocks, ordinary shares and ADRs from Nasdaq Trader's symbol directories, runs a pre-market scan of daily closes (20-day closing-high breakout, bull flag, reclaimed the 20-day average, oversold, oversold bounce) and an intraday opening-range breakout scan on 5-minute bars, then writes trader/watchlist.json for trader-news and trader-entry. Free Yahoo data, bar by bar. Use when the user says "scan the market", "find me setups", "what is breaking out", "opening range breakouts", "scan for bull flags", "oversold stocks", "pre-market scan", "build my watchlist", "what should I look at today", or at the start of a trading day before /trader-news.
trader-timemachine
jakeschincariol/day-trader-skill
Open the skill to read its SKILL.md instructions.
trader-analyst
jakeschincariol/day-trader-skill
The Earnings Analyst. Reads a company's reported numbers straight from SEC EDGAR (XBRL company facts from its 10-Qs and 10-Ks, plus the latest earnings 8-K and its press release) and sums up what changed: revenue, gross, operating and net margins, net income and diluted EPS, quarter by quarter, each against the same quarter a year earlier, with the trailing twelve months. Reads an earnings call transcript when you paste one. Use when the user says "how did Tesla's earnings look", "analyze the earnings", "what changed this quarter", "is revenue growing", "check the 10-Q", "compare margins", "sum up the call", "does it report this week", or before trading a stock around its earnings.
trader-entry
jakeschincariol/day-trader-skill
Open the skill to read its SKILL.md instructions.
trader-risk
jakeschincariol/day-trader-skill
Open the skill to read its SKILL.md instructions.
trader-news
jakeschincariol/day-trader-skill
Open the skill to read its SKILL.md instructions.
Popular code quality & workflow skills
grill-me
mattpocock/skills
A relentless interview to sharpen a plan or design.
improve-codebase-architecture
mattpocock/skills
Scan a codebase for deepening opportunities, present them as a visual HTML report, then grill through whichever one you pick.
handoff
mattpocock/skills
Compact the current conversation into a handoff document for another agent to pick up.
domain-modeling
mattpocock/skills
Build and sharpen a project's domain model. Use when discussing codebase terminology, writing or editing a GLOSSARY.md, or recording or editing an ADR.
codebase-design
mattpocock/skills
Shared vocabulary for designing deep modules. Use when the user wants to design or improve a module's interface, find deepening opportunities, decide where a seam goes, make code more testable or AI-navigable, or when another skill needs the deep-module vocabulary.
diagnosing-bugs
mattpocock/skills
Diagnosis loop for hard bugs and performance regressions. Use when the user says "diagnose"/"debug this", or reports something broken/throwing/failing/slow.