preprocess-pdf

Interprets PDF preprocessing results to guide routing decisions.

7|3|Updated Mar 8, 2026
One-click install
npx skills add https://github.com/BaiGanio/aperio --skill preprocess-pdf
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: preprocess-pdf
Source: https://github.com/BaiGanio/aperio/tree/main/skills/preprocess-pdf
Command: npx skills add https://github.com/BaiGanio/aperio --skill preprocess-pdf

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This internal reference provides guidance on interpreting Aperio's PDF preprocessing results (text, scanned, mixed, or empty) and what actions to take next. It is intended for when a PDF has already been preprocessed and you need to decide routing or further handling. Do NOT use for user-requested PDF tasks — use the dedicated pdf skill for creation, merging, or extraction.

Core Features & Use Cases

  • Result type interpretation: Distinguish between text-native, scanned, mixed, and empty PDFs and determine the correct downstream path.
  • Routing guidance: Offer clear next steps for each result type, such as inlining text, saving images, or prompting for additional input.
  • Operational independence: Serves as a reference during MCP attachment processing to ensure consistent handling across deployments.

Quick Start

Use this guide to interpret the PDF preprocessing result and decide the next routing steps.

Frequently Asked Questions about preprocess-pdf

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

FAQPage Schema
How do I route PDFs after preprocessing based on whether they are text or scanned?

PDF routing depends on interpreting preprocessing results to classify documents as text-native, scanned, mixed, or empty, directing actions like inline text extraction or image preprocessing.

What actions should I take when a PDF preprocessing result is empty or mixed?

For an empty or mixed PDF preprocessing result, the required action is to route the document to user re-prompting for additional input or apply image preprocessing respectively.

How does MCP router PDF attachment processing determine the correct downstream path?

MCP router attachment processing uses preprocessPdf.js detection logic to evaluate PDFs and apply consistent routing decisions for text-native, scanned, mixed, or empty files.

When should I use PDF preprocessing routing guidance instead of a standard PDF extraction tool?

Use PDF preprocessing routing guidance when a PDF is already preprocessed and you need to decide downstream handling, not for user-requested creation, merging, or extraction tasks.

What is the difference between handling text-native and scanned PDFs in automated document routing?

Handling text-native PDFs involves routing to inline text extraction, while scanned PDFs require routing to image preprocessing to manage the document content effectively.

Do I need any dependencies to interpret PDF preprocessing results for routing?

Interpreting PDF preprocessing results requires no external dependencies, serving as an internal reference to align with the preprocessPdf.js detection logic for routing decisions.