Trader Broker
Order Executor.
Install
npx skills add Jakeschincariol/trader-skill --skill trader-broker -g -a claude-code -y- Repository
- Jakeschincariol/trader-skill1.1k
- Category
- AI and agents
- Updated
- 21d ago
- License
- MIT
- Context cost
- Mediumabout 1,914 tokens
- Runs scripts
- Yes, review before use
What it does
Order Executor. Places APPROVED orders through your brokerage connector, one at a time, and never without your explicit yes. Shows each order as a plain ticket 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. Covers setting up Alpaca's official MCP server in Claude Desktop (paper trading by default, keys in env vars, never in chat), the Interactive Brokers connector (orders go to your IBKR account for your approval), and setting order tools to "Needs approval". Use when the user says "place the orders", "buy it", "execute", "send it to my broker", "connect Alpaca", "connect Interactive Brokers", "set up paper trading", or after /trader-risk passes.
trader-broker
The Order Executor is the only skill in this pack that can lead to a real order, so it is the strictest. An order reaches the market only after three separate gates, every time, for every order:
- trader-risk passed this exact order today (matched by fingerprint).
- The user typed an explicit yes for this one order in the chat.
- The user clicked Allow once on Claude's own permission card, which appears because the order tool is set to "Needs approval".
Two yeses from the user, one PASS from the rules. No yes, no order.
${CLAUDE_SKILL_DIR} below is this skill's folder (where this SKILL.md lives).
python3 "${CLAUDE_SKILL_DIR}/ticket.py" show # every ticket, READY or not
python3 "${CLAUDE_SKILL_DIR}/ticket.py" approve --index 1 --reply "yes"
python3 "${CLAUDE_SKILL_DIR}/ticket.py" result --index 1 --status placed --broker-id ID
python3 "${CLAUDE_SKILL_DIR}/ticket.py" fill --symbol AAPL --side buy --qty 3.6628 --price 341.27
python3 "${CLAUDE_SKILL_DIR}/ticket.py" log
ticket.py never talks to a broker. It renders tickets, checks that a reply
is a real yes for that order, and keeps the log in trader/state/broker.json.
Setup A: Alpaca (official MCP server, Claude Desktop)
Alpaca's own server is github.com/alpacahq/alpaca-mcp-server (MIT). It runs on the user's computer inside Claude Desktop. It is not in Claude's connector directory. It trades on a paper account unless told otherwise.
