ingest

Batch-import structured records into database collections with schema validation.

Updated Jul 23, 2026
One-click install
npx skills add https://github.com/platyplus/cairn-plugin --skill ingest-platyplus
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ingest
Source: https://github.com/platyplus/cairn-plugin/tree/main/cairn/skills/ingest
Command: npx skills add https://github.com/platyplus/cairn-plugin --skill ingest-platyplus

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill solves the risk of data corruption during bulk uploads by enforcing a strict, multi-step validation process that prevents silent errors and ensures data integrity.

Core Features & Use Cases

  • Schema-Aware Validation: Automatically shapes incoming data to match collection requirements, including enum values and reference lookups.
  • Safe Dry-Run Protocol: Provides a comprehensive report of validation errors and potential duplicates before any data is committed to the database.
  • Use Case: When you have a spreadsheet of field survey results, this skill helps you map the rows to your existing Cairn schema, verify the data against current constraints, and perform a safe, batch-insert operation.

Quick Start

Use the ingest skill to bulk upload the records from my attached CSV file into the health facilities collection.

Frequently Asked Questions about ingest

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

FAQPage Schema
How do I safely bulk import CSV records into existing database collections?

To safely bulk import data, you can use a validation workflow that maps your CSV rows to existing schema definitions, resolves references, and performs a dry run to catch errors before committing the batch.

What is a dry-run protocol for bulk data uploads?

A dry-run protocol for bulk uploads simulates the data import process to generate a report of validation errors and potential duplicates without writing any records to the database.

How does schema validation prevent data corruption during batch inserts?

Schema validation prevents data corruption by automatically shaping incoming data to match collection requirements, enforcing enum values, and resolving reference lookups before any write operation occurs.

Can I import structured records without defining a schema first?

No, importing structured records requires strict adherence to existing schema definitions to ensure data integrity, meaning the target collection schema must be established before the import workflow begins.

What is the best way to import spreadsheet data while preventing silent errors?

The best way to prevent silent errors during spreadsheet data import is to use a multi-step validation process that requires explicit confirmation before executing bulk write operations on the target collection.