last-30-days-research
**last-30-days-research** This Claude Code skill aggregates recent opinions and sentiment about any topic by searching Reddit, X/Twitter, and the broader web from the past 30 days, bypassing SEO-optimized content to surface authentic community discussion. Use it when you need genuine reactions to tools, products, trends, or events from real users rather than marketing materials, receiving a structured report organized by consensus points, disagreements, pain points, positive signals, contrarian takes, source links, and a confidence rating based on data volume and consistency.
git clone --depth 1 https://github.com/mohitagw15856/pm-claude-skills /tmp/last-30-days-research && cp -r /tmp/last-30-days-research/plugins/pm-cross/skills/last-30-days-research ~/.claude/skills/last-30-days-researchSKILL.md
# 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. ### Step 2 — Reddit search 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"). ### Step 3 — X/Twitter search 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). ### Step 4 — Broader web search 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
Conduct 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.
Structure AI and ML product decisions with the rigour of any product decision. Use when building AI-powered features, evaluating LLM integrations, designing AI products, or assessing AI readiness. Produces a complete AI product canvas covering problem definition, model approach, data requirements, evaluation framework, UX design, responsible AI checklist, and launch monitoring plan.
Transform feature briefs into structured design briefs that give designers the context they need before opening Figma. Use when asked to write a design brief, create a design handoff, brief a designer on a new feature, or translate a PRD into design requirements. Produces a brief with user goal, emotional context, success criteria, constraints, edge cases, and out-of-scope boundaries.
Design statistically rigorous A/B tests and interpret experiment results. Use when asked to design an experiment, run an A/B test, calculate sample size, interpret test results, or assess whether an experiment was successful. Produces a complete experiment design with hypothesis, sample size, run time, success criteria, and risk flags — or a results interpretation with ship/iterate/kill recommendation.
Synthesises user signals from multiple research sources into a unified, weighted insight brief. Use when you have data from interviews, support tickets, NPS verbatims, app reviews, or sales calls and need to reconcile contradictions, surface the underlying need behind requests, or answer 'what are users really telling us'. Produces ranked insights with confidence ratings, source weighting rationale, divergent signal analysis by user segment, and a research gap identification section.
Structure a product data analysis, metric deep-dive, funnel analysis, or cohort study. Use when asked to analyse product metrics, investigate a drop in conversion, explain a data change to stakeholders, or find the root cause of a metric movement. Produces a structured analysis with question, root cause, confidence level, and recommended action.
Interpret product metrics against goals and surface actionable signals. Use when asked to analyse product health, review key metrics, investigate a performance issue, produce a health report, or assess product-market fit signals. Produces a structured health report with RAG status, trend analysis, root cause hypotheses, and prioritised actions.
Structure a retention analysis, churn investigation, or engagement deep-dive for any product team. Use when asked to analyse user retention, investigate churn, measure DAU/MAU, or build a retention improvement plan. Produces a retention snapshot with root cause hypotheses, aha-moment correlation, and prioritised interventions.