← ClaudeAtlas

rudder-data-graphslisted

Produces Data Graph YAML from RETL sources for Audiences. Use when designing Data Graphs, mapping RETL to entities/events, or assessing customer fit for Audiences.
rudderlabs/rudder-agent-skills · ★ 19 · Data & Documents · score 77
Install: claude install-skill rudderlabs/rudder-agent-skills
# 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 1. `admin_search_organizations(company_name=...)` to get the `org_id`. 2. `admin_search_workspaces(search_by=organizationId)` using that id. 3. Keep only `status=ACTIVE` workspaces. *Why:* inactive workspaces often have stale or disconnected configs and will produce misleading source lists. 4. Note the likely warehouse-backed workspaces, but **do not assume you already have the correct `accou