LiteParse Document Parser
v1.0.0Use when parsing PDFs, DOCX, PPTX, XLSX, or images locally. Supports text extraction, JSON output with bounding boxes, batch processing, and page screenshots...
⭐ 0· 27·0 current·0 all-time
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
OpenClaw
Benign
medium confidencePurpose & Capability
Name, description, and runtime instructions all describe local parsing of PDFs, Office docs, spreadsheets, and images. Required helpers (LibreOffice, ImageMagick) are plausible for the stated features (conversion, rendering, OCR). No unrelated resources or credentials are requested.
Instruction Scope
SKILL.md only instructs running local CLI commands (lit parse, batch-parse, screenshot) and using a local config file; it does not ask the agent to read unrelated system files, access secrets, or transmit data to external endpoints. Outputs are written to local files.
Install Mechanism
No install spec is included in the registry (instruction-only). SKILL.md tells the user to use Homebrew (brew install llamaindex-liteparse and brew install --cask libreoffice, imagemagick). Using Homebrew is common, but the specific brew package ('llamaindex-liteparse') and overall lack of source/homepage metadata reduce provenance; the package could come from a third-party tap. Recommend verifying the package origin before installing.
Credentials
The skill declares no required environment variables, credentials, or config paths. The local liteparse.config.json is reasonable and limited to tool options (OCR language, DPI, etc.).
Persistence & Privilege
Skill is instruction-only, does not request persistent presence, and registry flags are default (always:false). There are no instructions to modify other skills or system-wide agent settings.
Assessment
This skill looks internally consistent for local document parsing, but the package provenance is unclear. Before installing: 1) verify the Homebrew package origin (which tap/repo provides 'llamaindex-liteparse') and inspect its homepage/source; 2) run 'lit --version' and check what binary was installed and where; 3) consider installing in a sandbox or VM if you want to inspect behavior first; 4) ensure LibreOffice and ImageMagick are installed from official sources; and 5) review/output files (and any logs) to confirm no unexpected network activity or external uploads.Like a lobster shell, security has layers — review code before you run it.
latestvk972r3c18g00cxcezrww5xrp6d849f4c
License
MIT-0
Free to use, modify, and redistribute. No attribution required.