update-from

Imports external schema and metadata into the vault with query-verified context files.

21|1|Updated Mar 30, 2026
One-click install
npx skills add https://github.com/ryanjanssen/metalayer --skill update-from-ryanjanssen
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: update-from
Source: https://github.com/ryanjanssen/metalayer/tree/main/skills/update-from
Command: npx skills add https://github.com/ryanjanssen/metalayer --skill update-from-ryanjanssen

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Bringing an existing data model from tools like dbt, LookML, or Snowflake into a markdown-based semantic layer is error-prone when source metadata is trusted blindly. This Skill imports external schemas into the vault while verifying every claim against real warehouse data before writing anything. ## Core Features & Use Cases - Preset-driven imports: Loads source-specific import presets from utils/imports/{source}.md that define how to connect, what to extract, and how to map source concepts to vault types. - Query-verified drafting: Runs verification queries against the actual warehouse to confirm grain, primary key uniqueness, column contents, join cardinality, and metric expressions before drafting any file. - Conflict-safe merging: Compares source metadata against existing vault files and surfaces disagreements on SQL, cardinality, aggregation, and descriptions for explicit user decision instead of silent overwrites. - Use Case: A team adopting dbt wants their models reflected in the Metalayer vault. The agent loads the dbt preset, extracts models and relationships, verifies each against Snowflake, drafts view, field, relation, and lore files, and presents them for approval before writing. ## Quick Start Tell the agent to update from your source, for example: update from dbt and import my models into the vault.

Frequently Asked Questions about update-from

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

FAQPage Schema
How do I import a dbt data model into a markdown semantic layer?▼

Run the update-from workflow with the dbt preset, which extracts models, columns, joins, and tests, maps them to vault views, fields, and relations, and verifies everything against the warehouse before drafting files for your approval.

How to migrate LookML or Snowflake metadata into an Obsidian-style vault?▼

Load the matching import preset from utils/imports, which defines connection details, extraction targets, and mapping rules. The agent then drafts wikilinked markdown files per entity and presents them in dependency order for review.

Does the import verify metadata against the actual warehouse?▼

Yes, verification is mandatory. The workflow runs queries to confirm grain, primary key uniqueness, column contents, join cardinality, and metric expressions, and refuses to write context files without warehouse access unless you explicitly approve unverified output marked with # UNVERIFIED.

What happens when source metadata conflicts with existing vault files?▼

Conflicts are never silently overwritten. Differences in SQL, cardinality, aggregation, or descriptions are shown side by side with evidence, and the vault version is preserved by default until you choose a resolution.

Can the import create concepts and topics automatically?▼

No. Concepts and topics require human understanding of the business domain, so the workflow only flags candidates. It generates views, fields, relations, and multi-object lore, skipping boilerplate columns and obvious rules.