Skill Detail

Parse local PDFs into agent-ready text, JSON, and screenshots with LiteParse

Run LiteParse locally to extract PDF text, spatial JSON, OCR-backed output, and page screenshots before sending documents into an agent workflow.

Data Extraction & TransformationMulti-Framework
Data Extraction & Transformation Multi-Framework Security Reviewed
โญ 5.1k GitHub stars โฌ‡ 37k/wk npm
INSTALL WITH ANY AGENT
npx skills add agentskillexchange/skills --skill parse-local-pdfs-into-agent-ready-text-json-and-screenshots-with-liteparse Copy
Works best when you want a reusable capability, not another fragile one-off prompt.
At a glance
Tools required
Node.js, npm or Homebrew, LiteParse CLI (`lit`), optional OCR server
Install & setup
Install with `npm i -g @llamaindex/liteparse` or `brew tap run-llama/liteparse && brew install llamaindex-liteparse`, then run `lit parse document.pdf –format json` or `lit screenshot document.pdf -o ./screenshots`.
Author
LlamaIndex
Publisher
Organization
Last updated
May 17, 2026
Quick brief

Use LiteParse when an agent needs a local, repeatable document-ingestion step before summarizing, retrieval indexing, evidence review, or visual page inspection. The operator installs the LiteParse CLI, parses PDFs into text or JSON with bounding boxes, limits work to specific page ranges when needed, and generates page screenshots for cases where layout or visual evidence matters. This is bounded to document pre-processing and agent handoff: it is not a generic LlamaIndex SDK listing or a cloud document service card.

How it works

What this skill actually does

Inputs and prerequisites: Node.js, npm or Homebrew, LiteParse CLI (`lit`), optional OCR server.

Setup notes: Install with `npm i -g @llamaindex/liteparse` or `brew tap run-llama/liteparse && brew install llamaindex-liteparse`, then run `lit parse document.pdf –format json` or `lit screenshot document.pdf -o ./screenshots`.

Source and verification boundary: use https://developers.llamaindex.ai/liteparse/ as the canonical reference before running the workflow; keep commands, API calls, CLI usage, and generated outputs reviewable against that upstream source.

Framework fit: publish this as a Multi-Framework workflow only when the operator can invoke the documented toolchain directly, rather than treating the upstream project as a generic product listing.