neqsim-document-intelligence-extraction

Classify engineering documents and route native text, OCR, and vision extraction into traceable evidence packages.

4|2|Updated May 31, 2026
One-click install
npx skills add https://github.com/equinor/neqsim-community-skills --skill neqsim-document-intelligence-extraction-equinor
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: neqsim-document-intelligence-extraction
Source: https://github.com/equinor/neqsim-community-skills/tree/main/skills/engineering-data/document-intelligence-extraction
Command: npx skills add https://github.com/equinor/neqsim-community-skills --skill neqsim-document-intelligence-extraction-equinor

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Engineering tasks often receive mixed inputs—PDFs, scans, Word and Excel files, drawings, charts, and photographs—where values extracted without provenance can silently enter simulations or safety decisions. This Skill classifies each source, plans the right extraction operations, and packages every fact with original text, page or locator, confidence, and review status so nothing unverified reaches downstream NeqSim workflows. ## Core Features & Use Cases - Source Classification and Routing: Detects PDF, Office, spreadsheet, text, and image formats and builds an ordered ExtractionPlan covering native text, tables, OCR, rendering, and vision steps. - Evidence Contract: Every fact carries original text, unit, page or locator, extraction method, confidence, and an automatic review gate for safety-critical, ambiguous, or low-confidence values. - Conflict Detection: Compares normalized values across multiple sources and reports disagreements as review items instead of silently picking one. - Use Case: Given a scanned equipment datasheet PDF plus a conflicting Excel specification, plan OCR and table extraction, capture design pressure with its page citation, and flag the mismatch between sources for human review before running a NeqSim simulation. ## Quick Start Ask the agent to classify the attached engineering PDF and produce a source-traceable evidence package of its design values with confidence scores and review flags.

Frequently Asked Questions about neqsim-document-intelligence-extraction

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

FAQPage Schema
How do I extract data from scanned engineering PDFs?

Scanned PDFs have little or no embedded text, so the plan renders each page and runs OCR with word coordinates, keeping OCR text separate from native text. Vision steps then interpret drawings, charts, and symbols that OCR alone cannot understand.

How do I handle conflicting values across engineering documents?

Use the find_conflicts function, which groups facts by field across ExtractionResult objects and reports any field whose normalized values differ. Conflicts are emitted as needs_review records rather than being silently resolved.

Can I use Markdown conversion for PDF data extraction?

Markdown normalization is allowed only as a reading and triage aid, never as an evidence method, because it joins pages and loses page boundaries. EvidenceFact rejects the markdown_normalize method; cite pages from native_text, native_tables, or ocr output instead.

What file formats does document extraction support?

Supported families include PDF, DOCX/ODT, XLSX/CSV/ODS, PPTX, plain text, HTML, XML, JSON, and common raster images such as PNG, JPEG, and TIFF. Unknown or unsupported formats are routed to manual triage rather than guessed.

Why does an extracted fact get flagged as needs_review?

A fact is marked needs_review when it is safety-critical, ambiguous, or has confidence below 0.85. Facts missing original text or a page/locator are rejected entirely, since unverifiable values must not enter simulations.

What are the limitations of OCR-based engineering extraction?

OCR quality depends on the runtime adapter and source quality; handwriting, faint scans, dense drawings, and unusual fonts may need specialist tools or manual transcription. Confidence is a triage signal, not proof of correctness, and the skill does not infer missing values.