data-lineage-explanation

Document data lineage and traceability across financial data ecosystems.

1|1|Updated Feb 19, 2026
One-click install
npx skills add https://github.com/GoldenZero/skills --skill data-lineage-explanation-goldenzero
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: data-lineage-explanation
Source: https://github.com/GoldenZero/skills/tree/main/skills/data-lineage-explanation
Command: npx skills add https://github.com/GoldenZero/skills --skill data-lineage-explanation-goldenzero

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes assets (resource) and references (resource) components.

What problem does it solve?

This Skill helps financial institutions meticulously document and explain data traceability and lineage, ensuring compliance with stringent regulatory requirements and improving data governance.

Core Features & Use Cases

  • Regulatory Compliance: Supports BCBS 239 and FFIEC expectations for data governance and risk reporting.
  • Data Traceability: Traces data from its authoritative source through all transformations to its final consumption point.
  • Risk Assessment: Identifies data quality risks and supports model risk management by providing clear data provenance.
  • Use Case: When preparing for a BCBS 239 audit, use this Skill to generate a comprehensive lineage report for a critical risk metric, detailing its sources, transformations, and quality controls.

Quick Start

Explain the data lineage for the 'customer_credit_score' data element.

Frequently Asked Questions about data-lineage-explanation

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

FAQPage Schema
How do I document data lineage for BCBS 239 regulatory reporting?

Documenting data lineage for BCBS 239 involves tracing critical risk metrics from authoritative sources through transformations to consumption points. This Skill maps data provenance and identifies quality controls to generate comprehensive compliance reports.

What is data traceability and how does it support model risk management?

Data traceability tracks data elements from origin to final use across financial ecosystems. It supports model risk management by providing clear data provenance, identifying transformations, and mapping quality controls to ensure reliable risk assessment inputs.

How do I trace data quality controls from source to consumption?

Tracing data quality controls requires mapping data paths from source systems through all transformations to final consumption. This Skill documents lineage across financial data ecosystems, identifying where quality checks occur within the data pipeline.

Can I use this for FFIEC data governance compliance audits?

Yes, this Skill supports FFIEC data governance expectations by documenting data traceability and lineage across financial institutions. It traces data from source to consumption, identifying transformations and mapping quality controls for regulatory audit preparation.

What's the best way to generate a data lineage report for risk metrics?

Generating data lineage reports for risk metrics requires mapping data sources, transformations, and quality controls. This Skill documents the complete data journey from source to consumption, producing comprehensive lineage reports aligned with regulatory requirements.

Why does data lineage matter for regulatory compliance in financial institutions?

Data lineage matters for regulatory compliance because it demonstrates data integrity and traceability across financial systems. It documents how data flows from sources through transformations to consumption, ensuring adherence to BCBS 239 and FFIEC governance guidelines.