paper-extract
Skill0 starsChanged 3 months agoMITView on GitHub
Inspect a quantitative-finance paper PDF with the available PDF capability and produce a checksum-bound, evidence-backed synopsis, metric dataset, formulas, exact replication targets, and ambiguity report. Use when paper.pdf exists and the user wants contributions, methods, tables, formulas, data design, performance claims, or a replication handoff. Requires visual verification of layout-sensitive tables and equations.
3 other projects use a version of this.
Adopted by
Most recently taken up by
- Deadpoolmine/systematic-research-skillstheir own version, first seen Nov 1, 2026
- smallSheep123/paper-skillstheir own version, first seen Oct 25, 2026
- L4pisLazuli/grounded-paper-skillstheir own version, first seen Aug 19, 2026
Other versions3 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 3
- Deadpoolmine/systematic-research-skills★ 14same name
- smallSheep123/paper-skills★ 11same name
- L4pisLazuli/grounded-paper-skills★ 0same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository11 other files it gives its agents.
- paper-replicateSkill
- paper-searchSkill
- paper-theory-reconstructSkill
- quant-paperSkill
- strategy-translateSkill
- paper-extractSkill
- paper-replicateSkill
- paper-searchSkill
- paper-theory-reconstructSkill
- quant-paperSkill
- strategy-translateSkill
The file
We split this skill into the rules it gives an agent
4 rules. About 0 are common, 3 are distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈3
Distinctive · estimate
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 28
Verify that the PDF title, authors, arXiv version, and checksums agree with meta.json and source_manifest.json.
- Distinctive: line 54
Never use regex, OCR, or extracted text as authoritative evidence for layout-sensitive content.
- Distinctive: line 55
Never invent values, units, signs, annualization, cost status, or formulas.
- Distinctive: line 56
Keep reported facts separate from interpretation and replication assumptions.
≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Paper extract
Turn papers/<versioned-id>/paper.pdf into a visually verified, finalized research record. Read and follow the available visual PDF capability before inspecting the paper. If pages cannot be rendered and inspected, stop; extracted text alone cannot satisfy this skill.
Resolve paths and contracts
Resolve the absolute workspace root and this skill's directory. Read references/extraction_schema.md, references/reported.schema.json, and references/note_template.md before authoring artifacts.
papers/<versioned-id>/
├── paper.pdf
├── meta.json
├── source_manifest.json
└── extraction/
├── note.md
├── reported.json
├── extraction_report.md
└── manifest.jsonWorkflow
- Verify that the PDF title, authors, arXiv version, and checksums agree with
meta.jsonandsource_manifest.json. Stop on a mismatch. - Build a complete page map using text/search only for navigation.
- Render and inspect the title, data/method pages, every core equation, every table used by a metric, and ambiguous footnotes.
- Record
source.page_count, every rendered page insource.visually_inspected_pages, and the actual PDF, metadata, and source-manifest hashes. - Attach page, table/equation, row/column, short transcription, and visual-verification status to every metric and formula.
- Assign stable strategy, variant, sample, and cost-regime IDs. Do not combine incompatible scopes in one replication target.
- Recompute
evidence_coverage; state unresolved choices and likely replication classification. - Validate and finalize:
QPA_EXTRACT_SKILL_DIR="/absolute/path/to/paper-extract"
QPA_WORKSPACE_ROOT="/absolute/path/to/workspace"
python3 "$QPA_EXTRACT_SKILL_DIR/scripts/validate_output.py" \
"$QPA_WORKSPACE_ROOT/papers/<versioned-id>/extraction/reported.json" --strict
python3 "$QPA_EXTRACT_SKILL_DIR/scripts/finalize_extraction.py" \
<versioned-id> --root "$QPA_WORKSPACE_ROOT/papers"The validator enforces both reported.schema.json and cross-record/source invariants. The finalizer hashes the PDF, source metadata, note, reported dataset, and ambiguity report. Later changes invalidate the replication gate.
Large papers
Inspect in page batches and maintain a page ledger. Do not truncate long Results sections. Prioritize section boundaries, performance tables, captions, method-referenced appendices, and pages cited by the paper's result discussion.
Rules
- Never use regex, OCR, or extracted text as authoritative evidence for layout-sensitive content.
- Never invent values, units, signs, annualization, cost status, or formulas.
- Keep reported facts separate from interpretation and replication assumptions.
- Preserve metric signs and declare risk-metric polarity.
- Make the TL;DR paper-specific: contribution, mechanism, fair comparison, evidence, and replication risk.
- Mark unresolved material rather than guessing.
- Author only the current
reported.schema.jsoncontract; reject noncurrent extraction artifacts and re-extract them from the bound PDF.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

