last30days
Created by Matt Van Horn
Explore recent community conversations across developer, social, and web sources.
Our developer take
Finding fresh developer signals
Before choosing a feature to build, investigate how developers describe the problem this month. Ask for repeated complaints and concrete workarounds, then use the brief to choose people to interview. Discussion volume alone does not establish demand.
A practical first workflow
How to use last30days
Build a recent, source-linked brief on one developer topic.
An AI IDE List walkthrough based on the linked template. These are suggested tasks and review criteria, not results from a hands-on test.
First, add this Bot
Open the official last30days template, choose Import Bot, and finish adding it in the Grok Bot app. Open its conversation, then follow the workflow below. If you have not set up the app, follow our installation and connection guide.
What to prepare
- A narrowly scoped topic and the decision you are researching.
- A target date window, language, and the source types you care about.
- Permission to install the documented skill in the Bot environment; Python 3.12 or newer is required.
Check the research skill
Ask the Bot to verify Python and its last30days skill. The listing specifies npx skills add mvanhorn/last30days-skill -g for installation in its environment.
Choose source access
Decide whether to complete optional X authentication. You can skip it; ask the Bot to state which sources remain available.
Run a focused brief
Provide one topic and a 30-day window. Request dated links and distinguish first-hand reports from reposted announcements.
Check the signal
Inspect the strongest sources and ask which conclusions depend on a single report. Narrow the topic if the brief is too broad.
First-run example
Replace every [BRACKETED_VALUE] with your details, attach the required files, then send this in the Bot's conversation.
Research the last 30 days of discussion about [DEVELOPER_TOPIC], ending [END_DATE]. I am deciding [DECISION]. Check your last30days skill and Python requirements first. Use available public sources; skip X if authentication is unavailable and disclose the gap. Return five useful findings, each with a dated source link, plus recurring pain points and one practical experiment for my project. Distinguish first-hand experience from announcements and speculation.
What you should get
Use this checklist to review the first result and request anything missing.
- A brief bounded by the requested start and end dates.
- Dated links, recurring themes, and a clear source-coverage note.
- A project experiment grounded in the findings.
For the next run
Repeat with a new end date when you need an updated brief. The skill's 30-day update check is separate from a recurring research job.
If the first run gets stuck
For install errors, have the Bot report its Python version and the failed command. If a source needs credentials, either complete its supported login or omit that source.
What the template includes
Official sourceSummarized from the public listing. The labels below describe capabilities; exact installed skill and connector names are not always published.
Integrations & inputs
- GitHub
- X (optional)
- YouTube
- ScrapeCreators
Skills & playbooks
last30days
Routines
Checks for a newer skill version every 30 days; this is separate from scheduling research briefs.
What to consider
Coverage varies with connected sources. Request a list of unavailable sources alongside the brief.