RETL Connection Analysis & Data Graph Design

What this skill produces

Given a customer name (or workspace / org identifier), this skill produces five deliverables, in order:

1. Source Inventory — every relevant RETL source categorized as entity / event / audience / supporting-only.
2. Untapped Segment List — realistic, filterable business dimensions the customer has not yet expressed as audiences.
3. Data Graph YAML — one per workspace / domain, ready for validation in rudder-cli or the visual builder.
4. Demo Warehouse Spec — tables, key columns, joins, and known / inferred schema details needed to mock the graph.
5. Action Items — priority-ordered next steps, including the upgrade narrative and any assumptions to confirm.

The end-to-end flow is: find workspaces → list RETL sources → shortlist relevant sources → fetch full configs for the shortlist → categorize → design graph → validate → hand off. Each step below says what to do and why, so you can adapt when the customer doesn't match the common shapes.

Step 1 — Find the customer's workspaces