zrwangems/dsh-zrwang-plugin / ars/skills/sr-screener
sr-screener
Flagged系统综述文献筛选:把方案或 PROSPERO 协议转成资格规则,双盲筛选标题摘要与全文,第三人裁决冲突,输出 PRISMA 2020 计数、EndNote/Zotero RIS 分组与可交付给论文技能的 literature_corpus。Triggers: systematic review screening, screen papers, PRISMA counts, pilot screening, adjudicate conflicts | 文献筛选, 系统综述筛选, PRISMA 计数, 筛选冲突裁决。
references/reporting_and_handoff.md
View on GitHub> 输出语言(本 DSH 集成强制):所有面向用户的文字、稿件、摘要、评审与报告一律使用**简体中文**;英文术语与引文保持英文。文中的 `zh-TW` / `zh-tw-en` 只是上游语言代码与脚本参数,不代表要用繁体输出。用户明确要求其他语言时以用户为准。
>
> 多角色执行(评审团、十阶段流水线、角色扮演)必须使用 DSH 的 Agent Team 工具(`spawn_teammate`、`team_task_*`、`wait_agent`、`send_message`);当前会话看不到这些工具,说明用户没开 Agent Team,必须先提示用户开启,不得退化成单会话顺序扮演。
# Reporting and handoff
## Contents
1. PRISMA 2020 numbers
2. Methods text and AI disclosure
3. Reference-manager import
4. Handoff to Academic Research Skills
## 1. PRISMA 2020 numbers
| PRISMA flow box | Source |
|-----------------|--------|
| Records identified from each database | `identification.json` `by_database` (raw records per export) |
| Duplicate records removed | `duplicates_removed` |
| Records screened | unique records with valid current final decisions |
| Records excluded | final title/abstract exclusions (the code breakdown is optional in PRISMA) |
| Reports sought for retrieval | records advanced (include + unclear) |
| Reports not retrieved | `ft_not_retrieved.csv` |
| Reports assessed for eligibility | retrieved reports with valid current final decisions |
| Reports excluded, with reasons | full-text exclusions by code, one reason per report |
| Studies included | full-text includes, after grouping companion reports into studies |
`*_prisma_counts.md` holds a Mermaid diagram (GitHub renders it) plus the JSON numbers. Records
from registers, websites or citation searching have separate PRISMA boxes; add them by hand.
Check that the per-database numbers match what each database reported for the search; if an
export was capped or split, say so.
Both stages mark counts as provisional and withhold methods text while any required decision
or recheck is pending. Full-text completeness also includes unfinished title/abstract screening,
adjudication and QC, even when every currently matched PDF already has a full-text decision.
Every prepared record (or FT manifest entry) needs a final decision; absent pending files do not
make missing decisions complete. Full-text preparation must also match the current TA decisions:
all advances occur exactly once in either retrieved or not-retrieved, and the TA decision snapshot
must be unchanged. A stale set stays provisional until it is prepared and assessed again.
The full-text diagram includes reports awaiting classification as a separate branch.
## 2. Methods text and AI disclosure
`*_methods_selection.md` is a draft with real numbers and `[TO COMPLETE]` slots. It covers what
PRISMA 2020 item 8 asks for: how many reviewers screened each record, whether they worked
independently, how disagreements were resolved, and which automation tools were used. The team
completes:
- the dates of the runs;
- the human verification that actually happened (who checked what, how many exclusions were
sampled, what was changed);
- the final human-confirmed numbers.
Before submission, check the target journal's AI policy and current guidance on AI in evidence
synthesis (for example the RAISE recommendations). Name the exact models (`model_labels` in the
config), the tool and its version, and keep the screening log as a supplementary file.
## 3. Reference-manager import
- **EndNote**: File > Import > File, "Reference Manager (RIS)", Unicode (UTF-8). The decision is
in Label (`TA-Include`, `TA-Unclear`, `TA-Exclude-E3`), the reasons in Notes; build smart
groups on Label. The record ID (`R00012`) is in the Reference ID field and in the note.
- **Zotero**: import each RIS file into its own collection; `--tag-keywords` adds the decision
as a tag.
- **Rayyan / Covidence**: import the RIS files, or use the Excel log to compare decisions.
Each RIS record is the richest source version (PubMed first) of the de-duplicated group, with
its original fields untouched plus the label and note.
Every rebuild writes all three category files, including empty categories, so earlier group
files cannot retain overridden records. Strings beginning with formula/control prefixes are
escaped as text in XLSX and CSV screening logs; the original record text remains in the source data.
All CSV exports quote every field, including empty fields. Formula prefixes after embedded
semicolons or tabs are also escaped with an apostrophe, so alternative-separator readers cannot
expose an executable formula by splitting a field. Original source data is preserved.
## 4. Handoff to Academic Research Skills
Within Academic Research Skills (ARS), `deep-research` covers research design and the search,
and `academic-paper` covers writing; this skill covers the screening in between.
- **Corpus**: `*_literature_corpus.yaml` is a list of `literature_corpus[]` entries in the ARS
`literature_corpus_entry.schema.json` format (citation key, title, CSL-JSON authors, year,
source pointer, venue, DOI, tags, provenance `obtained_via: other`,
`adapter_name: sr-screener`). Paste it under `literature_corpus:` in a Material Passport, or
give it to `academic-paper` or `deep-research` as the curated corpus: their literature agents
then read it first and search only for gaps.
- **Methods and results**: give `academic-paper` (`full` or `lit-review` mode) the methods
draft, the PRISMA counts and the excluded-with-reasons list for the Methods, Results and flow
diagram.
- **What stays here**: screening decisions. The receiving skills read the corpus; if they
re-apply criteria, it should be the same protocol, and any disagreement comes back here as an
override with a reason.
- The corpus file has no abstracts: abstracts can be publisher-copyrighted, and passports are
often shared.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| add-product-e2e-evalpaperclipai/paperclipAdd or extend a Paperclip full-stack runner E2E workflow, fixture, matcher, or report evidence path for local or Daytona execution. | Stars: 115k | Updated | Claude CodeCodex | Verified | Install |
| add-runner-evalpaperclipai/paperclipAdd or extend a Paperclip Runner protocol evaluation definition, roster, assertion, or report fixture with provenance and narrow validation. | Stars: 115k | Updated | Claude CodeCodex | Verified | Install |
| diagnose-why-work-stoppedpaperclipai/paperclipCompatibility entry point for failed, stalled, looping, or over-recovered Paperclip work. Use fix-failed-paperclip-run for the full diagnosis, regression, repair, real verification, and green-PR workflow; honor an explicitly requested diagnosis-only scope. | Stars: 115k | Updated | Claude CodeCodex | Verified | Install |
| fix-failed-paperclip-runpaperclipai/paperclipDiagnose and fix failed, stuck, slow, or incorrectly blocked Paperclip tasks and runs. Use with a task/run URL or failure report to trace the root cause, prove a regression red then green, check second-order effects, verify the real workflow, and deliver a PR with passing checks. | Stars: 115k | Updated | Claude CodeCodex | Verified | Install |