When should you use it?
- You work from a folder of papers and data
- You re-explain your project every session
- You need repeatable screening
Not for: Confidential data you cannot share; Judgments about what counts as evidence
What do you need, and what do you get?
You need
- Project folder
- Instructions file
- Screening criteria
You get
- Screening tables
- Extracted quotes
- Saved result files
How does it work, step by step?
- Open the folderAdd your project folder as a Codex project.
- Write the instructionsDraft an AGENTS.md covering your role, field norms, preferred voice and how feedback should sound.
- Keep permissions onHave it ask before editing or deleting files.
- Run a tedious taskScreen papers or rename PDFs, previewing changes first.
- Save outputsAsk it to write each major result to a file.
The prompt
Our own prompt, inspired by Mushtaq Bilal, PhD (@MushtaqBilalPhD) and written to work in ChatGPT and Custom agent. Values in lime are placeholders.
Fill in the blanks (optional; the copied prompt uses your values)
Create an AGENTS.md for my project in this folder with sections for Role ({my_field_and_project}), Standards ({citation_style_and_norms}), Voice ({style}) and Feedback ({focus}). Then screen the PDFs here against {criteria} and save a table to {output_file} with a reason for each decision. Ask before changing any existing file.
Inspired by Mushtaq Bilal, PhD (@MushtaqBilalPhD): Codex 101 for Academic Researchers. The prompt above is written by playbooks.bot in our own words; nothing from the original is quoted.
What can go wrong?
- Scanned PDFs may be read poorly; check.
- Do not put confidential details in the instructions file.
- Stale instructions skew results; update them.
Our take
For nontechnical researchers, the instructions file is the high-leverage step. Writing down your field's standards, preferred citation style and how you want critique once turns a general assistant into a consistent collaborator for that project. Keeping file-change permissions on at first is wise while you learn what it does, and previewing rename lists before applying them avoids a mess in a folder you care about. Treat every screening pass as a first filter: you still decide inclusion, and you still read the papers that matter. Save outputs as files in the project so the work leaves a visible record rather than living only in chat. Be careful with interview transcripts and other human-subjects material; check your ethics approval and strip identifiers before any cloud tool sees them. For copyrighted PDFs, prefer tools that keep files on your machine, and follow your library's and publisher's rules. Start with one tedious task, such as renaming, before trusting it with analysis.
Where the time goes back: You stop re-explaining your project and can rerun screens consistently.
FAQ
Do I need to code?
What stays with me?
Source and credit
Inspired by Mushtaq Bilal, PhD (@MushtaqBilalPhD). We describe the idea in our own words, link to the original, and wrote the prompt ourselves; nothing is quoted.
- Inspired by
- Codex 101 for Academic Researchers
- Creator
- Mushtaq Bilal, PhD (@MushtaqBilalPhD)
- Published on
- X
- Original date
- May 13, 2026
- License
- Not openly licensed (the poster keeps all rights), so we quote nothing and link to the original
- Originally for
- Custom agent
- AI dry run
- Oct 23, 2026: passed. Dry-run tested by our AI test agent on sample input. PASS: Gates held on desk check; no live sends, bookings or purchases.
AI dry run on sample data; not run with live connected accounts. The playbooks.bot test agent filled the prompt with synthetic inputs, produced the output and checked it against the page's stated outputs and guardrails. - Verified
- Oct 23, 2026: source link resolves to the original, the credited creator published it, our excerpt or prompt matches it, and the license allows our use.
Are you the creator? Claim or correct this page.