Skip to content
TrustedSkillsbeta
Back to all skills

Tracing Downstream Lineage

Checked
astronomer·vlatest·devops·Apache-2.0

This skill traces the origin of a given concept or event by mapping its subsequent developments and influences – useful for understanding complex relationships.

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 tracing-downstream-lineage -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.

Scanned
1 file, 153 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

The tracing-downstream-lineage skill enables users to trace how data flows through a system, identifying all downstream processes and dependencies that are affected by changes in upstream data sources. It helps visualize and understand the impact of modifications or updates in data pipelines.

When to use it

  • When debugging issues caused by changes in source data
  • Before making significant updates to ensure no downstream systems are disrupted
  • To audit how data is transformed and consumed across different stages

Key capabilities

  • Tracing dependencies from a given data source
  • Visualizing the flow of data through pipelines
  • Identifying affected processes when upstream data changes

Example prompts

  • "Show me all downstream processes impacted by this dataset update."
  • "Trace the lineage of this data point to see where it's used."
  • "What systems are affected if I modify this table in the database?"

Tips & gotchas

  • Ensure that your data pipeline is properly instrumented for accurate tracing.
  • This skill may not work effectively with unstructured or loosely defined data flows.