weekly-research-narrative

Synthesize a week of research into one evidence-backed PaperTrace narrative that connects several papers, releases, tools, or events. Use for weekly reviews and trend explainers; do not use when the r

SKILL.md

GitHub

Weekly Research Narrative

Find the week's connecting idea and show why it changes a research decision.

Select a thesis, not a category

A useful thesis describes movement or tension: a capability becoming measurable, a bottleneck shifting, two fields converging, an evaluation failing, or a tool making a method usable. “This week in AI” is a category, not a thesis.

Test the thesis against 5–10 source-backed items. Include counterevidence or a quiet item that complicates the popular story. If the evidence does not cohere, publish a smaller “signals to watch” note instead of forcing a trend.

Narrative shape

  • State the change in one sentence and name who should care.
  • Establish the prior state or bottleneck.
  • Organize evidence by causal role or disagreement, not by publication order.
  • Separate peer-reviewed work, preprints, vendor claims, runnable artifacts, and community reaction.
  • Explain what is newly possible, what is still blocked, and one action for a 5-, 20-, or 60-minute attention budget.
  • End with falsifiers: what evidence next week would weaken the thesis?

Balance and provenance

Prefer primary sources and link each material claim. Community and social attention may explain buzz but cannot establish scientific impact. Avoid making an AI story universal when domain evidence differs. When the topic crosses fields, preserve each field's evaluation norms and recruit review rather than importing CS benchmarks uncritically.

Produce parallel English and Chinese claims without adding facts in only one language. Reuse PaperTrace's impact/buzz/utility vocabulary and disclose that scores are editorial heuristics.