Skip to content
TrustedSkillsbeta
Back to all skills

Creating Openlineage Extractors

Checked
astronomer·vlatest·data·Apache-2.0

This skill generates OpenLineage extractor scripts to track data lineage, improving data observability and trust across your systems.

Repository

Install on your platform

Showing Claude Code. One command installs this skill into any of the agents below.

  1. 1

    Run this in your project

    terminal
    $ npx skills add astronomer/agents --skill creating-openlineage-extractors -a claude-code

  2. Uses the open-source skills CLI and needs Node.js. Add -g to install it for your user instead of this project.

What we know about this skill

Publisher

astronomer

Taken from the source listing. We haven't verified who controls this account.

Install target

Live repository

Not pinned. Installing fetches whatever the repository holds at the time you run the command.

No human has reviewed this code. The checks below are a static scan of the files at one commit — nobody has run this skill or judged whether it works. A skill runs with whatever access you give your agent, so read the source before you install it.

Automated safety checks

scanned

This skill passed all 6 checks. We read its files at one commit and looked for the things that make a skill dangerous to run — not for whether it works.

  • Declares what it does: passed

    SKILL.md parses and declares a name and a description.

    SKILL.md exists, its frontmatter parses, and it declares a name and a description.

  • No undeclared network calls: passed

    Makes no network calls.

    Every host the skill dials — from its scripts, its config endpoints or the commands it tells the agent to run — is either well-known package and API infrastructure or declared in its own frontmatter. Links in documentation are not counted.

  • No obfuscated payloads: passed

    No encoded or obfuscated payloads.

    No base64, hex or compressed blob is decoded and then executed, and no encoded shell commands.

  • No credential access: passed

    Reads no keys, tokens, keychains or credential files.

    Neither the code nor the SKILL.md instructions read SSH keys, cloud credentials, keychains, token stores, browser cookie databases or dotfiles that hold secrets.

  • No pipe-to-shell installers: passed

    No pipe-to-shell or download-and-run installers.

    No `curl … | sh` pattern, in the code or in the instructions, that runs code fetched at run time.

  • Pinned to a commit: passed

    Scanned astronomer/agents at cbe1141f54.

    The exact upstream commit SHA that was scanned is recorded, so the result refers to specific bytes.

Commit
cbe1141f54
Manifest
skills/creating-openlineage-extractors/SKILL.md
Scanned
1 file, 380 lines
This is a static scan, not a review. It reads the skill's files; it does not run them, and it cannot tell you whether the skill is any good or whether the code does what its description says. A skill runs with whatever access you give your agent.
What each check looks for →

About this skill

What it does

This skill enables the creation of OpenLineage extractors, which are used to collect and track metadata about data processing workflows. It allows users to define how data lineage is captured from various data processing systems, ensuring transparency and traceability in data pipelines.

When to use it

  • You need to implement data lineage tracking for ETL processes or data transformations.
  • Your organization requires audit trails or compliance reporting on data flows.
  • You are integrating with tools like Apache Airflow or other orchestration platforms that support OpenLineage.

Key capabilities

  • Generate custom extractors for different data processing frameworks.
  • Define metadata schemas and event types for lineage tracking.
  • Integrate with existing data infrastructure to capture lineage events automatically.

Example prompts

  • "Create an OpenLineage extractor for Apache Spark jobs running in our cluster."
  • "Generate a Python-based OpenLineage extractor that captures schema changes during data transformations."
  • "Set up an extractor to log metadata from our Flink pipelines into the OpenLineage API."

Tips & gotchas

  • Ensure your environment has the necessary dependencies, such as the OpenLineage SDK and compatible data processing tools.
  • Custom extractors may require domain-specific knowledge of the systems they are monitoring for accurate lineage tracking.