Data Lineage Tracker - Auto-activating skill for Data Pipelines. Triggers on: data lineage tracker, data lineage tracker Part of the Data Pipelines skill category.
33
Quality
3%
Does it follow best practices?
Impact
85%
0.98xAverage score across 3 eval scenarios
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./planned-skills/generated/11-data-pipelines/data-lineage-tracker/SKILL.mdETL lineage metadata tracking
Lineage event file created
100%
100%
Structured JSON format
100%
100%
Input dataset recorded
100%
100%
Output dataset recorded
100%
100%
Job name specified
100%
100%
Unique run ID
100%
100%
Timestamp recorded
100%
100%
Record counts captured
100%
100%
Error handling present
0%
0%
Multiple event states
37%
25%
Standard library or format used
12%
0%
Without context: $0.3721 · 1m 18s · 20 turns · 20 in / 4,829 out tokens
With context: $0.4873 · 1m 42s · 26 turns · 25 in / 6,019 out tokens
Airflow workflow lineage integration
DAG file produced
100%
100%
Retry delay configured
100%
100%
Task dependencies defined
100%
100%
Standard default_args
70%
70%
Dataset lineage annotations
100%
100%
Dataset namespace and name
100%
80%
No hardcoded secrets
100%
100%
Step-by-step documentation
100%
100%
Production-ready structure
100%
100%
Industry standard approach
100%
100%
Without context: $0.3821 · 2m · 19 turns · 20 in / 6,702 out tokens
With context: $0.4609 · 1m 57s · 24 turns · 283 in / 6,884 out tokens
Data quality validation with lineage
Four or more quality rules
100%
100%
Cleaned output CSV written
100%
100%
Lineage file produced
100%
100%
Source dataset in lineage
100%
100%
Output dataset in lineage
100%
100%
Per-check statistics
100%
100%
Run timestamp
100%
100%
Run identifier
87%
100%
Overall pass/fail outcome
100%
100%
Error handling
50%
50%
Structured logging
0%
0%
Standard lineage schema fields
33%
16%
Without context: $0.3331 · 1m 24s · 18 turns · 18 in / 5,231 out tokens
With context: $0.4350 · 1m 32s · 24 turns · 57 in / 5,605 out tokens
0c08951
Table of Contents
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.