hermes - 💡(How to fix) Fix Add first-class LiteParse agent skill for superior local document parsing

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…

LlamaIndex now publishes a dedicated LiteParse agent skill:

This looks like a materially better parser/document-extraction path than our current ad-hoc OCR/document parsing guidance because it gives agents a compact local CLI workflow for:

  • PDF/office/image parsing
  • JSON/text extraction
  • page screenshots
  • target page ranges
  • optional OCR server configuration
  • repeatable project defaults via liteparse.config.json

Root Cause

This looks like a materially better parser/document-extraction path than our current ad-hoc OCR/document parsing guidance because it gives agents a compact local CLI workflow for:

Code Example

npx skills add run-llama/llamaparse-agent-skills --skill liteparse
RAW_BUFFERClick to expand / collapse

Context

LlamaIndex now publishes a dedicated LiteParse agent skill:

This looks like a materially better parser/document-extraction path than our current ad-hoc OCR/document parsing guidance because it gives agents a compact local CLI workflow for:

  • PDF/office/image parsing
  • JSON/text extraction
  • page screenshots
  • target page ranges
  • optional OCR server configuration
  • repeatable project defaults via liteparse.config.json

Problem

Hermes should make this superior LiteParse parser workflow easy for agents to discover and use, instead of requiring users to manually find/install the upstream skill or rely on weaker generic document parsing instructions.

Current repo observation:

  • skills-lock.json already references the upstream LiteParse skill package.
  • The repository does not appear to include a bundled Hermes-native skills/.../liteparse/SKILL.md entry in the checked-in skill tree.
  • Hermes docs already support external skill directories and skills.sh-style installation, so this should fit naturally into the existing skills system.

Proposed work

Add first-class Hermes support for the LiteParse agent skill/parser workflow.

Suggested implementation options:

  • Bundle a Hermes-native optional skill for LiteParse under the productivity/document parsing category.
  • Or add a one-command install/sync path that imports the upstream skill from run-llama/llamaparse-agent-skills and exposes it through skills_list / skill_view.
  • Document the recommended setup in the skills docs, including npx skills add run-llama/llamaparse-agent-skills --skill liteparse and skills.external_dirs if appropriate.
  • Add guardrails/pitfalls around local-only parsing, output paths, OCR server URLs, and large JSON outputs.

Acceptance criteria

  • A Hermes agent can discover a liteparse skill through the normal skills tooling.
  • The skill points agents to the LiteParse CLI commands for text, JSON, screenshots, page ranges, batch parsing, and OCR server use.
  • Docs explain how to install/sync the upstream LlamaIndex/Vercel agent skill or how Hermes bundles it.
  • skills-lock.json / provenance behavior is clarified so lockfile references do not exist without an accessible skill payload.
  • Add at least a smoke test or documented manual verification path proving skill_view('liteparse') (or equivalent CLI) works after install.

Reference

The upstream docs describe the skill workflow as:

npx skills add run-llama/llamaparse-agent-skills --skill liteparse

Example prompts supported by the upstream skill include parsing PDFs as JSON, extracting text from DOCX folders, screenshotting PDF page ranges, and using a local PaddleOCR server.

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING

hermes - 💡(How to fix) Fix Add first-class LiteParse agent skill for superior local document parsing