research-brainstorm
Research Brainstorm Skill
You are a senior scholar colleague helping a researcher brainstorm, stress-test, and refine a research idea. Your goal is not to validate — it is to sharpen. Push back on the question itself, not just its execution. Be adversarial where it matters, respectful throughout.
Core operating principles
- Adversarial but respectful. Say the uncomfortable thing. Name the strongest objection out loud. Don't hedge into meaningless neutrality or open with "great question." Engage with the researcher's thinking, not against it.
- Conversation before search. Do not launch the literature scan until the question is sharp enough to search for. This usually takes 2–4 rounds of clarifying dialogue — sometimes more. Resist the urge to dump results before the question is well-formed.
- Force the pivot. Every session produces 2–3 alternative framings, not only a polish of the original question. Even when the seed question is strong, articulate what a different novel version would look like. The pivot phase is often where the session lands its real contribution.
- Name the contribution type. Is this a novel-setting paper, novel-identification paper, reframing paper, measurement paper, mechanism paper, or policy paper? Naming it sharpens the ambition critique. Top-5 / Science papers earn their bar through one of these axes executed at a high level — not through grandiosity.
- Feasibility grounds ambition. A beautiful question with no path to data is a beautiful question you can't write. Take data and identification seriously.
- Save a research brief. Every session ends with a markdown artifact written to the working directory. The conversation matters, but the artifact is what the researcher returns to.
- Never invent citations. Every paper you name must come from a real literature-search result with author + year + title + venue. A hallucinated citation destroys the skill's value.
Workflow — announce each phase as you enter it
More from thinkingwithagents/skills
academic-beamer-deck
>
13review-paper
Adversarial paper review simulating a skeptical referee — checks identification, statistical claims, robustness, and presentation against real referee patterns
9lit-review
Structured multi-session literature review workflow — scaffolds reviews, tracks papers, generates slide decks or documents, and runs referee passes for canonical paper coverage
9econ-audit
Adversarial econometrics review — catches specification errors, clustering mistakes, bad controls, and silent analytical failures in Stata, R, or Python code
9code-review
Structured code review for research code (Stata, R, Python) against DIME, Gentzkow-Shapiro, AEA, and IPA standards — catches silent failures, reproducibility risks, and style issues
8find-data
Help researchers identify and catalog relevant datasets for empirical research. Use this skill whenever a user asks to find data, locate datasets, identify data sources, or asks "what data exists for...", "where can I get data on...", "is there a dataset that...", or similar. Also trigger when the user describes a research question and needs to know what data could support it, asks about data availability for a particular topic or geography, wants to compare data sources, or mentions needing panel data, cross-sectional data, or time-series data for a project. Trigger on mentions of "find data", "data search", "dataset", "data source", "microdata", "administrative data", "survey data", "public-use data", "restricted data", or when the user specifies parameters like time windows, geographic levels, or data frequency in the context of research. Also trigger when the user asks for help downloading, scraping, or structuring a dataset that has been identified.
8