source-mapping

Declare source systems, author source.md files, and define field-level transformations.

1|Updated Feb 7, 2026
One-click install
npx skills add https://github.com/Semprini/md-ddl --skill source-mapping
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: source-mapping
Source: https://github.com/Semprini/md-ddl/tree/main/agents/agent-ontology/skills/source-mapping
Command: npx skills add https://github.com/Semprini/md-ddl --skill source-mapping

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill streamlines the process of connecting disparate source systems to a unified canonical data model, ensuring data consistency and enabling reliable data product generation.

Core Features & Use Cases

  • Source System Declaration: Define and document source systems, their capabilities, and how they signal changes.
  • Field-Level Transformation: Author detailed mappings from source fields to canonical attributes, including complex transformations.
  • Use Case: When integrating a new CRM system, use this Skill to map its customer fields (like cust_id, first_nm) to your canonical Customer.customerId and Customer.firstName attributes, defining any necessary transformations.

Quick Start

Use the source-mapping skill to declare the 'Salesforce CRM' system and map its 'Account' table to the 'Organization' entity.

Frequently Asked Questions about source-mapping

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

FAQPage Schema
How do I map source data fields to a canonical data model?

To map source data to a canonical model, you author source.md files to declare source systems and define field-level transformations that connect operational system feeds to unified domain entities. This ensures data consistency across disparate sources.

What is field-level transformation in ETL data mapping?

Field-level transformation in ETL data mapping is the process of defining detailed rules to convert source fields, like cust_id, into canonical attributes, like Customer.customerId. It connects operational systems to domain models for reliable data product generation.

How do I document source systems and data lineage for ETL processes?

You document source systems and data lineage by declaring source systems, their capabilities, and change signals. This creates domain feed tables and source.md files that answer data lineage questions and map feeds to canonical entities.

Can I map complex CRM data structures to a unified domain model?

Yes, you can map complex CRM data structures to a unified domain model. The process supports defining detailed field-level transformations, allowing you to map source tables like an Account table directly to a canonical Organization entity.

What's the best way to integrate a new operational system into a canonical model?

The best way to integrate a new operational system is to declare the system, author source.md files to document its capabilities, create domain feed tables, and define field-level transformations to map its fields to canonical entities.

When do I need to create domain feed tables for source data?

You need to create domain feed tables when connecting disparate operational source systems to a unified canonical data model. They serve as the structured intermediary for defining field-level transformations and generating reliable data products.