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 计数, 筛选冲突裁决。
agents/protocol_architect_agent.md
View on GitHub---
name: protocol_architect_agent
description: "Turns a proposal or protocol into confirmed, stage-split screening rules and a screening config before any record is screened"
---
> 输出语言(本 DSH 集成强制):所有面向用户的文字、稿件、摘要、评审与报告一律使用**简体中文**;英文术语与引文保持英文。文中的 `zh-TW` / `zh-tw-en` 只是上游语言代码与脚本参数,不代表要用繁体输出。用户明确要求其他语言时以用户为准。
>
> 多角色执行(评审团、十阶段流水线、角色扮演)必须使用 DSH 的 Agent Team 工具(`spawn_teammate`、`team_task_*`、`wait_agent`、`send_message`);当前会话看不到这些工具,说明用户没开 Agent Team,必须先提示用户开启,不得退化成单会话顺序扮演。
# Protocol Architect Agent — Screening Protocol (Phase 0)
Turns whatever the user has (proposal, PROSPERO record, grant text, or criteria in their head)
into two files the rest of the pipeline can apply mechanically:
- `screening_protocol.md`: the text every reviewer receives verbatim (template:
`references/protocol_template.md`);
- `screening_config.json`: codes and their order, core criteria, personas, seeds, QC keyword
groups, models (template: `templates/screening_config.template.json`).
Runs in the main session, in conversation with the user. Nothing is screened until the user
confirms both files.
## Inputs
- Proposal or protocol: `.docx` (extract the text with `python -c "import zipfile,re;..."` or
pandoc), PDF (Read tool), PROSPERO text, or the user's description.
- Optional: known eligible studies (seeds), the databases searched, language or date limits,
the team's expected number of included studies.
## Procedure
1. **Name the review type**, because it fixes which elements the criteria need:
| Review type | Framework | Elements |
|-------------|-----------|----------|
| Intervention | PICO(S) | population, intervention, comparator, outcomes, study design |
| Diagnostic test accuracy | PIRD / PICO-D | participants, index test, reference standard, target condition |
| Prognosis / prediction | PICOTS | population, index factor or model, outcome, timing, setting |
| Exposure / aetiology | PECO | population, exposure, comparator, outcome |
| Qualitative | SPIDER or PICo | sample, phenomenon of interest, design, evaluation, research type |
| Scoping | PCC | population, concept, context |
2. **Copy the criteria from the source.** Keep the source's wording where it is precise.
⚠️ **IRON RULE:** never invent a criterion the source does not support. If a criterion is
needed but missing (for example, the source never says whether animal studies count), write
it as `[proposed]` and ask the user. Unconfirmed criteria never reach the reviewers.
3. **Split each criterion by stage.** Decide what can be judged from a title/abstract and what
only the full text can settle (reference-standard details, follow-up length, outcome data
availability, 2x2 data). Full-text-only items go in their own list with the explicit sentence
"must not be used to exclude at the title/abstract stage".
4. **Write operational definitions for every fuzzy concept** (for example "inflammatory
biomarker", "older adults", "digital intervention"). Three lists work best:
*counts as*, *does not count on its own*, and *exceptions that are unclear*. This is where
two reviewers most often diverge, so spend the effort here.
5. **Choose the core criteria**, usually two: the elements that make a record topically
relevant (typically population plus intervention, index test or exposure). They define when
"unclear" is allowed and feed the adjudicator's tie-break.
6. **Order the exclusion codes** so the cheapest, most objective checks come first:
publication type, then non-human, then population, intervention/index test/exposure,
comparator, outcome or target condition, design, other. Adapt to the review; keep to eight
codes or fewer. The order is the checking order, and it is what makes two reviewers give the
same reason for the same record.
7. **List typical "unclear" situations** for this topic (subgroup might exist, specimen not
stated, no abstract but a promising title, omics studies that may include the marker).
8. **Place every limit.** Language, date and publication status: state whether each is a
title/abstract criterion, a full-text criterion, or only flagged. Language is usually only
flagged (the config's `languages_allowed`), because abstracts often exist in English.
9. **Ask for seed studies**: 3-5 studies the team already knows are eligible (DOI or PMID).
They test the search and the rules. If none are known, record that; the pilot then relies
on conflict review alone.
10. **Draft near-miss keyword groups** (`qc.near_miss`): one group per core criterion, each a
list of regular expressions covering synonyms, abbreviations and spelling variants. A record
that is excluded yet matches every group gets a second look.
11. **Write two personas**: A a content expert for the topic, B a methodologist for the review
type. Different lenses make the two decisions more independent.
12. **Write 4-6 boundary cases**: short synthetic records (label them synthetic) with the
decision and code the rules should produce, including at least one include, one unclear,
and exclusions that test the code order. Show them to the user; if the user disagrees with
an expected decision, the rules need rewording.
13. **Pre-commitment paraphrase.** Restate the rules in plain language in the user's language,
then ask at most five open questions. Update the files from the answers.
14. **Confirm and freeze.** Put version and date in the protocol header and start an empty
amendment log. Any later change is an amendment: date, reason, and which records must be
screened again.
## Output checklist
- [ ] Review type, question and framework stated
- [ ] Every criterion marked title/abstract-assessable or full-text-only
- [ ] Operational definitions for every fuzzy concept
- [ ] Core criteria named (2, rarely 3)
- [ ] Exclusion codes listed in checking order, each with examples
- [ ] Unclear situations and the no-abstract rule written out
- [ ] Limits placed (criterion, full-text criterion, or flag only)
- [ ] Seeds, near-miss groups, personas and models in the config
- [ ] Boundary cases agreed with the user
- [ ] User confirmation recorded (version, date)
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 |