paper-ocr-notes-pipeline

Paper OCR Notes Pipeline

This skill is a reusable policy for paper ingestion and note production. It must stay self-contained and work in any workspace.

Do not require any companion README.md or local notes file to run this workflow. If one exists, treat it only as supplemental context.

Objective

Generate a self-contained notes package from a paper source while preserving provenance, factual grounding, OCR quality, and teachability.

Inputs

• One of: a PDF path, a paper URL, or an arXiv abs URL.
• Optional: preferred folder slug.
• Optional: output root directory.

Output Root Resolution

Use this priority order:

1. If the user provides an output root, use it.
2. Else create and use ./papers-articles in the current working directory.

Output Contract

Create a dedicated folder:

<output-root>/<paper-slug>/

Required files:

• source file: <paper>.pdf or link.txt for URL-only sources,
• notes.md as the primary deliverable,
• README.md as a paper-local artifact and provenance index,
• <paper>.ocr.feedback-loop.txt as the final OCR output,
• <paper>.ocr.feedback-loop-comparison.md as the OCR replacement report.

notes.md must be sufficient for a new reader to learn the paper without opening extra files.

Canonical Notes Sections

Use these headings in order:

1. # <Paper Title>
2. ## TL;DR
3. ## Beginner's Guide
4. ## Paper Summary
5. ## Deep Dive
6. ## Critical Analysis
7. ## Learning Path
8. ## Key Equations Summary
9. ## References

Nested Skills

• Use pdf-ocr-feedback for pagewise OCR refinement.
• Use technical-writing-workflow while drafting and revising notes.md.

Core Principles

1. Reader intuition comes before technical detail.
2. Do not blur distinct concepts.
3. Evidence-first writing: claims point to table, figure, section, or page evidence.
4. Revision is mandatory.
5. Identity verification is mandatory before trusting extracted content.
6. Uncertainty and limitations must be stated explicitly.