init

Generate a version-controlled .astro/warehouse.md with per-table metadata from warehouse system catalogs.

419|61|Updated Jan 13, 2026
One-click install
npx skills add https://github.com/astronomer/agents --skill init-astronomer
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: init
Source: https://github.com/astronomer/agents/tree/main/skills/init
Command: npx skills add https://github.com/astronomer/agents --skill init-astronomer

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

Initialize warehouse schema discovery to generate a centralized, editable reference for all warehouse tables, enabling instant lookups and governance. Run once per project, refresh when schema changes. Use when user says /data:init or asks to set up data discovery.

Core Features & Use Cases

  • Auto-generates .astro/warehouse.md containing table metadata for instant lookups.
  • Code-enriched metadata by aggregating descriptions from dbt models and declarative SQL.
  • Use Case: Set up per-project warehouse discovery and refresh with schema drift.

Quick Start

To initialize the warehouse discovery for your project, run the data init flow described in SKILL.md and follow the prompts in your environment.

Frequently Asked Questions about init

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

FAQPage Schema
How do I automate warehouse schema discovery and cataloging?

You can automate warehouse schema discovery by reading warehouse configuration, querying system catalogs, and generating a version-controlled .astro/warehouse.md file containing per-table metadata to support instant lookups.

What is the best way to document data warehouse metadata for instant lookups?

The best way to document warehouse metadata for instant lookups is generating a centralized, editable reference that aggregates descriptions from dbt models and declarative SQL into a cached quick-reference file.

How does warehouse schema discovery handle schema drift over time?

Warehouse schema discovery handles schema drift by running the initialization flow again when the schema changes, refreshing the generated .astro/warehouse.md file to reflect updated per-table metadata across multiple databases.

Can I integrate discovered warehouse metadata with my existing CLAUDE.md file?

Yes, discovered warehouse metadata integrates with CLAUDE.md through an optional configuration that appends the cataloged table metadata, ensuring your environment has immediate access to the centralized quick-reference lookups.

Do I need dbt models to use automated warehouse schema discovery?

You do not need dbt models to run warehouse schema discovery, but having them allows the process to code-enrich the generated metadata by aggregating descriptions from those dbt models and declarative SQL files.