Risk sizing
Position size calculator
Account size, risk percentage, entry price, and stop distance become a suggested share count and position value.
Tools
Tools should support a process — not replace judgment
Guides to Claude skills, simulators, scanners, and the open-source Day Trader Skill pack. Every tool here is presented as software with limits. None of it is a signal service, a broker, or a promise of profit.
Needs approval: if a tool can reach an order path, keep a human confirmation and do not set it to Always allow. Paper trading remains the default.
Free · no login · no market data
Paper-first calculators
Two browser-only arithmetic tools for a written plan. Neither one connects to a broker, reads a quote, or places an order.
Payoff check
Risk-reward calculator
Entry, stop, and target become an R:R ratio, potential profit and loss, and a break-even hit rate before costs.
Practice record
Paper checklist and journal
A first-session checklist and a printable journal embedded in the paper trading guide. No account is created.
Tool guides
Start with the general skill setup, then choose a specific workflow only if it fits.
Setup guide
How to install Claude skills
A vendor-neutral walkthrough: repository install, Claude Code plugins, manual skill folders, permission checks, testing, updates, and removal.
Featured tool
Day Trader Skill install
Four install paths for the third-party Claude skills pack, plus Python and SEC identity notes. Independent guide; not the official project site.
Reference
The 11 skill modules
What each trader-* command does, what it reads, what it writes, and where the human approval gate sits.
Comparison
Claude trading tools compared
Workflow fit, broker reach, and update risk — compared without star-count theater or performance rankings.
Guardrail
Safety and approval gates
Paper default, typed confirmation, Needs approval, secret handling, and the claims this site refuses to make.
Before you install
A five-minute tool check
A tool can be useful and still be a bad fit. Check the source, the permissions, and the failure modes before you connect it to anything that matters.
For trading workflows, test on paper first. A tool that cannot explain its output, or that asks for blanket approval, is not a shortcut — it is a new risk.
- Who maintains it, and when was the last code push?
- Does it run code or make network requests?
- What permissions does it need, and can they be narrower?
- Does it require a typed confirmation before an order?
- Can you remove it cleanly and audit what it wrote?
Independence note.
Day Trader Skill is a third-party MIT project on GitHub. DayTraderSkill.com is an independent guide, not the official project site and not affiliated with its authors. Canonical source: github.com/Jakeschincariol/day-trader-skill.