New: Earn 20% as an AgentAlley affiliate. Share your link and earn on every sale you refer. Join now New: Earn 20% as an affiliate. Join now

Searches Reddit, X/Twitter

Last 30 days research

by mohitagw15856 · MIT license · ★ 1,395 on GitHub · updated Sep 23

Last 30 days research cover

Searches Reddit, X/Twitter, and the broader web for recent opinions, sentiment, and signal on any topic. Use when you need to know what real people are saying about a tool, product, trend, or event in the past 30 days — cutting through…

---
name: last-30-days-research
description: "Searches Reddit, X/Twitter, and the broader web for recent opinions, sentiment, and signal on any topic. Use when you need to know what real people are saying about a tool, product, trend, or event in the past 30 days — cutting through SEO content to surface genuine community reaction. Produces a structured report with consensus findings, pain points, positive signals, contrarian takes, source links, and a signal confidence rating."
---

# Last 30 Days Research

## The Problem

Googling gives SEO-stuffed "best of" lists written six months ago by someone who has never used the thing. Real honest takes live on Reddit threads, X replies, and niche communities — but chasing them across platforms eats your afternoon. This skill does the chase for you.

## Required Inputs

| Input | Required | Notes |
|-------|----------|-------|
| Topic | Yes | Tool, trend, feature, product, event, company — anything with a name |
| Date scope | No | Defaults to last 30 days. Can override to last 7 days or last 90 days |
| Angle | No | e.g. "focus on developer sentiment" or "looking for pricing complaints specifically" |

Overview

Googling gives SEO-stuffed "best of" lists written six months ago by someone who has never used the thing. Real honest takes live on Reddit threads, X replies, and niche communities — but chasing them across platforms eats your afternoon. This skill does the chase for you.

Manual install (npx, ZIP)
Claude Codenpx skills add mohitagw15856/pm-claude-skills --skill last-30-days-research -g -a claude-code
Claude Code (manual)mkdir -p ~/.claude/skills && curl -sL https://codeload.github.com/mohitagw15856/pm-claude-skills/tar.gz/f6ca79348c55 \ | tar -xz -C ~/.claude/skills --strip-components=2 pm-claude-skills-f6ca79348c55/skills/last-30-days-research
Windows (PowerShell)New-Item -ItemType Directory -Force "$HOME\.claude\skills" | Out-Null; Invoke-WebRequest "https://m.agentalley.io/zip/a9037fb811143ba4e18f/last-30-days-research.zip" -OutFile "$env:TEMP\last-30-days-research.zip"; Expand-Archive "$env:TEMP\last-30-days-research.zip" -DestinationPath "$HOME\.claude\skills" -Force
Claude.ai / desktopDownload the ZIP and upload it under Settings → Capabilities → Skills.
Codex, Cursor, other agentsPoint them at SKILL.md. The other files are plain text.

Connects with Agent Alley MCP · agentalley.io/mcp

Files included

  • SKILL.md7.3 KB
Read the files here
mohitagw15856/f6ca7931 file
SKILL.md
Show the full text159 lines

Last 30 Days Research

The Problem

Googling gives SEO-stuffed "best of" lists written six months ago by someone who has never used the thing. Real honest takes live on Reddit threads, X replies, and niche communities — but chasing them across platforms eats your afternoon. This skill does the chase for you.

Required Inputs

Input Required Notes
Topic Yes Tool, trend, feature, product, event, company — anything with a name
Date scope No Defaults to last 30 days. Can override to last 7 days or last 90 days
Angle No e.g. "focus on developer sentiment" or "looking for pricing complaints specifically"

Output Structure

The output is a structured research report with the following sections, delivered in this exact order:

