trade

Extract trade details from a command and enrich logs with portfolio context.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/robinlllll/claude-code-skills --skill trade
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: trade
Source: https://github.com/robinlllll/claude-code-skills/tree/main/trade
Command: npx skills add https://github.com/robinlllll/claude-code-skills --skill trade

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Logs trades with minimal friction during market hours, capturing execution details, rationale, and references for later review.

Core Features & Use Cases

  • Quick trade logging during market hours with minimal friction.
  • Automatic enrichment of logs with current portfolio context and thesis checks.
  • Post-trade checks and auto-task creation to maintain a decision trail.

Quick Start

Use the /trade command to log a trade quickly, e.g., /trade BUY AAPL 100 @ 185.50 "AI thesis".

Frequently Asked Questions about trade

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I log executed trades quickly during market hours?

You can log executed trades rapidly during market hours by issuing a command like /trade BUY AAPL 100 @ 185.50 "thesis", which extracts action, ticker, quantity, price, and rationale for deterministic markdown logging.

How does automated trade logging handle portfolio context and risk management?

Automated trade logging cross-references current portfolio data, thesis presence, and position histories to enrich logs, ensuring consistency and supporting risk management without manual data entry.

Can I use markdown trade logs for post-trade checks and auto-task creation?

Yes, the skill performs automated post-trade checks on markdown logs, maintaining a decision trail by offering optional thesis updates and auto-task creation for follow-up actions.

Does rapid trade logging require manual entry of investment thesis details?

No, rapid trade logging extracts the rationale directly from your command string, automatically checking it against existing portfolio context and position histories to maintain consistency.

What is the best way to maintain a decision trail for active portfolio positions?

The best way is using automated post-trade checks that log execution details and rationale, perform thesis presence validation, and create auto-tasks, ensuring a consistent decision trail for later review.

Are there limitations when logging trades outside of active market hours?

The skill is designed to operate within market hours to cross-reference current portfolio data accurately; logging outside this window may lack real-time context enrichment and immediate post-trade validation.