Check proposed stock orders against configured limits for loss, reward versus risk, position size, trading hours, and account rules. Get a PASS or BLOCK with reasons recorded for the exact order before it can be shown for broker execution.
Risk Manager. Checks every trade against your limits and stops anything over them, before it can reach the broker. For a day trade: a stop is required, the loss at the stop must fit your max loss per trade (measured from the higher of the plan's entry and a fresh price), reward:risk must meet your minimum, the day's total risk must fit your daily loss limit, no more than your trades per day, and no new entries outside your entry window or when the market is closed. It also keeps the basics: blocked tickers, order size, position cap, cash buffer, margin, short sales, options and crypto, malformed or bad bracket orders, duplicates and a daily order limit. Getting out is never blocked by a day limit. Prints PASS or BLOCK with the reason and records the verdicts so trader-broker only shows an order that passed. Use when the user says "check my order", "is this safe", "risk check", "does this break my rules", "can I take this trade", "how much have I risked today", or before /trader-broker, always.
Run score Not tested
See how to installReview the instructions the agent will receive before you install.
The Risk Manager is the gate between a proposal and the broker. Every order written by trader-budget or trader-broker's flatten passes through it. A BLOCK is final for that order: it does not go to the user for a yes, and it does not go to the broker. Most people who day trade lose money. These limits keep each loss and each day's losses small. They do not make a trade win.
${CLAUDE_SKILL_DIR} below is this skill's folder (where this SKILL.md lives).
python3 "${CLAUDE_SKILL_DIR}/check.py" # trader/ files; writes trader/state/risk.json
python3 "${CLAUDE_SKILL_DIR}/check.py" --json
python3 "${CLAUDE_SKILL_DIR}/check.py" --no-write # look without recording
python3 "${CLAUDE_SKILL_DIR}/check.py" --now "2026-10-19 10:15" # pin the clock (New York time)
| file | what |
|---|---|
trader/orders.json | the proposed orders (trader-budget, or trader-broker's flatten) |
trader/config.json | the limits (trader-budget ships config.example.json) |
trader/portfolio.json | cash and holdings; if missing, a fresh account funded with the budget |
trader/prices.json | a fresh price raises the entry it measures risk from; also values holdings |
trader/state/broker.json | what was placed today: duplicates, trades per day, daily loss, day trades |
trader/state/risk.json | the verdicts it writes, with a fingerprint of each exact order |
An entry opens or adds to a position: a buy, or a sell that would go short. An exit only reduces what you already hold. Getting out must always be possible, so an exit is checked for format, asset and short sales only. Every other rule (day limits, entry window, loss, reward:risk, blocked list, size, duplicates) turns into a warning for an exit, never a BLOCK.
Orders are checked in file order, as if each passed order had filled, so a batch that is fine order by order but breaks a limit together is caught.
| check | blocks when |
|---|---|
| format | no symbol, side not buy or sell, both or neither of qty and notional, a notional order that is not market + day (Alpaca's rule), a limit order with no limit price; a bracket that is not whole shares, not day or gtc, or misses its stop-loss or take-profit |
| asset | an option symbol while allow_options is false; crypto or anything that is not a US stock or ETF ticker |
| short | a sell of more than you hold (allow_short false) |
| blocked | (entries) the ticker is on the blocked list |
| size | (entries) under min_order_usd or over max_order_usd |
| position | (entries) the stock would be over max_position_pct of the account |
| cash | (entries) the buy would leave less than the cash buffer, or need margin |
| stop | (entries) no stop while require_stop is true (a bracket stop_loss_stop_price, or the order's plan stop); a stop on the wrong side of the entry |
| loss | (entries) qty x (entry minus stop) over max_loss_per_trade_usd |
| reward:risk | (entries) (target minus entry) / (entry minus stop) under min_reward_risk |
| daily loss | (entries) the max losses at the stops of today's entries, plus this one, over max_daily_loss_usd |
| trades | (entries) max_trades_per_day entries already placed today |
| window | (entries) before no_entries_before or after no_entries_after, or the market is closed |
| pdt | (entries, only with pdt_guard true) 3 day trades already in the last 5 business days |
| duplicate | (entries) the same symbol and side twice in one batch, or already placed today |
| daily limit | (entries) max_orders_per_day orders already placed today |
How the numbers work:
trader/prices.json (under 15 minutes old). A plan written at 10:15 cannot
understate the risk at 10:55 after the price ran up. An older price is not
used, and it says so.no_entries_* to null to switch the window off.pdt_guard on if yours does.Warnings do not block, but say them to the user: a LIVE account, a number sent as a number instead of a string, a stop that lives only in the plan and not at the broker, a price too old to use, an early close today.
alerts.py quote TSLA --write).check.py. Exit code 0 means every order passed, 1 means at least one
was blocked.The TSLA bracket from trader-budget at 10:15 AM on Monday 2026-10-19, on a fresh $5,000 paper account with the example config:
PASS #1 buy TSLA 8 shares, entry
entry 364.18 (the plan's entry), stop 358.32, target 370.04: risk 5.86 a share
max loss $46.88 (limit $50), reward:risk 1.00 (min 1)
today before this: 0 of 3 trades, $0 of $150 daily loss
1 passed, 0 blocked at 2026-10-19 10:15 New York. Cash after the passed orders: $2,086.56 (paper account).
One more share and it is blocked:
BLOCK #1 buy TSLA 9 shares, entry
entry 364.18 (the plan's entry), stop 358.32, target 370.04: risk 5.86 a share
max loss $52.74 (limit $50), reward:risk 1.00 (min 1)
today before this: 0 of 3 trades, $0 of $150 daily loss
- loss: 9 shares x 5.86 risk a share = $52.74 at the stop, over your $50 max loss per trade
The same 8 shares checked at 10:55 with the real 10:52 quote (366.48) in
trader/prices.json are blocked twice: 8 x 8.16 = $65.28 at the stop, and
reward:risk 0.44. At 9:40 they are blocked by the window (no new entries
before 9:45). The 3:55 PM sell that closes the position passes, even though
it is after the 3:30 entry cutoff: it is an exit.
It never places an order, never edits an order to make it pass, never loosens a limit, never blocks a sell that only gets the user out, and never treats a PASS as the user's yes.
"paper": true). Going live is the user's own decision, in their own config.No reviews yet. Tell others what you thought.
No login needed. Share how it worked for you, ask a question, or note where it did not run.
No comments yet. Be the first to write one.
Set one-time alerts for price levels, stop and target levels, percentage moves, scheduled times, and the NYSE opening bell. It can create stop, target, and flat-by-close alerts from a trade plan, check delayed quotes, and save prices for sizing and risk checks.
Review a company’s SEC filings to compare quarterly revenue, income, margins, and diluted EPS with the same quarter a year earlier, plus trailing twelve-month figures. Use an earnings release for context and summarize a pasted call transcript.
Prepare and present broker order tickets, record the user’s explicit yes, and track order results and fills. The workflow uses paper trading by default and requires a separate permission approval before an order is sent.
Calculate whole-share position size from a trade plan, budget, and configured limits for loss, position value, order size, and cash buffer. See which limit determines the size and get one proposed bracket order; the skill does not place it.
Watch a stock setup bar by bar and get the time and closing price when a completed 1- or 5-minute bar moves above an opening-range high or a level you specify. It can check volume and save the signal for exit planning; it never places an order.
Plan a long trade’s stop and target before entry using a trigger from trader-entry or a price you provide. Choose stop and target rules, review per-share risk and reward-to-risk, and save the plan for related tools. It does not place orders.