tda-document-ingestion

Convert PDFs, DOCX, XLSX, and web captures into vault-ready Markdown artifacts.

1|Updated Dec 13, 2025
One-click install
npx skills add https://github.com/ZK-Theory/TDL --skill tda-document-ingestion-zk-theory
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: tda-document-ingestion
Source: https://github.com/ZK-Theory/TDL/tree/main/.agents/skills/tda-document-ingestion
Command: npx skills add https://github.com/ZK-Theory/TDL --skill tda-document-ingestion-zk-theory

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Research documents arrive in formats like PDF, DOCX, XLSX, and web captures that cannot be cited or computed on directly, and naive conversion silently mangles tables and equations. This Skill converts them into Markdown or structured artifacts while explicitly flagging uncertain OCR regions and keeping converted text clearly separated from verified sources. ## Core Features & Use Cases - Source-Type Routing: Identifies whether a document is an academic paper, survey codebook, official report, reviewer attachment, or web capture, then routes it to the correct downstream workflow such as literature verification or wave-crosswalk checks. - Parser Selection and Conversion: Chooses the lightest suitable parser (simple conversion, layout-aware extraction, table extraction, or manual inspection) and preserves page and section anchors for later citation. - Provenance and Caveat Recording: Produces a required output record capturing source path, parser used, conversion command, layout caveats, and verification status so extracted numbers are treated as unverified until checked. - Use Case: A researcher receives a survey codebook PDF whose table will drive a variable recode. The Skill extracts the table, flags uncertain cells, records the conversion caveats, and routes the coding claim through the wave-crosswalk check before use. ## Quick Start Convert the attached codebook PDF into a Markdown artifact with page anchors, flag any uncertain table cells, and record the parser and caveats in the output header.

Frequently Asked Questions about tda-document-ingestion

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

FAQPage Schema
How do I convert a PDF or DOCX into Markdown for a research vault?

Identify the source type first, then pick the lightest parser that preserves what matters: simple conversion, layout-aware extraction, or table extraction. Preserve page and section anchors in the output so later citations can point back into the source.

Can I cite text extracted from a PDF directly in a paper?

No. Converted text is not automatically a verified source, and OCR or table extraction is provisional until checked. Academic sources must go through the literature-verification workflow before being cited in drafts.

How should extracted tables that drive variable recodes be handled?

Treat numbers extracted from tables as unverified until checked against the source rendering. Flag uncertain cells explicitly, and route any survey coding claims through the wave-crosswalk check before computing on them.

What should I do when OCR or table extraction quality is poor?

Say so explicitly rather than presenting a lossy conversion as the source. Flag uncertain OCR regions, equations, and tables in the artifact, and record the limitations in the output header.

What are the limitations of automated document conversion for research?

Conversion does not establish provenance or verify content; documents with unclear authorship must be identified before use. Silently mangled tables are worse than no table, so manual verification is required for anything that will be cited or computed on.