
astronomer-data
★ 397Claude Code plugin · astronomer/agents · Apache-2.0
Data engineering plugin - warehouse exploration, pipeline authoring, Airflow integration
27 skills — installs as one unit
⌁ skills (24)
airflow
🔥🔥🔥🔥✓ VerifiedQuery, manage, and troubleshoot Apache Airflow DAGs, runs, tasks, and system configuration. Supports 30+ commands across DAG inspection, run management, task logging, configuration queries, and direct REST API access Manage multiple Airflow instances with persistent configuration; auto-discover local and Astro deployments Trigger DAG runs synchronously (wait for completion) or asynchronously, diagnose failures, clear runs for retry, and access task logs with retry/map-index filtering Output...
Full instructions & audit →airflow-hitl
🔥🔥🔥✓ VerifiedHuman approval gates, form inputs, and branching in Airflow DAGs using deferrable operators. Four operator types: ApprovalOperator for approve/reject decisions, HITLOperator for multi-option selection with forms, HITLBranchOperator for human-driven task routing, and HITLEntryOperator for form data collection All operators are deferrable, releasing worker slots while awaiting human response via Airflow UI's Required Actions tab or REST API Supports optional features including custom...
Full instructions & audit →airflow-plugins
🔥🔥🔥✓ VerifiedBuild Airflow 3.1+ plugins that embed FastAPI apps, custom UI pages, React components, middleware, macros, and operator links directly into the Airflow UI. Use…
Full instructions & audit →analyzing-data
🔥🔥🔥✓ VerifiedQuery your data warehouse to answer business questions with cached patterns and concept mappings. Supports pattern lookup and caching for repeated question types, with outcome recording to improve future queries Includes concept-to-table mapping cache and table schema discovery via INFORMATION_SCHEMA or codebase grep Provides run_sql() and run_sql_pandas() kernel functions returning Polars or Pandas DataFrames for analysis CLI commands for managing concept, pattern, and table caches, plus...
Full instructions & audit →annotating-task-lineage
🔥🔥🔥✓ VerifiedAnnotate Airflow tasks with data lineage using inlets and outlets. Supports OpenLineage Dataset objects, Airflow Assets, and Airflow Datasets for defining inputs and outputs across databases, data warehouses, and cloud storage Use as a fallback when operators lack built-in OpenLineage extractors; follows a four-tier precedence system where custom extractors and OpenLineage methods take priority Includes dataset naming helpers for Snowflake, BigQuery, S3, and PostgreSQL to ensure consistent...
Full instructions & audit →blueprint
🔥🔥🔥✓ VerifiedDefine reusable Airflow task group templates with Pydantic validation and compose DAGs from YAML. Use when creating blueprint templates, composing DAGs from…
Full instructions & audit →checking-freshness
🔥🔥🔥✓ VerifiedVerify data freshness by checking table timestamps and update patterns against a staleness scale. Identifies timestamp columns using common ETL naming patterns ( _loaded_at , _updated_at , created_at , etc.) and queries their maximum values to determine age Classifies data into four freshness statuses: Fresh (< 4 hours), Stale (4–24 hours), Very Stale (> 24 hours), or Unknown (no timestamp found) Provides SQL templates for checking last update time and row count trends over recent days to...
Full instructions & audit →cosmos-dbt-core
🔥🔥🔥✓ VerifiedConvert dbt Core projects into Airflow DAGs or TaskGroups using Astronomer Cosmos. Supports three assembly patterns: standalone DbtDag, DbtTaskGroup within existing DAGs, and individual Cosmos operators for fine-grained control Choose from eight execution modes (WATCHER, LOCAL, VIRTUALENV, KUBERNETES, AIRFLOW_ASYNC, and others) based on isolation and performance needs Offers three parsing strategies (dbt_manifest, dbt_ls, dbt_ls_file, automatic) to balance speed and selector complexity...
Full instructions & audit →cosmos-dbt-fusion
🔥🔥🔥✓ VerifiedConfigure Astronomer Cosmos for dbt Fusion projects on Snowflake, Databricks, BigQuery, or Redshift with local execution. Requires Cosmos 1.11.0+, dbt Fusion binary installed separately in the Airflow runtime, and ExecutionMode.LOCAL with subprocess invocation Supports three parsing strategies: dbt_manifest (fastest for large projects), dbt_ls (for complex selectors), or automatic (simple setups) Covers ProfileConfig setup for warehouse connections, ProjectConfig for dbt project paths, and...
Full instructions & audit →creating-openlineage-extractors
🔥🔥🔥✓ VerifiedCustom OpenLineage extractors for unsupported Airflow operators and complex lineage scenarios. Two approaches: add OpenLineage methods directly to operators you own (recommended), or create custom extractors for third-party operators you cannot modify Extractors intercept operator execution at three points: before execution for static lineage, after success for runtime-determined outputs, and optionally after failure for partial lineage Register extractors via airflow.cfg or environment...
Full instructions & audit →dag-factory
🔥🔥🔥✓ VerifiedAuthor Apache Airflow DAGs declaratively with dag-factory YAML configs. Use when creating dag-factory templates, composing DAGs from YAML for dag-factory,…
Full instructions & audit →debugging-dags
🔥🔥🔥🔥✓ VerifiedSystematic root cause analysis and remediation for failed Airflow DAGs with structured investigation workflows. Guides through four-step diagnosis process: identify the failure, extract error details, gather contextual information, and deliver actionable remediation steps Categorizes failures into four types (data, code, infrastructure, dependency) to focus investigation and suggest appropriate fixes Provides ready-to-use CLI commands for log retrieval, run comparison, task clearing, and DAG...
Full instructions & audit →delegating-to-otto
🔥🔥🔥✓ VerifiedDrives Astronomer's Otto agent (`astro otto`) as a delegated sub-agent for Airflow, dbt, and data-engineering work. Use when the user explicitly asks to "use…
Full instructions & audit →deploying-airflow
🔥🔥🔥✓ VerifiedDeploy Airflow DAGs and projects. Use when the user wants to deploy code, push DAGs, set up CI/CD, deploy to production, or asks about deployment strategies…
Full instructions & audit →managing-astro-local-env
🔥🔥🔥✓ VerifiedManage local Airflow development environment with Astro CLI commands. Start, stop, restart, and kill local Airflow containers; default credentials are admin/admin with webserver at http://localhost:8080 View logs for all components or specific services (scheduler, webserver) with real-time follow option Access container shells and run Airflow CLI commands directly via astro dev bash and astro dev run Troubleshoot common issues including port conflicts, startup failures, package errors, and...
Full instructions & audit →migrating-ai-sdk-to-common-ai
🔥🔥✓ VerifiedMigrates Airflow projects from airflow-ai-sdk to apache-airflow-providers-common-ai 0.1.0+. Use this skill when the user wants to replace airflow-ai-sdk with…
Full instructions & audit →migrating-airflow-2-to-3
🔥🔥🔥🔥✓ VerifiedAutomated detection and code migration for upgrading Apache Airflow 2.x DAGs to Airflow 3.x. Provides Ruff-based auto-fix rules (AIR30/AIR301/AIR302/AIR31/AIR311/AIR312) to detect and resolve breaking changes in imports, operators, hooks, and context variables Covers critical architecture shifts: workers no longer access metadata DB directly; use the Airflow Python client or REST API instead of ORM session queries Includes manual migration checklist for issues Ruff cannot auto-fix: cron...
Full instructions & audit →profiling-tables
🔥🔥🔥✓ VerifiedComprehensive statistical and quality analysis of database tables with structured profiling output. Generates column-level statistics tailored to data type: min/max/percentiles for numeric columns, length metrics for strings, date ranges for timestamps Performs cardinality analysis to identify categorical vs. high-cardinality columns and detect skewed distributions Assesses data quality across five dimensions: completeness (NULL rates), uniqueness (duplicates), freshness (update timestamps),...
Full instructions & audit →setting-up-astro-project
🔥🔥🔥✓ VerifiedInitialize and configure Astro/Airflow projects with dependencies, connections, and environment setup. Scaffolds complete project structure with astro dev init , including directories for DAGs, plugins, tests, and configuration files Manage Python and OS-level dependencies via requirements.txt and packages.txt , with custom Dockerfile support for complex setups Configure connections, variables, and pools declaratively in airflow_settings.yaml , with export/import commands for environment...
Full instructions & audit →testing-dags
🔥🔥🔥✓ VerifiedIterative test-debug-fix cycles for Airflow DAGs with comprehensive failure diagnosis. Start with af runs trigger-wait <dag_id> to run a DAG and wait for completion; no pre-flight checks needed On failure, use af runs diagnose for comprehensive failure summary and af tasks logs to inspect error details from specific tasks Supports custom configuration, timeouts, and retry attempts; handles success, failure, and timeout scenarios with clear response interpretation Quick validation available...
Full instructions & audit →tracing-downstream-lineage
🔥🔥🔥✓ VerifiedTrace downstream data lineage to assess change impact before modifying tables or DAGs. Identifies direct consumers of a target table or DAG through source code search, view dependencies, and BI tool connections Builds a full dependency tree mapping all downstream impacts, from tables to dashboards to ML models Categorizes dependencies by criticality (critical, high, medium, low) to prioritize stakeholder communication and testing Generates an impact report with risk assessment, affected...
Full instructions & audit →tracing-upstream-lineage
🔥🔥🔥✓ VerifiedTrace upstream data lineage to identify sources, DAGs, and dependencies feeding a table or column. Supports tracing three target types: tables, columns, and DAGs; uses Airflow DAG source code and task inspection to find producing pipelines Handles SQL sources (FROM clauses), external systems (S3, Postgres, Salesforce, HTTP APIs), and file-based sources; recursively traces upstream chains Includes column-level tracing through direct mappings, transformations, and aggregations in DAG code...
Full instructions & audit →warehouse-init
🔥🔥✓ VerifiedInitialize warehouse schema discovery. Generates .astro/warehouse.md with all table metadata for instant lookups. Run once per project, refresh when schema…
Full instructions & audit →agents
AI agent tooling for data engineering workflows. Includes an MCP server for Airflow, a CLI tool (af) for interacting with Airflow from your terminal, and skills that extend AI coding agents with specialized capabilities for working with Airflow and data warehouses. Works with Claude Code, Cursor, and other agentic coding tools.
Built by Astronomer. Apache 2.0 licensed and compatible with open-source Apache Airflow.
Table of Contents
<!-- START doctoc generated TOC please keep comment here to allow auto update --> <!-- DON'T EDIT THIS SECTION, INSTEAD RE-RUN doctoc TO UPDATE -->- Installation
- Features
- Why Astro?
- Configuration
- Usage
- Development
- Troubleshooting
- Contributing
- Roadmap
- License
Features
The astronomer-data plugin bundles an MCP server and skills into a single installable package.
MCP Server
| Server | Description |
|---|---|
| Airflow | Full Airflow REST API integration via astro-airflow-mcp: DAG management, triggering, task logs, system health |
Skills
Data Discovery & Analysis
| Skill | Description |
|---|---|
| warehouse-init | Initialize schema discovery - generates .astro/warehouse.md for instant lookups |
| analyzing-data | SQL-based analysis to answer business questions (uses background Jupyter kernel) |
| checking-freshness | Check how current your data is |
| profiling-tables | Comprehensive table profiling and quality assessment |
Data Lineage
| Skill | Description |
|---|---|
| tracing-downstream-lineage | Analyze what breaks if you change something |
| tracing-upstream-lineage | Trace where data comes from |
| annotating-task-lineage | Add manual lineage to tasks using inlets/outlets |
| creating-openlineage-extractors | Build custom OpenLineage extractors for operators |
DAG Development
| Skill | Description |
|---|---|
| airflow | Main entrypoint - routes to specialized Airflow skills |
| setting-up-astro-project (Astro) | Initialize and configure new Astro/Airflow projects |
| managing-astro-local-env (Astro) | Manage local Airflow environment (start, stop, logs, troubleshoot) |
| authoring-dags | Create and validate Airflow DAGs with best practices |
| blueprint | Compose DAGs from YAML using reusable templates with Pydantic validation (airflow-blueprint) |
| testing-dags | Test and debug Airflow DAGs locally |
| debugging-dags | Deep failure diagnosis and root cause analysis |
| deploying-airflow | Deploy Airflow DAGs and projects (Astro, Docker Compose, Kubernetes) |
| airflow-hitl | Human-in-the-loop workflows: approval gates, form input, branching (Airflow 3.1+) |
dbt Integration
| Skill | Description |
|---|---|
| cosmos-dbt-core | Run dbt Core projects as Airflow DAGs using Astronomer Cosmos |
| cosmos-dbt-fusion | Run dbt Fusion projects with Cosmos (Snowflake/Databricks only) |
Migration
| Skill | Description |
|---|---|
| migrating-airflow-2-to-3 | Migrate DAGs from Airflow 2.x to 3.x |
Why Astro?
Astro is Astronomer's managed Airflow platform. It's optional, but a good fit if you want managed deployments, built-in alerting, and centralized observability across environments. If you run open-source Airflow, everything in this repo still applies—you'll just configure your own Airflow URL and infrastructure.
User Journeys
Data Analysis Flow
flowchart LR
init["/astronomer-data:warehouse-init"] --> analyzing["/astronomer-data:analyzing-data"]
analyzing --> profiling["/astronomer-data:profiling-tables"]
analyzing --> freshness["/astronomer-data:checking-freshness"]- Initialize (
/astronomer-data:warehouse-init) - One-time setup to generatewarehouse.mdwith schema metadata - Analyze (
/astronomer-data:analyzing-data) - Answer business questions with SQL - Profile (
/astronomer-data:profiling-tables) - Deep dive into specific tables for statistics and quality - Check freshness (
/astronomer-data:checking-freshness) - Verify data is up to date before using
DAG Development Flow
For open-source Airflow, use Docker Compose for local dev and the Helm chart for production (see deploying-airflow) instead of Astro setup skills.
flowchart LR
setup["/astronomer-data:setting-up-astro-project"] --> authoring["/astronomer-data:authoring-dags"]
setup --> env["/astronomer-data:managing-astro-local-env"]
authoring --> testing["/astronomer-data:testing-dags"]
testing --> debugging["/astronomer-data:debugging-dags"]- Setup (
/astronomer-data:setting-up-astro-project) - Initialize project structure and dependencies - Environment (
/astronomer-data:managing-astro-local-env) - Start/stop local Airflow for development - Author (
/astronomer-data:authoring-dags) - Write DAG code following best practices - Test (
/astronomer-data:testing-dags) - Run DAGs and fix issues iteratively - Debug (
/astronomer-data:debugging-dags) - Deep investigation for complex failures
Airflow CLI (af)
The af command-line tool lets you interact with Airflow directly from your terminal. Install it with:
uvx --from astro-airflow-mcp af --helpFor frequent use, add an alias to your shell config (~/.bashrc or ~/.zshrc):
alias af='uvx --from astro-airflow-mcp af'Then use it for quick operations like af health, af dags list, or af runs trigger <dag_id>.
See the full CLI documentation for all commands and instance management.
Telemetry: The
afCLI collects anonymous usage telemetry to help improve the tool. Only the command name is collected (e.g.,dags list), never the arguments or their values. Opt out withaf telemetry disable.
Development
See CLAUDE.md for plugin development guidelines.
Local Development Setup
# Clone the repo
git clone https://github.com/astronomer/agents.git
cd agents
# Test with local plugin
claude --plugin-dir .
# Or install from local marketplace
claude plugin marketplace add .
claude plugin install astronomer-data@astronomerAdding Skills
Create a new skill in skills/<name>/SKILL.md with YAML frontmatter:
---
name: my-skill
description: When to invoke this skill
---
# Skill instructions here...After adding skills, reinstall the plugin:
claude plugin uninstall astronomer-data@astronomer && claude plugin marketplace update && claude plugin install astronomer-data@astronomerRoadmap
Skills we're likely to build:
DAG Operations
- CI/CD pipelines for DAG deployment
- Performance optimization and tuning
- Monitoring and alerting setup
- Data quality and validation workflows
Astronomer Open Source
- DAG Factory - Generate DAGs from YAML
- Other open source projects we maintain
Conference Learnings
- Reviewing talks from Airflow Summit, Coalesce, Data Council, and other conferences to extract reusable skills and patterns
Broader Data Practitioner Skills
- Churn prediction, data modeling, ML training, and other workflows that span DE/DS/analytics roles
Don't see a skill you want? Open an issue or submit a PR!
Troubleshooting
Common Issues
| Issue | Solution |
|---|---|
| Skills not appearing | Reinstall plugin: claude plugin uninstall astronomer-data@astronomer && claude plugin marketplace update && claude plugin install astronomer-data@astronomer |
Installed as data@astronomer (old name) | Uninstall old name and reinstall: claude plugin uninstall data@astronomer && claude plugin marketplace update && claude plugin install astronomer-data@astronomer |
| Warehouse connection errors | Check credentials in ~/.astro/agents/.env and connection config in warehouse.yml |
| Airflow not detected | Ensure you're running from a directory with airflow.cfg or a dags/ folder |
Installation
Quick Start
npx skills add astronomer/agents --skill '*'This installs all Astronomer skills into your project via skills.sh. You'll be prompted to select which agents to install to. To also select skills individually, omit the --skill flag.
[!IMPORTANT] Claude Code users: We recommend using the plugin instead (see Claude Code section below) for better integration with MCP servers and hooks.
Compatibility
Skills: Works with 25+ AI coding agents including Claude Code, Cursor, VS Code (GitHub Copilot), Windsurf, Cline, and more.
MCP Server: Works with any MCP-compatible client including Claude Desktop, VS Code, and others.
[!NOTE] Open-source Airflow users: The MCP server works with any Airflow 2.x/3.x REST API. Set
AIRFLOW_API_URLto your self-hosted instance. Skills are tool-agnostic and work with any Airflow deployment.
Claude Code
# Add the marketplace and install the plugin
claude plugin marketplace add astronomer/agents
claude plugin install astronomer-data@astronomer
# Upgrading from the old plugin name? Uninstall first:
# claude plugin uninstall data@astronomer && claude plugin marketplace update && claude plugin install astronomer-data@astronomerThe plugin includes the Airflow MCP server that runs via uvx from PyPI. Data warehouse queries are handled by the analyzing-data skill using a background Jupyter kernel.
Cursor
Cursor supports both MCP servers and skills.
MCP Server - Click to install:
<a href="https://cursor.com/en-US/install-mcp?name=astro-airflow-mcp&config=eyJjb21tYW5kIjoidXZ4IiwiYXJncyI6WyJhc3Ryby1haXJmbG93LW1jcCIsIi0tdHJhbnNwb3J0Iiwic3RkaW8iXX0"><img src="https://cursor.com/deeplink/mcp-install-dark.svg" alt="Add Airflow MCP to Cursor" height="32"></a>
Skills - Install to your project:
npx skills add astronomer/agents --skill '*' -a cursorThis installs skills to .cursor/skills/ in your project.
Add to ~/.cursor/mcp.json:
{
"mcpServers": {
"airflow": {
"command": "uvx",
"args": ["astro-airflow-mcp", "--transport", "stdio"]
}
}
}Create .cursor/hooks.json in your project:
{
"version": 1,
"hooks": {
"stop": [
{
"command": "uv run $CURSOR_PROJECT_DIR/.cursor/skills/analyzing-data/scripts/cli.py stop",
"timeout": 10
}
]
}
}What these hooks do:
stop: Cleans up kernel when session ends
Other MCP Clients
For any MCP-compatible client (Claude Desktop, VS Code, etc.):
# Airflow MCP
uvx astro-airflow-mcp --transport stdio
# With remote Airflow
AIRFLOW_API_URL=https://your-airflow.example.com \
AIRFLOW_USERNAME=admin \
AIRFLOW_PASSWORD=admin \
uvx astro-airflow-mcp --transport stdioConfiguration
Warehouse Connections
Configure data warehouse connections at ~/.astro/agents/warehouse.yml:
my_warehouse:
type: snowflake
account: ${SNOWFLAKE_ACCOUNT}
user: ${SNOWFLAKE_USER}
auth_type: private_key
private_key_path: ~/.ssh/snowflake_key.p8
private_key_passphrase: ${SNOWFLAKE_PRIVATE_KEY_PASSPHRASE}
warehouse: COMPUTE_WH
role: ANALYST
query_tag: claude-code
databases:
- ANALYTICS
- RAW[!IMPORTANT] How the
databaseslist works:
- Optional for most connectors (
snowflake,postgres,bigquery) but required forsqlalchemy- For schema discovery (
/astronomer-data:warehouse-init): Determines which databases are scanned and included in the generated.astro/warehouse.md. Only databases listed here will be discovered. If omitted, no schema discovery will occur.- For query execution (
/astronomer-data:analyzing-data): The first database in the list becomes the default database context for the connection, but does NOT restrict which databases you can query. You can still access any database you have permissions for using fully-qualified table names (e.g.,OTHER_DB.SCHEMA.TABLE).Example: If you configure
databases: [ANALYTICS, RAW]:
ANALYTICSbecomes the default database for queries- You can still query
PRODwithSELECT * FROM PROD.PUBLIC.USERS- Only
ANALYTICSandRAWwill appear in warehouse schema documentation (run/astronomer-data:warehouse-init --refreshafter addingPRODto include it)
[!NOTE] The
accountfield requires your Snowflake account identifier (e.g.,orgname-accountnameorxy12345.us-east-1), not your account name. Find this in your Snowflake console under Admin > Accounts.
Store credentials in ~/.astro/agents/.env:
SNOWFLAKE_ACCOUNT=myorg-myaccount # Use your Snowflake account identifier (format: orgname-accountname or accountname.region)
SNOWFLAKE_USER=myuser
SNOWFLAKE_PRIVATE_KEY_PASSPHRASE=your-passphrase-here # Only required if using an encrypted private keySupported databases:
| Type | Package | Description |
|---|---|---|
snowflake | Built-in | Snowflake Data Cloud |
postgres | Built-in | PostgreSQL |
bigquery | Built-in | Google BigQuery |
sqlalchemy | Any SQLAlchemy driver | Auto-detects packages for 25+ databases (see below) |
The connector automatically installs the correct driver packages for:
| Database | Dialect URL |
|---|---|
| PostgreSQL | postgresql:// or postgres:// |
| MySQL | mysql:// or mysql+pymysql:// |
| MariaDB | mariadb:// |
| SQLite | sqlite:/// |
| SQL Server | mssql+pyodbc:// |
| Oracle | oracle:// |
| Redshift | redshift:// |
| Snowflake | snowflake:// |
| BigQuery | bigquery:// |
| DuckDB | duckdb:/// |
| Trino | trino:// |
| ClickHouse | clickhouse:// |
| CockroachDB | cockroachdb:// |
| Databricks | databricks:// |
| Amazon Athena | awsathena:// |
| Cloud Spanner | spanner:// |
| Teradata | teradata:// |
| Vertica | vertica:// |
| SAP HANA | hana:// |
| IBM Db2 | db2:// |
For unlisted databases, install the driver manually and use standard SQLAlchemy URLs.
</details> <details> <summary>Example configurations</summary># PostgreSQL
my_postgres:
type: postgres
host: localhost
port: 5432
user: analyst
password: ${POSTGRES_PASSWORD}
database: analytics
application_name: claude-code
# BigQuery
my_bigquery:
type: bigquery
project: my-gcp-project
credentials_path: ~/.config/gcloud/service_account.json
location: US
labels:
team: data-eng
env: prod
# SQLAlchemy (any supported database)
my_duckdb:
type: sqlalchemy
url: duckdb:///path/to/analytics.duckdb
databases: [main]
# SQLAlchemy with connect_args (passed to the DBAPI driver)
my_pg_sqlalchemy:
type: sqlalchemy
url: postgresql://${PG_USER}:${PG_PASSWORD}@localhost/analytics
databases: [analytics]
connect_args:
application_name: claude-code
# Redshift (via SQLAlchemy)
my_redshift:
type: sqlalchemy
url: redshift+redshift_connector://${REDSHIFT_USER}:${REDSHIFT_PASSWORD}@${REDSHIFT_HOST}:5439/${REDSHIFT_DATABASE}
databases: [my_database]Airflow
The Airflow MCP auto-discovers your project when you run Claude Code from an Airflow project directory (contains airflow.cfg or dags/ folder).
For remote instances, set environment variables:
| Variable | Description |
|---|---|
AIRFLOW_API_URL | Airflow webserver URL |
AIRFLOW_USERNAME | Username |
AIRFLOW_PASSWORD | Password |
AIRFLOW_AUTH_TOKEN | Bearer token (alternative to username/password) |
Usage
Skills are invoked automatically based on what you ask. You can also invoke them directly with /astronomer-data:<skill-name>.
Getting Started
-
Initialize your warehouse (recommended first step):
/astronomer-data:warehouse-initThis generates
.astro/warehouse.mdwith schema metadata for faster queries. -
Ask questions naturally:
- "What tables contain customer data?"
- "Show me revenue trends by product"
- "Create a DAG that loads data from S3 to Snowflake daily"
- "Why did my etl_pipeline DAG fail yesterday?"
One install gets you everything — 27 skills — kept up to date together.
Licensed under Apache-2.0— you can use, modify, and redistribute it under that license's terms.
License
Apache 2.0
Made with :heart: by Astronomer <img referrerpolicy="no-referrer-when-downgrade" src="https://static.scarf.sh/a.png?x-pxid=f1c1d270-334e-45ec-b711-77385036cff9" />