concept-explorer

Explain MD-DDL concepts, features, and design decisions through analogies and comparisons.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill helps users understand complex concepts within the Markdown Data Definition Language (MD-DDL) by providing clear explanations, analogies, and practical examples.

Core Features & Use Cases

  • Concept Explanation: Breaks down MD-DDL terms like entities, relationships, and data products.
  • Comparative Analysis: Compares MD-DDL to other tools and methodologies (e.g., ER diagrams, dbt, Data Mesh).
  • Validation Clarification: Explains MD-DDL's two-tier validation model and why it differs from traditional linters.
  • Use Case: A new user asks, "What is an MD-DDL entity and how is it different from a dbt model?" This Skill will provide a clear definition, an analogy, and highlight the key distinctions.

Quick Start

Explain the MD-DDL concept of a 'Data Product' to me.

Frequently Asked Questions about concept-explorer

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

FAQPage Schema
What is an MD-DDL entity and how does it differ from a dbt model?

An MD-DDL entity represents a core data structure conceptually, whereas a dbt model focuses on SQL-based transformations. This approach uses analogies and structured definitions to highlight key distinctions in data modeling methodologies.

How does MD-DDL validation work compared to traditional linters?

MD-DDL validation uses a two-tier validation system designed specifically for its data definition structure, unlike traditional linters that enforce generic syntax rules. This model clarifies design decisions and ensures lifecycle management compliance.

How do MD-DDL concepts compare to ER diagrams and Data Mesh?

MD-DDL concepts provide structured definitions for data products and relationships, whereas ER diagrams visualize relational schemas and Data Mesh focuses on organizational data ownership. Comparative analysis clarifies these distinct methodologies.

Can you explain the MD-DDL concept of a Data Product?

A Data Product in MD-DDL is an identifiable, structured output managed through the definition language. It is explained through practical examples and analogies to clarify its role within data lifecycle management.

Does MD-DDL integrate with FHIR or other external data modeling tools?

MD-DDL can be compared to external tools like FHIR to clarify its unique design decisions. It uses comparative analysis to explain how its conceptual framework differs from external healthcare data standards.