Skills for Real Engineers. Straight from my .agents directory.
trader-broker
Agent skill fromJakeschincariol/day-trader-skill
Order Executor. Sends approved orders to your broker, paper trading by default, never without your yes. Shows each order as a plain ticket (a bracket shows its stop-loss, take-profit and the max loss at the stop) plus the exact JSON for Alpaca's place_stock_order, records your yes word for word, then Claude's own Allow once / Deny card asks again. Builds the sell ticket that closes a day trade by your flat-by time, records fills, and logs each trade's max loss so trader-risk can hold the daily limit. Covers setting up Alpaca's official MCP server in Claude Desktop (paper by default, keys in env vars, never in chat), the Interactive Brokers connector, and setting order tools to "Needs approval". Use when the user says "place the order", "buy it", "execute", "send it to my broker", "close my position", "flatten", "get me out", "connect Alpaca", "set up paper trading", or after /trader-risk passes.
How to install trader-broker
npx skills add Jakeschincariol/day-trader-skill# or add only this skill to Claude Code: copy the folder
trader-broker/
# into
~/.claude/skills/trader-broker/ (all projects)
.claude/skills/trader-broker/ (one project)
1# trader-broker23The Order Executor is the only skill in this pack that can lead to a real4order, so it is the strictest. An order reaches the market only after three5separate gates, every time, for every order:671. **trader-risk passed this exact order today** (matched by fingerprint).82. **The user typed an explicit yes for this one order** in the chat.93. **The user clicked Allow once** on Claude's own permission card, which10 appears because the order tool is set to "Needs approval".1112Two yeses from the user, one PASS from the rules. No yes, no order.1314`${CLAUDE_SKILL_DIR}` below is this skill's folder (where this SKILL.md lives).1516```bash17python3 "${CLAUDE_SKILL_DIR}/ticket.py" show # every ticket, READY or not18python3 "${CLAUDE_SKILL_DIR}/ticket.py" approve --index 1 --reply "yes"19python3 "${CLAUDE_SKILL_DIR}/ticket.py" result --index 1 --status placed --broker-id ID --filled-qty 8 --filled-price 364.2020python3 "${CLAUDE_SKILL_DIR}/ticket.py" fill --symbol TSLA --side sell --qty 8 --price 370.0421python3 "${CLAUDE_SKILL_DIR}/ticket.py" flatten --symbol TSLA --qty 822python3 "${CLAUDE_SKILL_DIR}/ticket.py" log23```2425`ticket.py` never talks to a broker. It renders tickets, checks that a reply26is a real yes for that order, builds the flatten ticket, and keeps the log in27`trader/state/broker.json`. `--now "2026-10-19 10:15"` pins the clock (New York time).2829## What it reads and writes3031| file | what |32| --- | --- |33…
Excerpt shown under the repository's MIT license.
More skills in day-trader-skill
Similar skill repositories
An agentic skills framework & software development methodology that works.
A single CLAUDE.md file to improve Claude Code behavior, derived from Andrej Karpathy's observations on LLM coding pitfalls.
Public repository for Agent Skills
Persistent Context Across Sessions for Every Agent – Captures everything your agent does during sessions, compresses it with AI, and injects relevant context back into future sessions. Works with Claude Code, OpenClaw, Codex, Gemini, Hermes, Copilot, OpenCode + More
Production-grade engineering skills for AI coding agents.
