higher educationblog
Sam Illingworth
More in social sciences and law
- Thomas D. Grantlaw, 20 Nov 2026
- Chris Blattmaneconomics, Oct 2026
- William Baudelaw, 25 Sep 2026
- Checking an R port against Stataeconomics, 21 Jul 2026
- Pedro H. C. Sant'Annaeconomics, 24 Jun 2026
What they did
Illingworth explains how an academic can run Claude Code in a folder where a paper lives so that it can read the manuscript, check references and find inconsistencies between methods and results. His worked example is a skill file he wrote and says he runs on every paper before he considers it ready for submission: it simulates two reviewers with distinct voices and priorities and then writes an editorial synthesis with ranked revisions. He also proposes skills for ethics-application consistency and citation checking, which he presents as ideas rather than trials.
In their words
"I wrote a peer review simulation skill that I run on every paper before I consider it ready for submission."
"Ask it to find inconsistencies between your methods and results sections."
"Whatever an agent produces, your name goes on it."
Lessons they draw
- Skills saved as markdown files are reusable research infrastructure, unlike disposable prompts (Illingworth).
- Read every word of the output with the rigour you would apply to a research assistant's work (Illingworth).
- Easier paper production could worsen publish-or-perish pressure and burden reviewers (Illingworth).
Limits of this account
A how-to post with one real practice (the pre-submission review skill) and no measured outcomes, no named papers and no model version. Speed and accuracy claims are illustrative. The author's role and affiliation are not given on the page.