etl-lineage-explainer
Vendor-neutral skill for extracting and summarizing table-level lineage from SQL-based ETL jobs.
Works with
---
name: etl-lineage-explainer
description: Vendor-neutral skill for extracting and summarizing table-level lineage from SQL-based ETL jobs.
license: MIT
---
## When to invoke
- You have a folder of SQL files (or a single SQL script) that implements ETL/ELT.
- You need a quick, readable lineage view: sources → targets, plus joins/filters hints.
- You want a lightweight, vendor-neutral approximation (not a full SQL parser).
## Inputs needed
- Path to one SQL file or a directory containing `.sql` files.
- (Optional) Output path for a JSON summary.
## Workflow
1. Read each SQL file and strip comments.
2. Identify common ETL patterns:
- `INSERT INTO <target> ... FROM <source>`
- `CREATE TABLE <target> AS SELECT ... FROM <source>`
- `CREATE VIEW <target> AS SELECT ... FROM <source>`
3. Extract:
- Target object name
- Source object names from `FROM` and `JOIN`
- File name where found
4. Produce a consolidated lineage graph:
- Targets with their sources
- Reverse index: source → downstream targets
5. Emit both a human-readable markdown summary and machine-readable JSON.
## Output format
- JSON with:
- `edges`: list of `{source, target, file}`
- `targets`: `{target: {sources: [...], files: [...]}}`
- `sources`: `{source: {targets: [...], files: [...]}}`
- Markdown summary printed to stdout.
## Guardrails
- Best-effort parsing only; do not claim completeness.
- Avoid inferring schema ownership or PII.
- Treat quoted identifiers and database-specific syntax conservatively.
## Reference code
- `etl_lineage_explainer.py`More Data Engineering skills
data-pipeline
claude-office-skills/skills
Data pipeline and ETL automation - extract, transform, load workflows for data integration and analytics
ETL Pipeline
claude-office-skills/skills
Design and automate Extract, Transform, Load data pipelines for data integration and analytics
data-throughput-accelerator
affaan-m/ecc
Use when large data ingestion, backfill, export, ETL, warehouse loading, manifest catch-up, or table synchronization needs to become much faster while preserving data correctness.

