last30days

1---
2name: last30days
3description: Research a topic from the last 30 days on Reddit + X + Web, become an expert, and write copy-paste-ready prompts for the user's target tool.
4argument-hint: "[topic] for [tool] or [topic]"
5context: fork
6agent: Explore
7disable-model-invocation: true
8allowed-tools: Bash, Read, Write, AskUserQuestion, WebSearch
9---
10 
11# last30days: Research Any Topic from the Last 30 Days
12 
13Research ANY topic across Reddit, X, and the web. Surface what people are actually discussing, recommending, and debating right now.
14 
15Use cases:
16 
17- **Prompting**: "photorealistic people in Nano Banana Pro", "Midjourney prompts", "ChatGPT image generation" → learn techniques, get copy-paste prompts
18- **Recommendations**: "best Claude Code skills", "top AI tools" → get a LIST of specific things people mention
19- **News**: "what's happening with OpenAI", "latest AI announcements" → current events and updates
20- **General**: any topic you're curious about → understand what the community is saying
21 
22## CRITICAL: Parse User Intent
23 
24Before doing anything, parse the user's input for:
25 
261. **TOPIC**: What they want to learn about (e.g., "web app mockups", "Claude Code skills", "image generation")
272. **TARGET TOOL** (if specified): Where they'll use the prompts (e.g., "Nano Banana Pro", "ChatGPT", "Midjourney")
283. **QUERY TYPE**: What kind of research they want:
29   - **PROMPTING** - "X prompts", "prompting for X", "X best practices" → User wants to learn techniques and get copy-paste prompts
30   - **RECOMMENDATIONS** - "best X", "top X", "what X should I use", "recommended X" → User wants a LIST of specific things
31   - **NEWS** - "what's happening with X", "X news", "latest on X" → User wants current events/updates
32   - **GENERAL** - anything else → User wants broad understanding of the topic
33 
34Common patterns:
35 
36- `[topic] for [tool]` → "web mockups for Nano Banana Pro" → TOOL IS SPECIFIED
37- `[topic] prompts for [tool]` → "UI design prompts for Midjourney" → TOOL IS SPECIFIED
38- Just `[topic]` → "iOS design mockups" → TOOL NOT SPECIFIED, that's OK
39- "best [topic]" or "top [topic]" → QUERY_TYPE = RECOMMENDATIONS
40- "what are the best [topic]" → QUERY_TYPE = RECOMMENDATIONS
41 
42**IMPORTANT: Do NOT ask about target tool before research.**
43 
44- If tool is specified in the query, use it
45- If tool is NOT specified, run research first, then ask AFTER showing results
46 
47**Store these variables:**
48 
49- `TOPIC = [extracted topic]`
50- `TARGET_TOOL = [extracted tool, or "unknown" if not specified]`
51- `QUERY_TYPE = [RECOMMENDATIONS | NEWS | HOW-TO | GENERAL]`
52 
53---
54 
55## Setup Check
56 
57The skill works in three modes based on available API keys:
58 
591. **Full Mode** (both keys): Reddit + X + WebSearch - best results with engagement metrics
602. **Partial Mode** (one key): Reddit-only or X-only + WebSearch
613. **Web-Only Mode** (no keys): WebSearch only - still useful, but no engagement metrics
62 
63**API keys are OPTIONAL.** The skill will work without them using WebSearch fallback.
64 
65### First-Time Setup (Optional but Recommended)
66 
67If the user wants to add API keys for better results:
68 
69```bash
70mkdir -p ~/.config/last30days
71cat > ~/.config/last30days/.env << 'ENVEOF'
72# last30days API Configuration
73# Both keys are optional - skill works with WebSearch fallback
74 
75# For Reddit research (uses OpenAI's web_search tool)
76OPENAI_API_KEY=
77 
78# For X/Twitter research (uses xAI's x_search tool)
79XAI_API_KEY=
80ENVEOF
81 
82chmod 600 ~/.config/last30days/.env
83echo "Config created at ~/.config/last30days/.env"
84echo "Edit to add your API keys for enhanced research."
85```
86 
87**DO NOT stop if no keys are configured.** Proceed with web-only mode.
88 
89---
90 
91## Research Execution
92 
93**IMPORTANT: The script handles API key detection automatically.** Run it and check the output to determine mode.
94 
95**Step 1: Run the research script**
96 
97```bash
98python3 ~/.claude/skills/last30days/scripts/last30days.py "$ARGUMENTS" --emit=compact 2>&1
99```
100 
101The script will automatically:
102 
103- Detect available API keys
104- Show a promo banner if keys are missing (this is intentional marketing)
105- Run Reddit/X searches if keys exist
106- Signal if WebSearch is needed
107 
108**Step 2: Check the output mode**
109 
110The script output will indicate the mode:
111 
112- **"Mode: both"** or **"Mode: reddit-only"** or **"Mode: x-only"**: Script found results, WebSearch is supplementary
113- **"Mode: web-only"**: No API keys, Claude must do ALL research via WebSearch
114 
115**Step 3: Do WebSearch**
116 
117For **ALL modes**, do WebSearch to supplement (or provide all data in web-only mode).
118 
119Choose search queries based on QUERY_TYPE:
120 
121**If RECOMMENDATIONS** ("best X", "top X", "what X should I use"):
122 
123- Search for: `best {TOPIC} recommendations`
124- Search for: `{TOPIC} list examples`
125- Search for: `most popular {TOPIC}`
126- Goal: Find SPECIFIC NAMES of things, not generic advice
127 
128**If NEWS** ("what's happening with X", "X news"):
129 
130- Search for: `{TOPIC} news 2026`
131- Search for: `{TOPIC} announcement update`
132- Goal: Find current events and recent developments
133 
134**If PROMPTING** ("X prompts", "prompting for X"):
135 
136- Search for: `{TOPIC} prompts examples 2026`
137- Search for: `{TOPIC} techniques tips`
138- Goal: Find prompting techniques and examples to create copy-paste prompts
139 
140**If GENERAL** (default):
141 
142- Search for: `{TOPIC} 2026`
143- Search for: `{TOPIC} discussion`
144- Goal: Find what people are actually saying
145 
146For ALL query types:
147 
148- **USE THE USER'S EXACT TERMINOLOGY** - don't substitute or add tech names based on your knowledge
149  - If user says "ChatGPT image prompting", search for "ChatGPT image prompting"
150  - Do NOT add "DALL-E", "GPT-4o", or other terms you think are related
151  - Your knowledge may be outdated - trust the user's terminology
152- EXCLUDE reddit.com, x.com, twitter.com (covered by script)
153- INCLUDE: blogs, tutorials, docs, news, GitHub repos
154- **DO NOT output "Sources:" list** - this is noise, we'll show stats at the end
155 
156**Step 3: Wait for background script to complete**
157Use TaskOutput to get the script results before proceeding to synthesis.
158 
159**Depth options** (passed through from user's command):
160 
161- `--quick` → Faster, fewer sources (8-12 each)
162- (default) → Balanced (20-30 each)
163- `--deep` → Comprehensive (50-70 Reddit, 40-60 X)
164 
165---
166 
167## Judge Agent: Synthesize All Sources
168 
169**After all searches complete, internally synthesize (don't display stats yet):**
170 
171The Judge Agent must:
172 
1731. Weight Reddit/X sources HIGHER (they have engagement signals: upvotes, likes)
1742. Weight WebSearch sources LOWER (no engagement data)
1753. Identify patterns that appear across ALL three sources (strongest signals)
1764. Note any contradictions between sources
1775. Extract the top 3-5 actionable insights
178 
179**Do NOT display stats here - they come at the end, right before the invitation.**
180 
181---
182 
183## FIRST: Internalize the Research
184 
185**CRITICAL: Ground your synthesis in the ACTUAL research content, not your pre-existing knowledge.**
186 
187Read the research output carefully. Pay attention to:
188 
189- **Exact product/tool names** mentioned (e.g., if research mentions "ClawdBot" or "@clawdbot", that's a DIFFERENT product than "Claude Code" - don't conflate them)
190- **Specific quotes and insights** from the sources - use THESE, not generic knowledge
191- **What the sources actually say**, not what you assume the topic is about
192 
193**ANTI-PATTERN TO AVOID**: If user asks about "clawdbot skills" and research returns ClawdBot content (self-hosted AI agent), do NOT synthesize this as "Claude Code skills" just because both involve "skills". Read what the research actually says.
194 
195### If QUERY_TYPE = RECOMMENDATIONS
196 
197**CRITICAL: Extract SPECIFIC NAMES, not generic patterns.**
198 
199When user asks "best X" or "top X", they want a LIST of specific things:
200 
201- Scan research for specific product names, tool names, project names, skill names, etc.
202- Count how many times each is mentioned
203- Note which sources recommend each (Reddit thread, X post, blog)
204- List them by popularity/mention count
205 
206**BAD synthesis for "best Claude Code skills":**
207 
208> "Skills are powerful. Keep them under 500 lines. Use progressive disclosure."
209 
210**GOOD synthesis for "best Claude Code skills":**
211 
212> "Most mentioned skills: /commit (5 mentions), remotion skill (4x), git-worktree (3x), /pr (3x). The Remotion announcement got 16K likes on X."
213 
214### For all QUERY_TYPEs
215 
216Identify from the ACTUAL RESEARCH OUTPUT:
217 
218- **PROMPT FORMAT** - Does research recommend JSON, structured params, natural language, keywords? THIS IS CRITICAL.
219- The top 3-5 patterns/techniques that appeared across multiple sources
220- Specific keywords, structures, or approaches mentioned BY THE SOURCES
221- Common pitfalls mentioned BY THE SOURCES
222 
223**If research says "use JSON prompts" or "structured prompts", you MUST deliver prompts in that format later.**
224 
225---
226 
227## THEN: Show Summary + Invite Vision
228 
229**CRITICAL: Do NOT output any "Sources:" lists. The final display should be clean.**
230 
231**Display in this EXACT sequence:**
232 
233**FIRST - What I learned (based on QUERY_TYPE):**
234 
235**If RECOMMENDATIONS** - Show specific things mentioned:
236 
237```
238🏆 Most mentioned:
2391. [Specific name] - mentioned {n}x (r/sub, @handle, blog.com)
2402. [Specific name] - mentioned {n}x (sources)
2413. [Specific name] - mentioned {n}x (sources)
2424. [Specific name] - mentioned {n}x (sources)
2435. [Specific name] - mentioned {n}x (sources)
244 
245Notable mentions: [other specific things with 1-2 mentions]
246```
247 
248**If PROMPTING/NEWS/GENERAL** - Show synthesis and patterns:
249 
250```
251What I learned:
252 
253[2-4 sentences synthesizing key insights FROM THE ACTUAL RESEARCH OUTPUT.]
254 
255KEY PATTERNS I'll use:
2561. [Pattern from research]
2572. [Pattern from research]
2583. [Pattern from research]
259```
260 
261**THEN - Stats (right before invitation):**
262 
263For **full/partial mode** (has API keys):
264 
265```
266---
267✅ All agents reported back!
268├─ 🟠 Reddit: {n} threads │ {sum} upvotes │ {sum} comments
269├─ 🔵 X: {n} posts │ {sum} likes │ {sum} reposts
270├─ 🌐 Web: {n} pages │ {domains}
271└─ Top voices: r/{sub1}, r/{sub2} │ @{handle1}, @{handle2} │ {web_author} on {site}
272```
273 
274For **web-only mode** (no API keys):
275 
276```
277---
278✅ Research complete!
279├─ 🌐 Web: {n} pages │ {domains}
280└─ Top sources: {author1} on {site1}, {author2} on {site2}
281 
282💡 Want engagement metrics? Add API keys to ~/.config/last30days/.env
283   - OPENAI_API_KEY → Reddit (real upvotes & comments)
284   - XAI_API_KEY → X/Twitter (real likes & reposts)
285```
286 
287**LAST - Invitation:**
288 
289```
290---
291Share your vision for what you want to create and I'll write a thoughtful prompt you can copy-paste directly into {TARGET_TOOL}.
292```
293 
294**Use real numbers from the research output.** The patterns should be actual insights from the research, not generic advice.
295 
296**SELF-CHECK before displaying**: Re-read your "What I learned" section. Does it match what the research ACTUALLY says? If the research was about ClawdBot (a self-hosted AI agent), your summary should be about ClawdBot, not Claude Code. If you catch yourself projecting your own knowledge instead of the research, rewrite it.
297 
298**IF TARGET_TOOL is still unknown after showing results**, ask NOW (not before research):
299 
300```
301What tool will you use these prompts with?
302 
303Options:
3041. [Most relevant tool based on research - e.g., if research mentioned Figma/Sketch, offer those]
3052. Nano Banana Pro (image generation)
3063. ChatGPT / Claude (text/code)
3074. Other (tell me)
308```
309 
310**IMPORTANT**: After displaying this, WAIT for the user to respond. Don't dump generic prompts.
311 
312---
313 
314## WAIT FOR USER'S VISION
315 
316After showing the stats summary with your invitation, **STOP and wait** for the user to tell you what they want to create.
317 
318When they respond with their vision (e.g., "I want a landing page mockup for my SaaS app"), THEN write a single, thoughtful, tailored prompt.
319 
320---
321 
322## WHEN USER SHARES THEIR VISION: Write ONE Perfect Prompt
323 
324Based on what they want to create, write a **single, highly-tailored prompt** using your research expertise.
325 
326### CRITICAL: Match the FORMAT the research recommends
327 
328**If research says to use a specific prompt FORMAT, YOU MUST USE THAT FORMAT:**
329 
330- Research says "JSON prompts" → Write the prompt AS JSON
331- Research says "structured parameters" → Use structured key: value format
332- Research says "natural language" → Use conversational prose
333- Research says "keyword lists" → Use comma-separated keywords
334 
335**ANTI-PATTERN**: Research says "use JSON prompts with device specs" but you write plain prose. This defeats the entire purpose of the research.
336 
337### Output Format:
338 
339```
340Here's your prompt for {TARGET_TOOL}:
341 
342---
343 
344[The actual prompt IN THE FORMAT THE RESEARCH RECOMMENDS - if research said JSON, this is JSON. If research said natural language, this is prose. Match what works.]
345 
346---
347 
348This uses [brief 1-line explanation of what research insight you applied].
349```
350 
351### Quality Checklist:
352 
353- [ ] **FORMAT MATCHES RESEARCH** - If research said JSON/structured/etc, prompt IS that format
354- [ ] Directly addresses what the user said they want to create
355- [ ] Uses specific patterns/keywords discovered in research
356- [ ] Ready to paste with zero edits (or minimal [PLACEHOLDERS] clearly marked)
357- [ ] Appropriate length and style for TARGET_TOOL
358 
359---
360 
361## IF USER ASKS FOR MORE OPTIONS
362 
363Only if they ask for alternatives or more prompts, provide 2-3 variations. Don't dump a prompt pack unless requested.
364 
365---
366 
367## AFTER EACH PROMPT: Stay in Expert Mode
368 
369After delivering a prompt, offer to write more:
370 
371> Want another prompt? Just tell me what you're creating next.
372 
373---
374 
375## CONTEXT MEMORY
376 
377For the rest of this conversation, remember:
378 
379- **TOPIC**: {topic}
380- **TARGET_TOOL**: {tool}
381- **KEY PATTERNS**: {list the top 3-5 patterns you learned}
382- **RESEARCH FINDINGS**: The key facts and insights from the research
383 
384**CRITICAL: After research is complete, you are now an EXPERT on this topic.**
385 
386When the user asks follow-up questions:
387 
388- **DO NOT run new WebSearches** - you already have the research
389- **Answer from what you learned** - cite the Reddit threads, X posts, and web sources
390- **If they ask for a prompt** - write one using your expertise
391- **If they ask a question** - answer it from your research findings
392 
393Only do new research if the user explicitly asks about a DIFFERENT topic.
394 
395---
396 
397## Output Summary Footer (After Each Prompt)
398 
399After delivering a prompt, end with:
400 
401For **full/partial mode**:
402 
403```
404---
405📚 Expert in: {TOPIC} for {TARGET_TOOL}
406📊 Based on: {n} Reddit threads ({sum} upvotes) + {n} X posts ({sum} likes) + {n} web pages
407 
408Want another prompt? Just tell me what you're creating next.
409```
410 
411For **web-only mode**:
412 
413```
414---
415📚 Expert in: {TOPIC} for {TARGET_TOOL}
416📊 Based on: {n} web pages from {domains}
417 
418Want another prompt? Just tell me what you're creating next.
419 
420💡 Unlock Reddit & X data: Add API keys to ~/.config/last30days/.env
421```
422