data_engineer

Design multi-tenant JSONB schemas and ETL pipelines for RetentionAI.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/ColbyRReichenbach/retentionAI --skill data-engineer-colbyrreichenbach
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: data_engineer
Source: https://github.com/ColbyRReichenbach/retentionAI/tree/main/.claude/skills/data_engineer
Command: npx skills add https://github.com/ColbyRReichenbach/retentionAI --skill data-engineer-colbyrreichenbach

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

RetentionAI requires robust, scalable multi-tenant data architectures to support JSONB flexibility, efficient ETL pipelines, and strict data quality and isolation guarantees across many organizations.

Core Features & Use Cases

  • Multi-tenant JSONB schema patterns with fixed universal fields and flexible custom attributes.
  • End-to-end ETL pipelines (GA4, Stripe, Shopify) with data quality validation and indexing strategies.
  • Data generation, seeding, and synthetic data support for testing and onboarding new tenants.
  • Tenant isolation via org_id, role-based access, and migration tooling (Alembic) for safe schema evolution.

Quick Start

Initialize a new organization by creating the org record, applying the universal tables, and wiring an ETL workflow to ingest GA4 data.

Frequently Asked Questions about data_engineer

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

FAQPage Schema
How do I design a multi-tenant data schema with PostgreSQL JSONB?

Design multi-tenant PostgreSQL schemas by combining fixed universal fields with flexible JSONB custom attributes, enforcing strict tenant isolation via org_id, and optimizing indexes for scalable query performance.

What's the best way to build ETL pipelines for GA4, Stripe, and Shopify data?

Build scalable ETL pipelines for GA4, Stripe, and Shopify by integrating data quality validation checks and indexing strategies to ensure reliable ingestion and structured storage across tenants.

How does tenant isolation work in a multi-tenant data architecture?

Tenant isolation in multi-tenant architectures works by enforcing an org_id column across universal tables, applying role-based access controls, and using migration tooling to safely evolve schemas without cross-tenant data leaks.

Can I use Alembic migrations for multi-tenant schema evolution?

Yes, you can use Alembic migrations for multi-tenant schema evolution to safely apply structural changes and maintain data integrity across universal tables while preserving existing tenant data.

How do I generate synthetic data for testing multi-tenant ETL workflows?

Generate synthetic data for multi-tenant workflows by seeding test records with varied JSONB custom attributes and unique org_id values to validate data quality monitoring and replay pipelines.

What are the limitations of JSONB patterns for multi-tenant data quality?

JSONB limitations in multi-tenant data quality include potential indexing overhead and flexible schema validation challenges, requiring strict universal field enforcement and active data quality monitoring to prevent inconsistent tenant records.