Day Trader Skill install: Claude Code trading skill & four paths
TL;DR. This is the day trader skill install guide — including the Claude Code trading skill plugin path. Path A (paste URL) is fastest for Claude chat. Path B is for Claude Code plugins. Path C copies folders for plain
/trader-* commands. Path D pastes a single SKILL.md when you cannot install tools. Always set paper defaults and read the safety checklist before any broker connector. Source: upstream GitHub — this page is not the official site. Not financial advice.Not financial advice. Installing skills does not make day trading safe. Most people who day trade lose money. Keep paper trading as the default.
Before you start
- Claude account and/or Claude Code installed, depending on the path.
- Python 3.8+ on the machine that will run the helper scripts (
python3 --version). - Nothing mandatory to
pip installfor the upstream standard-library tools. - For SEC-facing tools (news filings / analyst), prepare a polite identity string:
Your Name you@example.comforSEC_USER_AGENTortrader/config.json. - Read Safety before enabling any brokerage MCP / connector.
Which path should I use?
| Path | Best when | Trade-off |
|---|---|---|
| A · Paste URL | You work in Claude chat and want the fewest steps | Depends on Claude’s current skill-install UX |
| B · Claude Code plugin | You already live in Claude Code / terminal agents | Commands are namespaced as /day-trader-skill:trader-… |
| C · Copy folders | You want plain /trader-scanner style names | You maintain updates with git pull + re-copy |
| D · Paste SKILL.md | No Claude Code; you only need the method text | You lose the Python tooling unless you run scripts yourself |
Path A — Paste the repo URL into Claude
- Open a Claude chat that supports skill install from a repository URL.
- Paste the upstream URL alone on a line:
https://github.com/Jakeschincariol/day-trader-skill
- On the next line, tell Claude to install the skill, for example:
install skill
- Confirm the skills appear (scanner, news, entry, …). If the UI asks for permissions, allow only what you understand — never blanket-approve brokerage tools.
- Still configure paper defaults and SEC identity before any live-looking connector. See Safety.
Path B — Claude Code plugin marketplace
- Open Claude Code in a terminal.
- Add the marketplace, then install the plugin:
/plugin marketplace add Jakeschincariol/day-trader-skill /plugin install day-trader-skill@day-trader-skill
- Expect namespaced commands such as
/day-trader-skill:trader-scanner. If a tutorial shows bare/trader-scanner, either adjust for the namespace or use Path C. - If a command “does nothing,” jump to the troubleshoot matrix.
Path C — Copy trader-* folders
- Clone the upstream repository (verify the org/name — forks are numerous):
git clone https://github.com/Jakeschincariol/day-trader-skill.git cd day-trader-skill
- Global Claude skills directory:
cp -r trader-* ~/.claude/skills/
- Or project-local (keeps skills with one repo):
mkdir -p .claude/skills cp -r trader-* .claude/skills/
- Restart / reload Claude Code if commands do not appear. You should get plain
/trader-scannerstyle names. - When upstream updates (if it does),
git pulland re-copy — or track staleness on changelog watch.
Path D — Paste a single SKILL.md
- Open any one skill folder on GitHub (for example
trader-scanner/SKILL.md). - Paste that markdown at the top of a Claude chat to run it as a mode / method prompt.
- Understand the limit: without the Python helpers you lose automated scan/news/sim scripts unless you run those files yourself from a clone.
- Still do not treat chat output as financial advice or as an approved order.
Python & SEC identity
Helper scripts expect Python 3.8 or newer. Upstream emphasizes standard-library code — no mandatory pip stack for the core tools described in the README.
Identify yourself for SEC endpoints, for example:
export SEC_USER_AGENT="Your Name you@example.com"
Or set sec_user_agent inside trader/config.json following upstream’s example config files. Be polite; do not hammer endpoints.
Smoke-test without placing anything
- From a clone, try a read-only style command documented upstream (for example listing a universe or checking entry status on a ticker) — not broker submit.
- Optional: run upstream unit tests offline if present:
python3 -m unittest discover -s tests -v - Walk the paper path on Paper trading before you ever consider a live connector.
Next: when install “works” but feels broken
Namespaced commands, missing Python, SEC 403s, sandboxes without network, and Always-allow mistakes are covered on the dedicated page: Install troubleshooting.