Lexoid CLI

What it does

When your agent uses it

• The user wants to extract markdown / JSON / LaTeX from a file
• URL without writing Python
• Run schema-based structured extraction
• Batch-parse from shell scripts

Example prompts

• “parse this PDF”
• “convert document to markdown”
• “extract JSON from PDF”
• “/lexoid-cli”

Requirements

• Python 3
• A credential in GOOGLE_API_KEY
• A credential in OPENAI_API_KEY

Workflow steps

3 steps, taken from the first numbered list in SKILL.md.

1. 1lexoid is installed (lexoid --help or python -m lexoid --help). If not, run pip install lexoid.
2. 2For LLM-based commands, the relevant API key env var is set
3. 3For Linux DOCX → PDF, LibreOffice (lowriter) must be installed.

What it can do on your machine

Read from SKILL.md and the folder at commit b45d174. It shows what the files ask for, not the result of running them.

• Tool permissions

  Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

  From allowed-tools in the SKILL.md frontmatter.

• Runs code

  Shell commands in SKILL.md call:

  • ollama
  • python
  • jq
  • pip

  From the folder's file list and the shell code blocks in SKILL.md.

• Network

  No URLs in SKILL.md. Its commands use pip, which can reach the network depending on how they are called.

  From URLs in SKILL.md, links to its own repository left out.

• Credentials

  Names these keys or tokens, usually read from environment variables:

  • GOOGLE_API_KEY
  • OPENAI_API_KEY
  • ANTHROPIC_API_KEY
  • MISTRAL_API_KEY
  • HUGGINGFACEHUB_API_TOKEN
  • TOGETHER_API_KEY
  • OPENROUTER_API_KEY
  • FIREWORKS_API_KEY

  From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Lexoid CLI loads about 2k tokens when it runs. Until then it costs about 123 tokens; SKILL.md has 769 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it

~123

When it runs · the whole SKILL.md, loaded when a task matches

~2k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

• NoteMentions a .env fileSKILL.md:29

  ### Loading API keys from `.env`

• NoteMentions a .env fileSKILL.md:31

  API keys are commonly stored in a `.env` file at the project root rather than exported in the shell. The `lexoid` CLI do

• NoteMentions a .env fileSKILL.md:33

  **Always load `.env` in a subshell so the keys never leak into the surrounding environment** — the parentheses scope the

• NoteMentions a .env fileSKILL.md:36

  # Load .env for this command only (if it exists); env is reset to its prior state on exit

• NoteMentions a .env fileSKILL.md:37

  ( set -a; [ -f .env ] && . ./.env; set +a; lexoid parse --input document.pdf --parser-type LLM_PARSE --model gpt-4o )

• NoteMentions a .env fileSKILL.md:40

  Do **not** run a bare `set -a; . ./.env; set +a` in the parent shell — that persists secrets into the session.

• NoteMentions a .env fileSKILL.md:60

  regardless of routing). LLM-based: load .env first.

• NoteMentions a .env fileSKILL.md:81

  `schema` commands are LLM-based — load `.env` first (see "Loading API keys from .env") unless keys are already exported

• NoteMentions a .env fileSKILL.md:107

  LaTeX conversion is LLM-based — load `.env` first (see "Loading API keys from .env") unless keys are already exported.

• NoteMentions a .env fileSKILL.md:134

  the env var. The CLI does not auto-load `.env`; load it via the subshell wrapper (see "Loading API keys from .env") and

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from oidlabs-com/Lexoid at commit b45d174, republished under its Apache-2.0 licence (© oidlabs-com). 769 words, ~1,969 tokens.

name

lexoid-cli

description

Parse and convert documents (PDFs, images, web pages, DOCX/XLSX/PPTX, audio) from the terminal using the `lexoid` CLI. Use when the user wants to extract markdown / JSON / LaTeX from a file or URL without writing Python, run schema-based structured extraction, or batch-parse from shell scripts. Triggers include "parse this PDF", "convert document to markdown", "extract JSON from PDF", "convert PDF to LaTeX", "use lexoid CLI", or any pipe/shell-style document-processing request.

# Load .env for this command only (if it exists); env is reset to its prior state on exit
( set -a; [ -f .env ] && . ./.env; set +a; lexoid parse --input document.pdf --parser-type LLM_PARSE --model gpt-4o )

# Default: AUTO routing, markdown to stdout
lexoid parse --input document.pdf

# Save to file
lexoid parse --input document.pdf --output output.md

# Full result as JSON (includes per-page segments, token usage, parsers_used)
lexoid parse --input document.pdf --format json --output result.json

# Explicit LLM parsing (forces an LLM regardless of routing). LLM-based: load .env first.
lexoid parse --input document.pdf --parser-type LLM_PARSE --model gpt-4o
lexoid parse --input document.pdf --parser-type LLM_PARSE --model claude-3-5-sonnet-20241022
lexoid parse --input scanned.pdf --parser-type LLM_PARSE --model mistral-ocr-latest

# Force static parsing (no LLM, no API key needed for PDFs)
lexoid parse --input document.pdf --parser-type STATIC_PARSE --framework pdfplumber

# Parse a URL
lexoid parse --input https://example.com --output page.md

# Tune chunking / parallelism
lexoid parse --input big.pdf --pages-per-split 8 --max-processes 8

# Inline schema
lexoid schema \
  --input invoice.pdf \
  --schema '{"type":"object","properties":{"invoice_number":{"type":"string"},"total":{"type":"number"}}}' \
  --output invoice.json

# Schema from file, explicit provider
lexoid schema --input invoice.pdf --schema schema.json --api openai --model gpt-4o

# Example-guided extraction (improves accuracy)
lexoid schema --input invoice.pdf --schema schema.json \
  --example-schema example.json

# Treat the whole doc as one instance (vs. one per page)
lexoid schema --input contract.pdf --schema schema.json --fill-single-schema

lexoid latex --input paper.pdf --output paper.tex
lexoid latex --input paper.pdf --model gpt-4o

lexoid parse --input report.pdf | grep -i "revenue"
lexoid parse --input report.pdf --format json | jq '.token_usage'

© oidlabs-com, Apache-2.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in skills/lexoid-cli of oidlabs-com/Lexoid.

Open the folder on GitHubat commit b45d174