Day trading / execution
Order Executor
Shows the ticket in plain words and sends it only after you type yes. Paper by default.
Renders approved orders as readable tickets, requires an explicit yes for that exact order and talks to a brokerage connector with paper trading as the default.
- Default
- Paper
- Consent
- Required
- Auto trade
- Never
- Keys
- Env only
Live scene
Order Executor
git clone https://github.com/Jakeschincariol/day-trader-skill.gitMITOverview
What Order Executor actually does
The Order Executor is the only skill in the pack that can lead to an order, and it cannot do it alone. It shows the ticket in plain words, waits for you to type yes for that exact order, then calls your brokerage connector.
Paper trading is the default. Keys live in environment variables, never in the chat, and the connector should be set to require approval so there is a second check.
Capabilities
What it helps your agent ship
Render approved orders as plain-language tickets.
Mark each ticket READY or not ready.
Require an explicit yes for that exact order.
Default to paper trading.
Read broker keys from environment variables.
Never place options, margin, short or leverage unless enabled.
Workflow
The process the skill follows
A repeatable sequence keeps the agent from jumping straight into edits before it understands the job.
- 01
Load approved orders
Read only the orders that passed the risk manager.
- 02
Show the ticket
Render symbol, side, size, stop and target in plain words.
- 03
Ask for consent
Wait for an explicit yes for that exact order.
- 04
Call the connector
Send the order through the configured brokerage tool.
- 05
Confirm the result
Report the fill or the error, and keep paper as the default.
Inside the pack
References and modules
These are the load-on-demand files or command groups that make the skill useful beyond a single prompt.
ticket.py show
Display the tickets and their readiness.
Paper mode
True by default in the example config.
Brokerage connector
Alpaca MCP or another approved tool.
Consent gate
A typed yes for the exact ticket.
Environment keys
No secrets in chat or config.
Ticket state
READY only after the risk manager passes the order.
Use cases
Where it earns its place
Safe execution
A human approves every order before it leaves.
Paper practice
Rehearse the full chain without risking real money.
Ticket review
See the order in words before it reaches a broker.
Prompt starters
Try one of these first
Copy a prompt into your agent. Replace the example URL with your own project or page.
Show me the ticket for this order and wait for my yes.
Place this approved order in paper trading only.
Why is this ticket not READY?
Keep exploring
Related skills
Want a site that uses this skill properly?
We build Next.js websites with technical SEO, structured data, 3D scenes and motion that stays inside a performance budget.