mcpbeat

Extraction Form

willoscar/extraction-form

| Use when `evidence-review` has screened includes and needs a schema-aligned extraction table.

2k tokens
context cost
the whole folder, loaded on every use
2
files
ships runnable scripts
0
copies elsewhere
how many repositories repackaged it
496
stars on the repo
on the repository, not the skill itself

Install

one command, takes just this skill from the repository 
npx skills add https://github.com/WILLOSCAR/research-units-pipeline-skills --skill extraction-form

What comes with it

5 056 bytes besides the instruction
scripts/run.py

The instruction itself

7 sections, as written by the author

Extraction Form

Transforms screened include rows plus protocol schema into the analysis table used by evidence-review.

Inputs

Required:

  • papers/screening_log.csv
  • output/PROTOCOL.md

Optional:

  • papers/paper_notes.jsonl

Output

  • papers/extraction_table.csv

Contract

The table must:

  • contain one row per included paper
  • preserve provenance columns (paper_id, title, year, url)
  • include protocol-defined extraction fields
  • keep narrative residue in notes, not in schema columns

Script boundary

scripts/run.py should:

  • parse the extraction schema from the protocol
  • filter include rows
  • materialize a normalized CSV

Acceptance

  • output exists
  • include rows map 1:1 to extraction rows
  • schema matches output/PROTOCOL.md

Non-goals

  • synthesis writing
  • bias scoring

How to use it

Copy the folder

Take willoscar/extraction-form from the repository into ~/.claude/skills for personal use, or into .claude/skills inside a project.

Check the name does not clash

The agent identifies a skill by the name field in its header. Two skills with the same name cannot sit side by side — one of them will be ignored.