From market-deep-analyst
Draft concise morning meeting notes summarizing overnight developments, trade ideas, and key events for coverage stocks. Designed for the 7am morning meeting format — tight, opinionated, actionable. Triggers on "morning note", "morning meeting", "what happened overnight", "trade idea", "morning call prep", or "daily note".
How this skill is triggered — by the user, by Claude, or both
Slash command
/market-deep-analyst:morning-noteThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Scan for relevant events across coverage universe:
Scan for relevant events across coverage universe:
Earnings & Guidance
News & Events
Market Context
Keep it tight — a morning note should be readable in 2 minutes:
[Date] Morning Note — [Analyst Name] [Sector Coverage]
Top Call: [Headline — the one thing PMs need to hear]
Overnight/Pre-Market Developments
Key Events Today
Trade Ideas (if any)
If a coverage company reported, provide a quick reaction:
| Metric | Consensus | Actual | Beat/Miss |
|---|---|---|---|
| Revenue | |||
| EPS | |||
| [Key metric] | |||
| Guidance |
Our Take: 2-3 sentences — is this good or bad for the stock? Does it change our thesis?
Action: Maintain / Upgrade / Downgrade rating? Adjust price target?
npx claudepluginhub bruce762/market-deep-analystGuides completion of development work by verifying tests, detecting environment, and presenting structured options for merge, PR, or cleanup.
Guides creation and editing of skills using test-driven development with pressure scenarios and subagents to verify agent compliance.
Dispatches multiple subagents concurrently for independent tasks without shared state. Use when facing 2+ unrelated failures or subsystems that can be investigated in parallel.
4plugins reuse this skill
First indexed Jun 3, 2026