armor-lineage

Name: armor-lineage
Availability: InStock
Author: anomalyarmor

Map upstream sources and downstream consumers of data assets.

1|Updated Jan 31, 2026

Search Tags:#data flow #dependencies #impact analysis #data lineage #upstream #downstream

Ready to run

npx skills add https://github.com/anomalyarmor/agents --skill armor-lineage

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: armor-lineage
Source: https://github.com/anomalyarmor/agents/tree/main/skills/lineage
Command: npx skills add https://github.com/anomalyarmor/agents --skill armor-lineage

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires anomalyarmor, and includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill helps you understand how data flows through your systems, identifying dependencies and potential impacts of changes.

Core Features & Use Cases

Visualize Data Flow: Trace data upstream to its sources and downstream to its consumers.
Impact Analysis: Understand which downstream systems or reports will be affected by changes to a specific table.
Root Cause Analysis: Identify the origin of data issues by tracing back through dependencies.
Use Case: Before modifying a critical fact_orders table, use this Skill to see all the dashboards, ML models, and other tables that rely on it, ensuring no unintended consequences.

Quick Start

Use the armor-lineage skill to find all upstream dependencies for the asset 'asset-uuid' with a depth of 2.

Frequently Asked Questions about armor-lineage

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

FAQPage Schema

How do I trace data lineage and dependencies for a specific asset?▼

Trace data lineage by querying the asset to map upstream sources and downstream consumers. This maps your data's journey through the ecosystem to visualize dependencies and understand data flow.

What is impact analysis and how does it work for downstream data consumers?▼

Impact analysis identifies downstream systems and reports affected by changes to a specific table. It traces data flow to critical assets, ensuring no unintended consequences occur before modifying dependencies.

How can I perform root cause analysis by tracing upstream data flow?▼

Perform root cause analysis by tracing upstream dependencies back to their sources. This identifies the origin of data issues within the ecosystem, facilitating investigation for critical assets.

Do I need API credentials to map data dependencies?▼

Yes, you need configured API credentials and the AnomalyArmor Python SDK to access lineage information. These prerequisites are required to explore upstream and downstream dependencies within the data ecosystem.

Can I check the impact of modifying a fact table on ML models and dashboards?▼

Yes, impact analysis reveals all dashboards, ML models, and tables relying on a specific fact table. Mapping downstream consumers ensures modifications to critical assets do not cause unintended consequences.