trader-risk
Agent skill fromJakeschincariol/trader-skill
Risk Manager. Checks every proposed order against your limits before it can reach the broker and blocks anything over them: blocked tickers, max order size, minimum order, max position percent after the fill, the cash buffer, margin, short sales, options and crypto (off unless allowed), malformed orders, duplicates and a daily order limit. Prints PASS or BLOCK with the reason for each order and records the verdicts so trader-broker only shows an order that passed. Use when the user says "check my orders", "is this safe", "risk check", "does this break my rules", "can I place this", or before /trader-broker, always.
How to install trader-risk
npx skills add Jakeschincariol/trader-skill# or add only this skill to Claude Code: copy the folder
trader-risk/
# into
~/.claude/skills/trader-risk/ (all projects)
.claude/skills/trader-risk/ (one project)
1# trader-risk23The Risk Manager is the gate between a proposal and the broker. Every order4written by trader-budget, trader-rebalance or trader-tax passes through it.5A BLOCK is final for that order: it does not go to the user for a yes, and6it does not go to the broker.78`${CLAUDE_SKILL_DIR}` below is this skill's folder (where this SKILL.md lives).910```bash11python3 "${CLAUDE_SKILL_DIR}/check.py" # trader/ files; writes trader/state/risk.json12python3 "${CLAUDE_SKILL_DIR}/check.py" --json13python3 "${CLAUDE_SKILL_DIR}/check.py" --no-write # look without recording14```1516## What it reads and writes1718| file | what |19| --- | --- |20| `trader/orders.json` | the proposed orders |21| `trader/config.json` | the limits (trader-budget ships `config.example.json`) |22| `trader/portfolio.json` | cash and holdings; if missing, a fresh account funded with the budget |23| `trader/prices.json` | needed to size share-count orders and value holdings |24| `trader/state/broker.json` | what was placed today, for duplicates and the daily limit |25| `trader/state/risk.json` | the verdicts it writes, with a fingerprint of each exact order |2627## The checks2829Orders are checked in file order, as if each passed order had filled, so a30batch that is fine order by order but breaks a rule together is caught.3132| check | blocks when |33| --- | --- |34…
Excerpt shown under the repository's MIT license.
