Stats
Actions
Tags
From Slatemark
Run a Pre-Trade Brief on $ARGUMENTS using the connected Slatemark tools.
How this command is triggered — by the user, by Claude, or both
Slash command
/slatemark:pre-trade-briefThe summary Claude sees in its command listing — used to decide when to auto-load this command
Run a Pre-Trade Brief on $ARGUMENTS using the connected Slatemark tools. If no horizon is given, assume a swing (multi-day to multi-week) view and say so explicitly. Decompose across tools and hand back one brief, not a blurb: - the multi-week trend with key support and resistance, ATR, and recent volume profile; - the next catalyst on the calendar and how the name has reacted to that event historically; - today's options skew and the 30-day IV percentile; - the macro backdrop framing the window. Always close with the invalidation level: where does the thesis break, and what would co...
Run a Pre-Trade Brief on $ARGUMENTS using the connected Slatemark tools. If no horizon is given, assume a swing (multi-day to multi-week) view and say so explicitly.
Decompose across tools and hand back one brief, not a blurb:
Always close with the invalidation level: where does the thesis break, and what would confirm versus reject a hold of the key level? This is an open analysis the user takes into their own decision, never a recommendation to buy or sell.
npx claudepluginhub pdassoc-io/slatemark-plugin --plugin slatemark