Etl lineage explainer

Skill sisodiabhumca/agent-skills/skills/etl-lineage-explainer

Production-Ready Agent Skills : product analytics, growth experiments, CRM, research synthesis, postmortems, data contracts, SaaS spend, compliance, architecture maps, and LLM eval and many more.

Install

npx -y skills add sisodiabhumca/agent-skills --skill etl-lineage-explainer

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

Vendor-neutral skill for extracting and summarizing table-level lineage from SQL-based ETL jobs.

SKILL.md

1.5 KB, as published. Nobody here has run it

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

Read each SQL file and strip comments.
Identify common ETL patterns:
- INSERT INTO <target> ... FROM <source>
- CREATE TABLE <target> AS SELECT ... FROM <source>
- CREATE VIEW <target> AS SELECT ... FROM <source>
Extract:
- Target object name
- Source object names from FROM and JOIN
- File name where found
Produce a consolidated lineage graph:
- Targets with their sources
- Reverse index: source → downstream targets
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