Skip to content
OpenAgentSkill
Browsing is open · Catalog captured 2026-11-21 · Automatic updates and account services are paused.
Documents

odl-pdf

Procedure for extracting structured data from PDFs with opendataloader-pdf (ODL) correctly: read the installed tool's own help to discover its current options, build the minimal command for the user's goal, verify the extraction actually succeeded, and diagnose silent failures the tool does not report. Use when the user is using, evaluating, or considering opendataloader-pdf/ODL to extract, parse, or convert PDF content to text, markdown, JSON, or HTML — including scanned-PDF OCR, tables, bounding boxes, or a RAG pipeline over PDFs. Do NOT use for PDF merge/split/rotate, Office-format conversion, form filling, or PDF/UA accessibility-compliance tagging.

opendataloader-project · AI review on file

Installation

Read the source and dependencies before running a command. Copying does not install or execute anything.

npx skills add opendataloader-project/opendataloader-pdf --skill odl-pdf

About this skill


name: odl-pdf description: > Procedure for extracting structured data from PDFs with opendataloader-pdf (ODL) correctly: read the installed tool's own help to discover its current options, build the minimal command for the user's goal, verify the extraction actually succeeded, and diagnose silent failures the tool does not report. Use when the user is using, evaluating, or considering opendataloader-pdf/ODL to extract, parse, or convert PDF content to text, markdown, JSON, or HTML — including scanned-PDF OCR, tables, bounding boxes, or a RAG pipeline over PDFs. Do NOT use for PDF merge/split/rotate, Office-format conversion, form filling, or PDF/UA accessibility-compliance tagging. license: Apache-2.0 compatibility: > Requires an installed opendataloader-pdf runtime plus whatever prerequisites that installed version declares. Do not assume a specific runtime version; discover the requirement from the installed package and its help.

opendataloader-pdf usage skill

This skill is not a catalogue of ODL's current options. It is a procedure for reading the interface the currently-installed ODL exposes, solving the user's problem with it, verifying the result, and avoiding the silent failures that interface does not reveal. Option names, values, and defaults change between releases, so this skill never spells them — it teaches you to discover them at runtime and interpret them. It is written for any AI agent.

Purpose

Help a user extract data from PDFs with ODL correctly: translate their goal into a capability, discover the option that expresses it from the installed tool, run the minimal command, verify the extraction against their intent, and diagnose failures. The single fact that motivates every step: a zero exit code does not mean the extraction succeeded. Command success and extraction success are different things, and several ODL behaviors return a clean exit while silently dropping what the user asked for. Guarding against that is this skill's core job.

Source-of-truth rule

The installed tool describes itself. Before you build any command, read the installed help — invoke the tool with --help (or -h), and read the companion help of any separate server or backend component the task needs. That output is the authority for this environment: the options it lists, the values it accepts, and the defaults it names are what will actually run.

Authority order, when sources disagree:

  1. Installed --help / -h — the truth for the user's version. Always wins.
  2. Official published CLI reference — supplementary only, for discovery when the tool is not yet runnable. Its version may differ from the user's, so treat anything from it as provisional until confirmed against the installed help.
  3. Your own memory of past option names — not a source. Never put an option into a generated command because you remember it; confirm it in the installed help first.

Probe when help is insufficient. --help is a syntax reference; it may not say whether an option operates (a backend flag can be listed while no backend is running) or how two options interact. When help does not settle it, run a small safe probe — a tiny input, a throwaway output directory, a reachability check — observe the real result, and confirm from that. Never assert behavior you have not either read in help or observed in a probe.

Reading this skill's own files. Every references/… and scripts/… path in this skill resolves against the directory containing this SKILL.md, not your current working directory. Your harness exposes that base directory; resolve siblings from there. If a path does not resolve, locate this SKILL.md's directory and read the sibling from there — do not skip a reference or invent its contents.

Representative workflow (interpret the help, don't recite it)

This is the procedure, shown once end-to-end. It uses a placeholder convention for anything version-specific: <the … option help lists> means "the option you find in the installed help that provides this capability" — you resolve the real name at runtime, you do not type the placeholder.

  1. Goal → capability. Restate the user's ask as a capability the tool might provide, not as a flag. Common capabilities: choose an output format; select a processing mode (in-tool vs. an AI/OCR backend); enable OCR for scanned pages; control table handling; select pages; choose an output destination; stream to stdout. Example: "I need citations back to page and region" → capability = an output format that carries position metadata.

  2. Search the installed help for the item that expresses that capability. Read the help text; find the option whose description matches the capability. Note its exact name and the values it documents — from the help, not memory.

  3. Confirm values and defaults from help. If the option takes a value, read which values the help lists and what the default is. If the default already does what the user wants, you may not need the option at all.

  4. Build the minimal command. Start with the simplest thing that can satisfy the goal — the fewest options, the least-complex mode. Prefer the in-tool local path before invoking any AI/OCR backend; add complexity only when a verified result shows it is needed. Shape:

    opendataloader-pdf <input> <the output-format option help lists> <the output-destination option> <the quiet/no-log option>
    

    Fill each placeholder with the real name you read in step 2.

  5. VERIFY (next section) — never stop at the exit code.

  6. Expand one step if insufficient. If verification shows the goal is not met, add exactly one capability (e.g. escalate table handling, or move to the AI/OCR backend), re-run, and verify again. One change at a time keeps cause and effect legible. Loop back to step 2 for each new capability.

Wh

Read the complete source ↗