SR Screener turns a proposal or PROSPERO protocol into confirmed eligibility rules, then screens titles, abstracts and full texts with two independent AI reviewers. Disagreements go to a third reviewer, and every exclusion carries an ordered code and a short reason.
It reads RIS, PubMed .nbib, Web of Science and CSV exports, removes duplicates and runs in resumable batches. The outputs are an Excel log, RIS groups for EndNote or Zotero, PRISMA counts, a methods draft and a corpus file that hands off to the academic-paper skill. People keep the final sign-off.
What You Get
- A confirmed screening protocol and config file built from your proposal
- Screening decisions with one ordered exclusion code and a short reason per record
- An Excel log, RIS groups for EndNote or Zotero, and PRISMA 2020 counts with a flow diagram
- A methods paragraph with an AI-use statement and a literature corpus file for the writing stage
Common Use Cases
- Title and abstract screening of a database export for a systematic review
- Piloting eligibility criteria against a team’s own labelled records
- Adjudicating screening conflicts from a Rayyan or Covidence export
- Auditing exclusions and reporting the selection process for PRISMA
What Makes It Unique
The skill enforces a fixed order of work. The protocol must be confirmed before any record is read, a pilot must pass against the team’s labels before the full run, a cost estimate needs a clear yes, and a sample of records both reviewers excluded gets a senior recheck. It reports observed agreement, kappa and PABAK together, and states that a single model reading twice is not two independent reviewers.
Under The Hood
The skill loads a long SKILL.md with eight modes and four agent files. Deterministic steps run as local Python scripts that parse exports, merge decisions and build outputs; they use the standard library, with openpyxl optional for the Excel log. Reviewers run as lean subagents with read and search tools only, so they cannot browse, write files or see each other’s work. The skill reads your exports and PDFs and writes working files, logs and reports to your project folder. Text inside records is treated as data and never as instructions.