## Last 30 Days Research: [Topic]
Research window: [Date 30 days ago] → [Today's date]

---

## What People Agree On
[Consensus points that appear across multiple platforms — most reliable signal]

## Where People Disagree
[Active debates, contrasting views — include which side has more weight]

## Pain Points That Keep Coming Up
[Recurring complaints and frustrations — strongest signal of real problems]

## Positive Signals
[What people genuinely praise — not PR, but unprompted appreciation]

## Most Interesting Takes
[Contrarian, unexpected, or surprisingly insightful comments worth noting]

## Sources
[Links to the most useful threads/posts found — 5–10 links with brief labels]

## Signal Confidence
[High / Medium / Low — with a one-line rationale based on data volume and consistency]

Each section should contain substantive content, not placeholders. If a section has no findings (e.g. no positive signals found), state that explicitly rather than leaving it empty or fabricating content.

Instructions for Claude

Step 1 — Calculate the date window

Determine today's date and subtract 30 days to get the research start date. Format: YYYY-MM-DD. Use these dates explicitly in every search query.

Run at least three web searches targeting Reddit:

site:reddit.com "[topic]" after:[30-days-ago-date]
site:reddit.com "[topic]" 2025
reddit.com "[topic]" discussion OR thread OR comments

For each result: read the thread title, top-level comments, and any highly-upvoted replies. Record the key claims and the URL.

If the topic has common synonyms or abbreviations, run additional searches with those (e.g. "Claude Code" and "claude.code" and "Anthropic coding tool").

Run at least two web searches targeting X:

site:twitter.com OR site:x.com "[topic]" after:[30-days-ago-date]
"[topic]" site:x.com -is:retweet

Note: X search via web has limitations. If results are sparse, supplement with searches for specific accounts known to discuss the topic area (e.g. tech journalists, domain experts).

Run at least two broader searches for articles, blog posts, and commentary:

"[topic]" review OR opinion OR experience [month] [year]
"[topic]" vs OR alternative OR comparison [month] [year]

Target sources: Hacker News, Substack, dev.to, personal blogs, product communities. Avoid press releases and vendor-authored content.

Step 5 — Cross-platform corroboration check

Before writing the report, review everything collected and apply the corroboration rule:

When the same point appears on both Reddit and X independently, treat it as strong signal — it's likely true.

A point mentioned only once on one platform is a data point, not a finding. Weight your sections accordingly.

Step 6 — Write the report

Populate each section of the output structure. Follow these rules:

  • What People Agree On: Only include points you saw on 2+ platforms or in multiple independent threads. These are your most reliable findings.
  • Where People Disagree: Name the sides. "Some say X, others say Y — and the X camp seems louder based on upvote counts / engagement."
  • Pain Points: Be specific. "Performance issues" is weak. "Cold start times over 4 seconds on the free tier" is useful.
  • Positive Signals: Must be unprompted praise, not from product marketing or sponsored content.
  • Most Interesting Takes: At least 2, maximum 5. Quote or closely paraphrase where possible.
  • Sources: Include the actual URLs. Label each one briefly (e.g. "Reddit thread: 'Has anyone switched from X to Y?'").
  • Signal Confidence: Rate High/Medium/Low based on:
    • High = 10+ sources, consistent signal across platforms
    • Medium = 5–10 sources, some inconsistency
    • Low = fewer than 5 sources, or highly fragmented signal
Step 7 — Sanity check before delivering

Before outputting the report, verify:

  • Every claim in the report traces to an actual source found during research (not prior knowledge)
  • The date window was actually applied to searches, not ignored
  • No fabricated or hallucinated URLs in the Sources section
  • Signal Confidence rating reflects the actual data volume, not optimism

Quality Checks

  • At minimum 3 Reddit searches were run with the date filter applied
  • At minimum 2 X/Twitter searches were run
  • At minimum 2 broader web searches were run
  • Cross-platform corroboration principle was applied (same point on multiple platforms = stronger signal)
  • Pain Points section contains specific, concrete details — not vague generalisations
  • Sources section contains real URLs (not hallucinated), verified during research
  • Signal Confidence is rated and justified
  • If a section has no findings, it says so explicitly rather than being omitted or padded
  • No vendor-authored content or press releases treated as independent signal
  • Synonyms and alternative names for the topic were searched

Anti-Patterns

  • Do not treat SEO blog posts or vendor-authored content as community signal — only count independent sources
  • Do not report findings without applying the date filter — prior knowledge mixed with recent search results produces stale, unverifiable claims
  • Do not fabricate or guess at URLs — every link in the Sources section must have been retrieved during the research session
  • Do not report a single mention as a "finding" — a finding requires corroboration from at least two independent sources
  • Do not rate Signal Confidence as High when fewer than 5 credible sources were found — this misleads the reader about how much to rely on the output

Example Trigger Phrases

  • "What are people saying about Cursor AI from the last 30 days?"
  • "Research Vercel's recent sentiment"
  • "Last 30 days on the Arc browser shutdown"
  • "What's the current vibe on Supabase?"
  • "What are developers saying about Claude Code lately?"
  • "Research [topic] from the last 30 days"
  • "Give me a signal report on [product]"
  • "What's the Reddit and Twitter take on [trend]?"
1---
2name: last-30-days-research
3description: "Searches Reddit, X/Twitter, and the broader web for recent opinions, sentiment, and signal on any topic. Use when you need to know what real people are saying about a tool, product, trend, or event in the past 30 days — cutting through SEO content to surface genuine community reaction. Produces a structured report with consensus findings, pain points, positive signals, contrarian takes, source links, and a signal confidence rating."
4---
5 
6# Last 30 Days Research
7 
8## The Problem
9 
10Googling gives SEO-stuffed "best of" lists written six months ago by someone who has never used the thing. Real honest takes live on Reddit threads, X replies, and niche communities — but chasing them across platforms eats your afternoon. This skill does the chase for you.
11 
12## Required Inputs
13 
14| Input | Required | Notes |
15|-------|----------|-------|
16| Topic | Yes | Tool, trend, feature, product, event, company — anything with a name |
17| Date scope | No | Defaults to last 30 days. Can override to last 7 days or last 90 days |
18| Angle | No | e.g. "focus on developer sentiment" or "looking for pricing complaints specifically" |
19 
20## Output Structure
21 
22The output is a structured research report with the following sections, delivered in this exact order:
23 
24```
25## Last 30 Days Research: [Topic]
26Research window: [Date 30 days ago] → [Today's date]
27 
28---
29 
30## What People Agree On
31[Consensus points that appear across multiple platforms — most reliable signal]
32 
33## Where People Disagree
34[Active debates, contrasting views — include which side has more weight]
35 
36## Pain Points That Keep Coming Up
37[Recurring complaints and frustrations — strongest signal of real problems]
38 
39## Positive Signals
40[What people genuinely praise — not PR, but unprompted appreciation]
41 
42## Most Interesting Takes
43[Contrarian, unexpected, or surprisingly insightful comments worth noting]
44 
45## Sources
46[Links to the most useful threads/posts found — 5–10 links with brief labels]
47 
48## Signal Confidence
49[High / Medium / Low — with a one-line rationale based on data volume and consistency]
50```
51 
52Each section should contain substantive content, not placeholders. If a section has no findings (e.g. no positive signals found), state that explicitly rather than leaving it empty or fabricating content.
53 
54## Instructions for Claude
55 
56### Step 1 — Calculate the date window
57 
58Determine today's date and subtract 30 days to get the research start date. Format: YYYY-MM-DD. Use these dates explicitly in every search query.
59 
60### Step 2 — Reddit search
61 
62Run at least three web searches targeting Reddit:
63 
64```
65site:reddit.com "[topic]" after:[30-days-ago-date]
66site:reddit.com "[topic]" 2025
67reddit.com "[topic]" discussion OR thread OR comments
68```
69 
70For each result: read the thread title, top-level comments, and any highly-upvoted replies. Record the key claims and the URL.
71 
72If the topic has common synonyms or abbreviations, run additional searches with those (e.g. "Claude Code" and "claude.code" and "Anthropic coding tool").
73 
74### Step 3 — X/Twitter search
75 
76Run at least two web searches targeting X:
77 
78```
79site:twitter.com OR site:x.com "[topic]" after:[30-days-ago-date]
80"[topic]" site:x.com -is:retweet
81```
82 
83Note: X search via web has limitations. If results are sparse, supplement with searches for specific accounts known to discuss the topic area (e.g. tech journalists, domain experts).
84 
85### Step 4 — Broader web search
86 
87Run at least two broader searches for articles, blog posts, and commentary:
88 
89```
90"[topic]" review OR opinion OR experience [month] [year]
91"[topic]" vs OR alternative OR comparison [month] [year]
92```
93 
94Target sources: Hacker News, Substack, dev.to, personal blogs, product communities. Avoid press releases and vendor-authored content.
95 
96### Step 5 — Cross-platform corroboration check
97 
98Before writing the report, review everything collected and apply the corroboration rule:
99 
100**When the same point appears on both Reddit and X independently, treat it as strong signal — it's likely true.**
101 
102A point mentioned only once on one platform is a data point, not a finding. Weight your sections accordingly.
103 
104### Step 6 — Write the report
105 
106Populate each section of the output structure. Follow these rules:
107 
108- **What People Agree On**: Only include points you saw on 2+ platforms or in multiple independent threads. These are your most reliable findings.
109- **Where People Disagree**: Name the sides. "Some say X, others say Y — and the X camp seems louder based on upvote counts / engagement."
110- **Pain Points**: Be specific. "Performance issues" is weak. "Cold start times over 4 seconds on the free tier" is useful.
111- **Positive Signals**: Must be unprompted praise, not from product marketing or sponsored content.
112- **Most Interesting Takes**: At least 2, maximum 5. Quote or closely paraphrase where possible.
113- **Sources**: Include the actual URLs. Label each one briefly (e.g. "Reddit thread: 'Has anyone switched from X to Y?'").
114- **Signal Confidence**: Rate High/Medium/Low based on:
115 - High = 10+ sources, consistent signal across platforms
116 - Medium = 5–10 sources, some inconsistency
117 - Low = fewer than 5 sources, or highly fragmented signal
118 
119### Step 7 — Sanity check before delivering
120 
121Before outputting the report, verify:
122 
123- [ ] Every claim in the report traces to an actual source found during research (not prior knowledge)
124- [ ] The date window was actually applied to searches, not ignored
125- [ ] No fabricated or hallucinated URLs in the Sources section
126- [ ] Signal Confidence rating reflects the actual data volume, not optimism
127 
128## Quality Checks
129 
130- [ ] At minimum 3 Reddit searches were run with the date filter applied
131- [ ] At minimum 2 X/Twitter searches were run
132- [ ] At minimum 2 broader web searches were run
133- [ ] Cross-platform corroboration principle was applied (same point on multiple platforms = stronger signal)
134- [ ] Pain Points section contains specific, concrete details — not vague generalisations
135- [ ] Sources section contains real URLs (not hallucinated), verified during research
136- [ ] Signal Confidence is rated and justified
137- [ ] If a section has no findings, it says so explicitly rather than being omitted or padded
138- [ ] No vendor-authored content or press releases treated as independent signal
139- [ ] Synonyms and alternative names for the topic were searched
140 
141## Anti-Patterns
142 
143- [ ] Do not treat SEO blog posts or vendor-authored content as community signal — only count independent sources
144- [ ] Do not report findings without applying the date filter — prior knowledge mixed with recent search results produces stale, unverifiable claims
145- [ ] Do not fabricate or guess at URLs — every link in the Sources section must have been retrieved during the research session
146- [ ] Do not report a single mention as a "finding" — a finding requires corroboration from at least two independent sources
147- [ ] Do not rate Signal Confidence as High when fewer than 5 credible sources were found — this misleads the reader about how much to rely on the output
148 
149## Example Trigger Phrases
150 
151- "What are people saying about Cursor AI from the last 30 days?"
152- "Research Vercel's recent sentiment"
153- "Last 30 days on the Arc browser shutdown"
154- "What's the current vibe on Supabase?"
155- "What are developers saying about Claude Code lately?"
156- "Research [topic] from the last 30 days"
157- "Give me a signal report on [product]"
158- "What's the Reddit and Twitter take on [trend]?"
159 
View all files on GitHub →

Details

Updated
Sep 23, 2026
License
MIT
Stars on the repo
★ 1,395
Checked
Source
mohitagw15856/pm-claude-skills ↗
Creator
mohitagw15856 · 193 listings
View creator

Made with last-30-days-research

Last 30 days research — Galaxy 3D — fly through all 1170 skills as a glowing constellation you orbit and click into (from the mohitagw15856/pm-claude-skills README)
Last 30 days research — Galaxy 3D — fly through all 1170 skills as a glowing constellation you orbit and click into (from the mohitagw15856/pm-claude-skills README)

by mohitagw15856

Last 30 days research — PM Skills Wrapped — your practice turned into a shareable, Spotify-Wrapped-style story (from the mohitagw15856/pm-claude-skills README)
Last 30 days research — PM Skills Wrapped — your practice turned into a shareable, Spotify-Wrapped-style story (from the mohitagw15856/pm-claude-skills README)

by mohitagw15856

Similar skills

See all →
SkillReverse engineer native, managed, Electron/JavaScriptREAmorluto/rea · by morlutoReverse engineer native, managed, Electron/JavaScript, packaged, firmware, and browser targets with REA. Use shipped-artifact or requested runtime evidence to explain features, compare versions, decompile code, or guide a reconstruction. Skip REA for ordinary source-repository architecture analysis.★ 316k GitHub starsSkillBrainstorms ideas into designs before any creative workBrainstorming Ideas Into Designsobra/superpowers · by obraYou MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.★ 290k GitHub starsSkillRequires technical rigor and verificationCode Review Receptionobra/superpowers · by obraUse when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable - requires technical rigor and verification, not performative agreement or blind implementation★ 290k GitHub starsSkillDiagnosis loop for hard bugs and performance regressionsDiagnosing bugsmattpocock/skills · by mattpocockDiagnosis loop for hard bugs and performance regressions. Use when the user says "diagnose"/"debug this", or reports something broken/throwing/failing/slow.★ 267k GitHub starsSkillImplement the result of /to-spec and /to-tickets in codeImplement specmattpocock/skills · by mattpocockImplement the result of /to-spec and /to-tickets in code.★ 267k GitHub starsSkillWriting a PR bodymattpocock/skills · by mattpocockUse when writing a PR body.★ 267k GitHub stars

More from mohitagw15856

SkillDesign a 360-degree feedback survey or write a structured360-Degree Feedback Template Skillmohitagw15856/pm-claude-skills · by mohitagw15856Design a 360-degree feedback survey or write a structured 360 feedback report. Use when asked to build a 360 feedback process, write 360 feedback for a colleague, design a feedback survey, or produce a feedback report. Produces either a complete survey instrument with rating scales and open-ended questions, or a structured narrative feedback report with themes, strengths, and development areas.★ 1.4k GitHub starsSkillDesign statistically rigorous A/B tests for product featuresA/B Test Planner Skillmohitagw15856/pm-claude-skills · by mohitagw15856Design statistically rigorous A/B tests for product features, UI changes, onboarding flows, and pricing experiments. Use when asked to set up an experiment, design an A/B test, calculate sample size, or interpret test results. Produces a complete test plan with hypothesis, variant definitions, sample size, duration estimate, guardrail metrics, and a results interpretation guide.★ 1.4k GitHub starsSkillGenerate a WCAG 2.2 accessibility audit checklistAccessibility Audit Skillmohitagw15856/pm-claude-skills · by mohitagw15856Generate a WCAG 2.2 accessibility audit checklist and remediation suggestions for any UI or design. Use when asked to audit for accessibility, check WCAG compliance, review a design for a11y issues, or create an accessibility remediation plan. Produces a prioritised checklist with pass/fail assessments and specific fixes.★ 1.4k GitHub starsSkillBuild a structured account plan for any key customerAccount Plan Skillmohitagw15856/pm-claude-skills · by mohitagw15856Build a structured account plan for any key customer or target account. Use when asked to create an account plan, key account strategy, strategic account review, or territory plan. Produces a complete account plan with relationship map, growth opportunities, risks, and 90-day action plan.★ 1.4k GitHub starsSkillOptimize an article for Answer Engine Optimization so AIAEO Optimizer Skillmohitagw15856/pm-claude-skills · by mohitagw15856Optimize an article for Answer Engine Optimization (AEO) so AI engines like ChatGPT, Perplexity, and Claude can extract, quote, and cite it. Use when asked to AEO-optimize, make content AI-readable, improve AI citation chances, or adapt an article for answer engines. Produces an AEO-optimised rewrite with question headings, 50–80 word answer capsules, a paragraph-length audit, and flagged trust signals.★ 1.4k GitHub starsSkillConduct a structured ethical review of an AI or ML featureAI Ethics Review Skillmohitagw15856/pm-claude-skills · by mohitagw15856Conduct a structured ethical review of an AI or ML feature, model, or product. Use when preparing to deploy an AI system, assessing algorithmic risk, auditing a model for bias, or producing a responsible AI impact assessment. Produces a structured ethics review covering fairness, transparency, privacy, safety, accountability, and societal impact with a risk tier score, pre-deployment checklist, and prioritised mitigations.★ 1.4k GitHub stars