baseline-capture

Document existing data assets as MD-DDL baseline files.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This skill addresses the challenge of documenting existing data schemas, models, ETL pipelines, and catalog metadata for audit, historical record-keeping, or as a starting point for canonical modeling.

Core Features & Use Cases

  • Automated Baseline Generation: Creates MD-DDL baseline files from various raw inputs like DDL, dbt models, or natural language descriptions.
  • Flexible Input Handling: Accepts DDL, dbt artifacts, catalog exports, ERDs, or prose descriptions without requiring user reformatting.
  • Use Case: A data team needs to document the current state of their legacy data warehouse before migrating to a new system. They can feed DDL scripts and pipeline descriptions into this skill to generate comprehensive baseline documentation.

Quick Start

Use the baseline-capture skill to document the provided CREATE TABLE statements as a baseline.

Frequently Asked Questions about baseline-capture

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

FAQPage Schema
How do I document existing data assets from DDL scripts and dbt models?

To document existing data assets, you can feed raw DDL scripts, dbt models, or catalog exports into a baseline generator to automatically create structured MD-DDL baseline files with metadata headers for audit and historical record-keeping.

Can I use natural language descriptions to generate schema documentation for a legacy data warehouse?

Yes, you can use natural language prose descriptions to generate schema documentation. The baseline capture process accepts unformatted text descriptions and converts them into structured baseline files without requiring strict input formatting.

What is the best way to create a baseline of ETL pipelines and catalog metadata for a migration audit?

The best way to create a baseline for a migration audit is to process your ETL pipeline definitions and catalog exports through an automated baseline generator, which outputs structured MD-DDL files within a dedicated baselines folder.

Does baseline documentation work with raw catalog exports and ERDs without reformatting?

Yes, baseline documentation works directly with raw catalog exports and ERDs. The system accepts these various input formats natively, allowing you to generate comprehensive structured baseline files without needing to manually reformat the source materials.

How do I identify candidate entities for canonical modeling from existing data schemas?

You can identify candidate entities for canonical modeling by processing existing data schemas through a baseline capture tool, which analyzes the structured baseline files generated from your inputs and automatically flags suitable entities for canonical modeling.

When should I not use automated baseline files for documenting data assets?

You should not use automated baseline files when your goal is to create canonical entities directly, as this documentation process is strictly for audit, historical record-keeping, and generating raw inputs for downstream canonical modeling.