rye-tabular-intake

Extract CSV and XLSX rows into NDJSON with source lineage tracking.

2|Updated Feb 20, 2026
One-click install
npx skills add https://github.com/BLTGV/project-rye --skill rye-tabular-intake
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: rye-tabular-intake
Source: https://github.com/BLTGV/project-rye/tree/main/skills/rye-tabular-intake
Command: npx skills add https://github.com/BLTGV/project-rye --skill rye-tabular-intake

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) and assets (resource) components.

What problem does it solve?

This Skill eliminates the tedious, error-prone manual work of processing CSV and XLSX source files for database imports, while preserving full source lineage and auditability for Rye-tracked data workflows.

Core Features & Use Cases

  • Lossless Tabular Extraction: Inspect and extract CSV/XLSX rows into NDJSON with stable source lineage, no data loss.
  • Flexible Field Mapping: Map source columns to destination records using simple declarative configs or custom TypeScript logic for complex transforms.
  • Many-to-One Grouping: Group multiple source rows into parent records with full source-set tracking, ideal for invoice lines to parent invoices.
  • Rye Audit Integration: Stage and commit intake trails to Rye for full traceability, duplicate detection, and change review before final database loads. A common use case is importing customer spreadsheets into a CRM, where every source row, mapping step, and grouped parent record is tracked in Rye's append-only audit model.

Quick Start

Use the rye-tabular-intake skill to inspect your sales spreadsheet, map its columns to your Rye contacts table, and commit the full intake lineage to your Rye database.

Frequently Asked Questions about rye-tabular-intake

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

FAQPage Schema
How do I import CSV and XLSX files into a database while preserving source lineage?

To import CSV and XLSX files while preserving source lineage, you can extract rows into NDJSON with stable tracking, apply field mapping, and commit the full intake trail to an append-only audit model for traceability.

What is the best way to map spreadsheet columns to database records with complex transforms?

The best way to map spreadsheet columns to database records is by using declarative configs for simple alignment or custom TypeScript logic for complex transforms, ensuring deterministic mapping during the tabular extraction process.

Can I group multiple source rows into a single parent record during tabular data extraction?

Yes, you can group multiple source rows into a single parent record during tabular data extraction. This many-to-one grouping tracks the full source-set, which is ideal for mapping invoice lines to parent invoices.

Does Rye integration support duplicate detection and change review before final database loads?

Rye integration supports duplicate detection and change review before final database loads by staging intake trails and committing them to Rye's audit model, allowing full traceability and data validation prior to loading.

How do I commit extracted tabular data to PostgreSQL using a SQL-only approach?

You can commit extracted tabular data to PostgreSQL using either a direct PostgreSQL commit option or a SQL-only approach, enabling flexible database integration for Rye-tracked intake pipelines.

When should I use declarative config versus TypeScript modules for data mapping?

Use declarative config for straightforward column-to-record alignment, and switch to custom TypeScript modules when your data mapping requires complex transforms or conditional logic to accurately process tabular source data.