data-ingestion-pipeline

Build batch and streaming data ingestion pipelines with extraction, validation, deduplication, and staging.

Updated May 16, 2026
One-click install
npx skills add https://github.com/organvm-i-theoria/_agent-ontology --skill data-ingestion-pipeline-organvm-i-theoria
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: data-ingestion-pipeline
Source: https://github.com/organvm-i-theoria/_agent-ontology/tree/main/.agents/skills/data-ingestion-pipeline
Command: npx skills add https://github.com/organvm-i-theoria/_agent-ontology --skill data-ingestion-pipeline-organvm-i-theoria

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires httpx, asyncpg, pyyaml.

What problem does it solve? Moving data from APIs, files, and databases into target systems often produces corrupt, duplicated, or silently lost records when pipelines lack validation gates and staging. This Skill provides a structured extract-validate-transform-stage-load workflow that prevents bad data from reaching production systems. ## Core Features & Use Cases - Multi-Source Extraction: Pull records from JSON/YAML/CSV files, paginated REST APIs via httpx, and databases via asyncpg with batched cursors. - Validation & Deduplication: Apply schema and business-rule validation gates, then deduplicate records with configurable merge strategies (keep first, keep latest, merge fields). - Staging & Orchestration: Stage batches with metadata tracking before promotion, and orchestrate the full pipeline through composable extractor, validator, transformer, and loader components. - Use Case: Importing thousands of records from a third-party API into a database—extract paginated results, validate required fields, deduplicate on ID, stage the batch for inspection, then load with row-count verification. ## Quick Start Ask the AI to build a data ingestion pipeline that extracts records from a paginated REST API, validates them against a schema, deduplicates by ID, and stages the batch before loading into a database.

Frequently Asked Questions about data-ingestion-pipeline

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

FAQPage Schema
How do I build a data ingestion pipeline in Python?▼

Structure the pipeline as composable stages: extract from sources, validate against a schema, transform and deduplicate, stage the batch, then load. The IngestionPipeline class coordinates an extractor, validator, transformer, and loader, returning counts of extracted, valid, invalid, and loaded records.

How to extract data from a paginated REST API with httpx?▼

Use an async httpx client loop that requests pages with page and per_page parameters until an empty result set is returned. Accumulate records from each response's items or results field into a single list before downstream processing.

How do I deduplicate records during data ingestion?▼

Build a key tuple from designated key fields for each record and skip records whose key was already seen. For merging duplicates, choose a strategy: keep first, keep latest, or merge fields by overlaying non-null values across the duplicate group.

Why should data be staged before loading into a database?▼

Staging writes each batch to an intermediate directory with metadata (record count, timestamp, status) before promotion to the target. This enables inspection, rollback, and re-runs without corrupting the destination, and supports idempotent pipeline behavior.

What are common data ingestion pipeline anti-patterns?▼

Common anti-patterns include skipping validation gates, loading directly from source without staging, ignoring deduplication, silently dropping invalid records, building monolithic non-composable pipelines, and lacking idempotency so re-runs produce inconsistent results.