Activate when Cowork is opened and watchlist monitoring cadence has elapsed. Activate when user says "check my watchlist", "what's new on my watchlist", "run watchlist", "any updates", "watchlist digest", or configures monitoring via /curiosity-stack:watchlist command. Do NOT activate on every session — check last_run date in local.md first.
From curiosity-stacknpx claudepluginhub ameya85/curiosity-stackThis skill uses the workspace's default tool permissions.
Provides UI/UX resources: 50+ styles, color palettes, font pairings, guidelines, charts for web/mobile across React, Next.js, Vue, Svelte, Tailwind, React Native, Flutter. Aids planning, building, reviewing interfaces.
Fetches up-to-date documentation from Context7 for libraries and frameworks like React, Next.js, Prisma. Use for setup questions, API references, and code examples.
Calculates TAM/SAM/SOM using top-down, bottom-up, and value theory methodologies for market sizing, revenue estimation, and startup validation.
Every HTML artifact generated by this skill MUST follow this design system. No exceptions. Never invent colours, never use dark backgrounds, never use purple or blue as primary backgrounds.
Palette:
#fafaf8 (warm white)white#2c2c2c (soft charcoal)#6b6b6b#9a9690#1b5e52 (deep teal) — the ONLY accent colour#e0ddd6#f0f7f4#fff8f0 background, #f0d090 border, #5a3a00 textTypography:
'Georgia', serif, 14px minimum'Courier New', monospaceComponent rules:
background: #1b5e52; color: whitebackground: white; border: 1px solid #e0ddd6; border-radius: 8pxbackground: #1b5e52; color: white for primary actionsPill colour system:
background:#e6f1fb; color:#0c447c; border:0.5px solid #85b7ebbackground:#eaf3de; color:#27500a; border:0.5px solid #97c459background:#faeeda; color:#633806; border:0.5px solid #ef9f27background:#fcebeb; color:#791f1f; border:0.5px solid #f09595background:#f3f4f6; color:#374151; border:0.5px solid #d1d5dbbackground:#eaf3de; color:#27500abackground:#e6f1fb; color:#0c447cAttribution footer — mandatory on every artifact:
<div style="margin-top:32px;padding-top:12px;border-top:1px solid #e0ddd6;
display:flex;justify-content:space-between;align-items:center;
font-family:'Courier New',monospace;font-size:10px;color:#9a9690">
<span>Not SEBI registered · Not investment advice · For research only</span>
<a href="https://curiositystack.app" target="_blank"
style="color:#1b5e52;font-weight:700;text-decoration:none">
⬡ curiositystack.app
</a>
</div>
A scheduled research monitoring agent. Runs automatically when Cowork is opened and the user's set cadence has elapsed. Monitors every item on the watchlist for material developments, maps findings to value chain layers, scores materiality, and delivers a digest to email (default) and surfaces it in Cowork.
This plugin cannot write directly to local.md during a session due to Cowork's file system sandbox. Instead, after any configuration change, generate the exact YAML block the user needs to paste and instruct them clearly:
Your watchlist has been configured. To save this permanently,
open curiosity-stack.local.md and paste the following under
watchlist_topics:
[exact YAML block]
Open the file with:
Windows: notepad "C:\path\curiosity-stack.local.md"
Mac: open -e ~/path/curiosity-stack.local.md
Save and close. I'll read it on your next session.
Always generate the complete YAML block — never partial. Never ask the user to write YAML manually.
Before doing anything, silently read local.md:
watchlist_last_run datewatchlist_cadence (daily / weekly / fortnightly)For each item in the user's watchlist, run parallel research across all signal types the user has prioritised:
Signal types:
Research sources:
Per item, for each signal found:
After broad research, check each item's specific triggers:
If a trigger condition is met:
CURIOSITY STACK — WATCHLIST DIGEST
[Daily / Weekly / Fortnightly] | [Date]
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
🚨 TRIGGERS FIRED
[Only if any triggers met]
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
[TOPIC 1] — [HIGH / MEDIUM / LOW]
Layer affected: L[X] — [layer name]
Signal type: [News / Regulatory / New Entrant / Funding]
What happened:
[2-3 lines — factual, specific]
Why it matters:
[2-3 lines — how this changes or doesn't change the thesis]
Thesis impact: [Strengthens / Weakens / Neutral / Watch]
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
[TOPIC with no material change]
No material developments this period. ⚪
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
Open Cowork to go deeper → claude.ai/cowork
Plugin: Curiosity Stack by Ameya Pimpalgaonkar
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
⬡ Curiosity Stack · #CuriosityStack
finstor85.substack.com
Not investment advice. Research purposes only.
Email delivery (default):
Use Gmail MCP connector.
Subject: Curiosity Stack — [Cadence] Digest | [Date] | [X] updates
If triggers fired: prepend 🚨 to subject.
Cowork surface (always):
Watchlist digest ready — [X] updates, [Y] triggers fired.
[View digest] or [Skip for now]
After running, generate the update block:
Update your curiosity-stack.local.md — paste this:
watchlist_last_run: [today's date]
/curiosity-stack:watchlist CommandYour Watchlist
Monitoring: [cadence] | Last run: [date] | Next run: [date]
Email digest: [on/off] → [email]
Tracked topics:
→ [topic 1] — [X triggers set] — last: [HIGH/MEDIUM/LOW/none]
→ [topic 2] — [X triggers set] — last: [HIGH/MEDIUM/LOW/none]
Options:
1. Add topic
2. Remove topic
3. Add / edit trigger
4. Change cadence
5. Toggle email digest
6. View last digest
7. View digest archive
After any configuration change, generate the complete YAML block for the user to paste into local.md.
watchlist_cadence: daily / weekly / fortnightly
watchlist_last_run: [date]
watchlist_email: [email]
watchlist_email_enabled: true / false
watchlist_cowork_summary: true / false
session_count: 0
watchlist_topics:
- name: [topic]
added: [date]
last_status: HIGH / MEDIUM / LOW / none
signal_priorities:
- news
- regulatory
- new_entrants
- funding
triggers:
- layer: L[X]
condition: "[plain language condition]"
last_fired: [date or never]
Never show raw YAML to the user. Always render the watchlist as an interactive HTML artifact. YAML is generated silently in the background only when the user clicks "Generate YAML to save" or confirms changes.
Tab 1 — Topics Each topic is a collapsible card showing:
Tab 2 — Schedule & delivery
"Add topic" button → fires sendPrompt('Add a new topic to my watchlist') Claude responds with topic confirmation, then re-renders the full UI with the new topic expanded
Adding a trigger inline → updates the UI immediately, no chat needed
Save button → fires sendPrompt() to confirm, then shows "Saved ✓" for 2.5 seconds. Also generates the YAML block silently.
YAML is NEVER shown unless user explicitly clicks "Generate YAML to save" on the Schedule tab. Even then, show it in a code block below the UI, not instead of it.
Removing a topic → removes the card immediately from UI, fires sendPrompt() to confirm removal
When the watchlist agent detects a trigger condition:
Use the same category colours as the scenario library: