llm-extraction-formfill

Convert OCR text into structured JSON with provenance and uncertainty.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/JustinChaney2023/orate --skill llm-extraction-formfill
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: llm-extraction-formfill
Source: https://github.com/JustinChaney2023/orate/tree/main/roles/llm-extraction-formfill
Command: npx skills add https://github.com/JustinChaney2023/orate --skill llm-extraction-formfill

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Convert OCR/transcript text into a structured JSON form with provenance and uncertainty using local LLMs. Use when implementing extraction prompts, schema-constrained decoding, validation, and safe form-filling (no hallucinations).

Core Features & Use Cases

  • Schema-guided extraction with provenance and uncertainty
  • Deterministic validators and a safe form-filling workflow
  • Reusable prompts and schemas to extract structured fields from documents

Quick Start

Use the llm-extraction-formfill skill to transform an OCR transcript into a filled_form.json with value, confidence, source_spans, and rationale.

Frequently Asked Questions about llm-extraction-formfill

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I convert OCR text to structured JSON with provenance?

To convert OCR text to structured JSON with provenance, you can use schema-guided extraction to emit a filled_form.json containing value, confidence, source_spans, and rationale for each field.

What is the best way to fill forms from transcripts without hallucinations?

The best way to fill forms from transcripts without hallucinations is applying deterministic validators and schema-constrained decoding to return unknown_reason when derivation is not possible.

Does schema-constrained decoding work with local LLMs for document extraction?

Yes, schema-constrained decoding works with local LLMs for document extraction by applying extraction prompts and validation workflows to safely fill structured fields from OCR transcripts.

How do I track uncertainty and source spans during JSON extraction?

To track uncertainty and source spans during JSON extraction, the workflow emits fields for confidence, source_spans, and rationale alongside the extracted value in the structured output.

Why does my OCR to JSON extraction return unknown_reason for certain fields?

Your OCR to JSON extraction returns unknown_reason when the schema-guided extraction process determines that derivation of a specific field is not possible from the available document text.

Can I use reusable prompts and schemas to extract structured fields from documents?

Yes, you can use reusable prompts and schemas to extract structured fields from documents, enabling deterministic validation and safe form-filling across multiple OCR transcripts.