annotating-task-lineage

Annotate Airflow tasks with inlets and outlets for data lineage.

2|Updated Jan 15, 2026
One-click install
npx skills add https://github.com/Abhinow1997/pe-orgair-platform --skill annotating-task-lineage-abhinow1997
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: annotating-task-lineage
Source: https://github.com/Abhinow1997/pe-orgair-platform/tree/main/airflow/.agents/skills/annotating-task-lineage
Command: npx skills add https://github.com/Abhinow1997/pe-orgair-platform --skill annotating-task-lineage-abhinow1997

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Annotate Airflow tasks to attach lineage metadata, enabling visibility into data flow and easier governance across DAGs.

Core Features & Use Cases

  • Manual lineage: add inlets and outlets to tasks that lack OpenLineage extractors.
  • Flexible integration: support OpenLineage Dataset objects or Airflow Assets as lineage endpoints.
  • Use Case: quickly annotate a simple operator to mark its inputs and outputs for downstream lineage tooling.

Quick Start

Annotate an Airflow task by configuring inlets and outlets to define its data inputs and outputs.

Frequently Asked Questions about annotating-task-lineage

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I add data lineage annotations to Airflow tasks using inlets and outlets?

To add data lineage annotations to Airflow tasks, configure the inlets and outlets properties on the operator to define data inputs and outputs for downstream lineage tooling.

When do I need to manually attach lineage metadata to an Airflow operator?

You need to manually attach lineage metadata when an Airflow operator lacks built-in OpenLineage extractors or when you prefer manual lineage configuration for specific data flow visibility.

Does this approach support both OpenLineage Dataset objects and Airflow Assets for lineage?

Yes, flexible integration supports both OpenLineage Dataset objects and Airflow Assets to serve as lineage endpoints when you annotate tasks with inlets and outlets.

What is the best way to annotate a simple Airflow operator for OpenLineage tracking?

The best way to annotate a simple operator is by configuring its inlets and outlets according to OpenLineage guidance, marking its inputs and outputs for downstream lineage tooling.

Can I use inlets and outlets to enable data governance visibility across DAGs?

Yes, attaching lineage metadata to tasks via inlets and outlets enables visibility into data flow and easier governance across your Airflow DAGs.