Run Claude Trading Skills for investor market review and trade journaling
Use the Claude Trading Skills pack to run structured market-regime checks, portfolio reviews, swing-trade screens, trade journals, and performance retrospectives inside Claude workflows.
npx skills add agentskillexchange/skills --skill run-claude-trading-skills-for-investor-market-review-and-trade-journaling
Claude Trading Skills is a Claude Skills-based workflow toolkit for individual investors who want a disciplined review process rather than automated trading signals. An agent/operator uses its documented skill packages and workflow manifests to run daily market-regime checks, weekly core-portfolio reviews, swing-opportunity screening, trade journaling, and monthly performance review with explicit gates and artifacts.
What this skill actually does
Use this when a trader or investor wants Claude to structure research, risk review, position sizing, journaling, and post-trade learning from local files, screenshots, CSVs, and optional market-data integrations. Do not use it as a broker, signal service, automated trading bot, or investment adviser. The useful boundary is the repeatable decision-process workflow: Claude helps organize evidence and review discipline, while the user owns all trading decisions and external execution.
Inputs and prerequisites: Claude Skills or Claude Code, local portfolio/trading files, optional FMP/FINVIZ Elite/Alpaca data integrations depending on workflow.
Setup notes: Download the relevant .skill archive from skill-packages/ and upload it through Claude Settings -> Skills, or install the repository’s skills/workflows into Claude Code following the README and documentation site.
Source and verification boundary: use https://tradermonty.github.io/claude-trading-skills/ as the canonical reference before running the workflow; keep commands, API calls, CLI usage, and generated outputs reviewable against that upstream source.
Framework fit: publish this as a Claude Code workflow only when the operator can invoke the documented toolchain directly, rather than treating the upstream project as a generic product listing.