cheap-scan1

Extract academic PDF text locally and triage sections to reduce API token usage.

Updated Feb 26, 2026
One-click install
npx skills add https://github.com/naj2r/claude-econ-paper-template --skill cheap-scan1
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: cheap-scan1
Source: https://github.com/naj2r/claude-econ-paper-template/tree/main/.claude/skills/cheap-scan1
Command: npx skills add https://github.com/naj2r/claude-econ-paper-template --skill cheap-scan1

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires pymupdf.

What problem does it solve?

Cheap-scan1 dramatically reduces API token usage and cost when ingesting and analyzing academic PDFs by extracting text locally, triaging relevance, and only invoking vision models for pages that need them.

Core Features & Use Cases

  • Local zero-token text extraction using pymupdf with per-page quality metrics to detect scanned PDFs and trigger fallbacks.
  • Progressive triage funnel (abstract → introduction → conclusion → selective sections) and a --safe mode for exhaustive reads with per-section relevance tags.
  • Pattern-driven scanner routing for tables, figures, and equations plus optional page rendering and parallel visual/equation analysis, producing a consolidated notes.md compatible with downstream literature workflows.
  • Use cases: large-scale literature reviews, selective law-review processing, batch triage of working papers, and cost-conscious vision calls for empirical research.

Quick Start

Run the cheap-scan1 pipeline on path/to/paper.pdf in default mode to produce a consolidated notes.md in the specified output directory.

Frequently Asked Questions about cheap-scan1

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I reduce API token consumption when extracting text from academic PDF papers?

To reduce API token consumption for academic PDFs, extract text locally using pymupdf and apply progressive triage. This filters content via abstract, introduction, and conclusion sections before selectively invoking vision models, minimizing expensive API calls.

How does progressive triage work for batch processing literature review PDFs?

Progressive triage filters PDF content sequentially through abstract, introduction, and conclusion sections. This funnel approach assesses relevance early, reducing token usage by only processing selective sections and routing specific patterns like tables to vision models when needed.

Do I need pymupdf to process scanned PDFs and extract figures or tables?

Yes, pymupdf is required for local zero-token text extraction and per-page quality metrics to detect scanned PDFs. It triggers fallbacks and optional page rendering for vision model analysis of tables, figures, and equations.

What is the difference between safe mode and progressive mode for document triage?

Safe mode performs exhaustive reads with per-section relevance tags for comprehensive analysis. Progressive mode uses a filtering funnel through abstract, introduction, and conclusion sections to minimize token usage during batch triage of working papers.

Can I route specific PDF content like tables and equations to vision models automatically?

Yes, pattern-driven scanner routing automatically detects tables, figures, and equations within extracted PDF text. It optionally renders pages for parallel visual and equation analysis, producing consolidated markdown notes for downstream workflows.

What are the limitations of using local text extraction for PDF document triage?

Local text extraction cannot process scanned PDFs without triggering optional page rendering for vision models. Complex layouts may require selective visual extraction, and exhaustive safe mode reads increase token consumption compared to progressive triage filtering.