liteparse
Skill19 starsChanged 4 days agoApache-2.0View on GitHub
Read or extract text, tables, and values from a document file (PDF, DOCX, PPTX, XLSX, or image) locally with the `lit` CLI. Use when a task needs the contents of such a file.
- Installs packages
We split this skill into the rules it gives an agent
1 rule. 0 are common, 0 are distinctive, and 1 is very specific to this project.
0
Common
Most of the 5 edited versions we read keep these.
0
Distinctive
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 38
If two targeted greps do not find the answer, run the bundled BM25 ranker once instead of trying keyword variants.
“Common” is measured: kept by at least 6 in 10 of the 5 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
LiteParse
lit extracts text from documents locally without a model. Every lit parse re-extracts the whole document, and every line you print stays in context for the rest of the session, so the goal is few parses, few turns, small output.
Parse once to a file, then search the file
lit parse "/abs/path/doc.pdf" --format text --no-ocr -o /tmp/doc.txt && wc -l /tmp/doc.txtReuse /tmp/doc.txt for every later question about the document. Never re-run lit parse to search.
- Born-digital PDF (has a text layer, like most reports): pass
--no-ocr. It is much faster and gives the same text. - Scanned PDF or image: drop
--no-ocr. If digits look wrong, read the page visually (below). --format jsononly when you need bounding boxes or layout. Search it, never print it whole.
Search in few turns
- Get the context in the same command:
grep -n -i -C4 "total assets" /tmp/doc.txt | head -40. Usesed -n 'A,Bp'only when you need a wider window than-Cgave. Batch independent lookups into one command:
for q in "carbon intensity" "scope 1" "total revenue"; do \ echo "=== $q ==="; grep -n -i -C3 "$q" /tmp/doc.txt | head -25; done- Bound every output with
head. Use shellgrep/sedon the saved file rather than the Read and Grep tools. If two targeted greps do not find the answer, run the bundled BM25 ranker once instead of trying keyword variants. Give it a natural-language query with several synonyms.
-kis the number of matches and-ethe lines of context around each:uv run --script <skill-dir>/scripts/search.py /tmp/doc.txt -q "materiality assessment priority topics" -k 8 -e 5
Read a page visually: last resort
Screenshots are the most expensive thing you can put in context. Use one only when text cannot answer the question (dense multi-column tables, figures, charts). Render one page at modest DPI, and re-render higher only if the text is illegible:
lit screenshot "/abs/path/doc.pdf" --target-pages "13" --dpi 150 -o /tmp/shots/ # then read the PNGThe page flag is --target-pages, not --pages.
Setup
Go straight to the parse. Skip lit --version and --help unless something failed. If lit is missing: npm i -g @llamaindex/liteparse. Office files need LibreOffice and images need ImageMagick; lit converts both to PDF.
Other versions5 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 5
- sammcj/agentic-coding★ 167same name
- Luooops/skills★ 1same name
- Enjoyoer/loadout★ 0same name
- jbaham2/llamacloud-plugin★ 0same name
- patoangolano/bio-stack★ 0same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository64 other files it gives its agents.
- AGENTS.mdAGENTS.md
- skills/on-demand/vercel-composition-patterns/AGENTS.mdAGENTS.md
- adr-writingSkill
- codebase-designSkill
- code-reviewSkill
- crwlSkill
- dev-browserSkill
- diagnosing-bugsSkill
- domain-modelingSkill
- git-commitSkill
- grillingSkill
- implementSkill
- librarianSkill
- prototypeSkill
- prSkill
- researchSkill
- simple-englishSkill
- skill-dietSkill
- tddSkill
- wizardSkill
- writing-for-agentsSkill
- architecture-scanSkill
- brandkitSkill
- broSkill
- cavemanSkill
- coding-standardsSkill
- design-taste-frontendSkill
- diagram-designSkill
- fable-safe-promptSkill
- grill-for-unknownsSkill
- grill-meSkill
- grill-with-docsSkill
- handoffSkill
- high-end-visual-designSkill
- humanizerSkill
- i-have-adhdSkill
- imagegen-frontend-mobileSkill
- imagegen-frontend-webSkill
- image-to-codeSkill
- implementation-orchestratorSkill
- improve-codebase-architectureSkill
- marpSkill
- minimalist-uiSkill
- oss-repo-reviewSkill
- pretty-mermaidSkill
- redesign-existing-projectsSkill
- reducing-entropySkill
- retroSkill
- rpiSkill
- sentrySkill
- setup-matt-pocock-skillsSkill
- setup-ts-deep-modulesSkill
- show-meSkill
- suggest-skillsSkill
- supervisorSkill
- teachSkill
- tech-specSkill
- to-questionnaireSkill
- to-specSkill
- to-ticketsSkill
- The first 60 shown.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

