chat-complex-documents

Featured

Chat with and search your complex documents — ask questions, extract tables and fields, and get answers grounded in the source. Connects the hosted Unstructured Transform MCP server to parse, structure, and enrich PDFs, Word/Excel/PowerPoint, images, scanned files, emails, and 60+ other formats into clean, AI-ready text for search, Q&A, and summarization without building a custom parsing pipeline.

Data & Documents 954 stars 145 forks Updated today MIT

Install

View on GitHub

Quality Score: 92/100

Stars 20%
99
Recency 20%
100
Frontmatter 20%
70
Documentation 15%
100
Issue Health 10%
50
License 10%
100
Description 5%
100

Skill Content

## What this does (in plain terms) You have documents — contracts, reports, slide decks, scanned PDFs, spreadsheets, emails, images — and you want the assistant to reliably get the content _out_ of them and make it usable: searchable, answerable, summarizable, or ready to feed a knowledge base or another tool. **Unstructured Transform** does exactly that. Hand it files and it turns them into clean, structured, AI-ready data across 60+ formats with one pipeline — no custom parsing or OCR to build and maintain. See the [Transform overview](https://docs.unstructured.io/transform/overview). Under the hood it: - **Partitions** each document into structured elements (titles, paragraphs, tables, lists), adjusting extraction per page for accuracy and cost. - **Enriches** the result with metadata, table and image descriptions, and entity recognition. The result is structured JSON that's ready for search, Q&A, summarization, and agents. ## Why people use it - **Make documents searchable and answerable.** Transform extracts clean, structured text and tables from your files so the assistant can search them and answer questions grounded in the source. - **Handle messy, varied files.** One integration covers 60+ formats (scanned PDFs, tables, images, Office files) instead of a per-format parser. ## When to use USE THIS SKILL WHEN: - The user wants to extract or structure content from documents (PDF, Office, images, emails, scanned files). - The user wants documents made searchabl...

Details

Author
vellum-ai
Repository
vellum-ai/vellum-assistant
Created
5 months ago
Last Updated
today
Language
TypeScript
License
MIT

Integrates with

Similar Skills

Semantically similar based on skill content — not just same category

Data & Documents Listed

data-tidy

Clean up messy data into a structured, validated table — from any source (a junk-filled .xlsx/CSV, a pasted email/markdown table, a Word table, or an Outlook .msg) to a clean .xlsx plus an audit/change report. Use when the user wants to "clean up this data", "tidy this spreadsheet", "normalise this list", "structure this messy export", "dedupe this", "standardise these dates / currencies", or "turn this into a clean table". (For getting data OUT of PDFs — tables, forms, scanned documents — use data-extract, not this skill.) Works INTENT-FIRST: it asks what the data is for and the expected output up front, then profiles → proposes a transform recipe → you confirm → applies it deterministically → reports every change and flags cells for review. Never mangles silently; transforms are computed locally by a deterministic engine. Standalone — no other toolkit required. NOT deal-document intelligence (lease abstraction, model review, comps) — that's out of scope.

0 Updated 5 days ago
moonlight-lupin
Data & Documents Listed

document-chunker

Use this skill when the task involves processing large files or document sets with Codex as the AI coworker: document ingestion, file inventory, parsing, chunking, structured extraction, embeddings preparation, retrieval QA, SEC/Form D processing, HypeStake knowledge ingestion, or auditing .chunks.jsonl outputs. All AI interpretation must be performed by Codex, not by bundled scripts.

0 Updated 3 days ago
andrewr303
Data & Documents Listed

data-extract

Get STRUCTURED data OUT of documents — PDFs (incl. multi-table/scanned via local OCR), Word, PowerPoint (.pptx), and Outlook .msg — into a clean .xlsx plus an audit report. Use when the user wants to "extract data from this PDF/document", "pull the table out of this report", "get the figures from these statements/certificates", "turn these confirmations into a table", "read the fields off this form", or "extract these line items". Two modes: key-value/FORM extraction (label → value, one record per document — certificates, confirmations, cover sheets) and TABLE extraction (list a document's tables, pick one, pull it). Intent-first; normalises via the shared engine (dates → DD MMM YYYY, currency → amount + code) and flags anything unfound or uncertain — never invents values. Extraction is computed locally (local OCR only). NOT for already-tabular data (use data-tidy) or deal-document intelligence like lease abstraction/model review (out of scope).

0 Updated 5 days ago
moonlight-lupin