← Research ExtractorCONTENT HISTORY

Update to Research Extractor

Snapshot Oct 24, 2026 · 13:54 UTC · version 1.0.1

Collection source: downloaded plugin package.

WHAT CHANGED

First saved snapshot

No earlier snapshot is available to establish a change.

Save Research Extractor and check future changes in Following.

Up to 10 plugins free · no card required.

Compare saved observations

Download comparison JSON
Full technical diff · 0 changed fields
Full snapshot data
{
  "description": "Extract consistent fields across several research papers, construct evidence tables, compare studies, identify discrepancies, and flag possible duplicate reports/cohorts. Use for systematic/scoping reviews or multi-paper synthesis preparation.",
  "included_files": [],
  "name": "systematic-review-synthesis",
  "skill_md_contents": "---\nname: systematic-review-synthesis\ndescription: Extract consistent fields across several research papers, construct evidence tables, compare studies, identify discrepancies, and flag possible duplicate reports/cohorts. Use for systematic/scoping reviews or multi-paper synthesis preparation.\n---\n\n# Multi-paper extraction and evidence tables\n\nThis skill supports structured data extraction, not automatic meta-analysis or a completed review. Follow `research-data-extraction` invariants. PRISMA is a reporting guideline; do not conflate reporting completeness with study validity or risk of bias.\n\n## Workflow\n\n1. Determine the review question and requested fields; ask only if the question/schema is materially ambiguous.\n2. Define the normalized schema once before extracting. If user supplied one, use it exactly.\n3. Assign a stable unique Study ID to every paper/report. Where sources may be companion reports, record separate Report IDs and only a tentative shared-cohort ID.\n4. Process each source independently. Never fill one study's missing field from another study or from generic knowledge.\n5. Preserve each value's source location and missingness code.\n6. Build rows with identical columns, then run consistency checks across sample sizes, groups, timepoints, units, outcome definitions, and estimates.\n7. Flag possible duplicate underlying studies for human review. Do not merge reports or counts automatically.\n8. Return the evidence table plus unresolved discrepancies, extraction uncertainties, and any scope not completed.\n\n## Suggested columns\n\nStudy ID; report/citation; country; design; population; eligibility; total/enrolled/analyzed sample sizes; intervention/exposure; comparator; primary outcome; follow-up; main result; effect estimate; CI; p-value; adverse events; author conclusion; author limitations; funding/conflict; bias-related evidence; locations; uncertainty.\n\n## Duplicate-study signals\n\nPossible overlap indicators include the same registration number, authors, recruitment dates, institution, sample size, intervention groups, or baseline characteristics. Report signal(s), confidence (`HIGH`/`MEDIUM`/`LOW`) and reason. A match on one attribute is not proof. Keep records separate unless the user confirms linkage or the reports clearly identify a single study.\n\n## Synthesis boundary\n\nDescribe patterns without implying pooled effects. Do not calculate a meta-analysis, GRADE certainty, or causal conclusion unless asked and sufficient methodological inputs and an appropriate protocol are supplied. Keep risk-of-bias evidence separate from formal judgments.\n"
}

SHA-256 of public snapshot: 3b4a42e899de8ba652b5c086258553fbe78c1a73fbc9a5bd2c78648d80c813af