setting-up-astro-project

Initialize and configure Astro/Airflow projects using the Astro CLI.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Initialize and configure Astro/Airflow projects to standardize setup and reduce boilerplate across teams.

Core Features & Use Cases

  • Initialize a new Astro/Airflow project structure with dags/ include/ plugins/ tests/ Dockerfile, packages.txt, requirements.txt, and airflow_settings.yaml.
  • Configure connections, variables, and pools via airflow_settings.yaml and prepare environments for local development or containerized deployments.
  • Use Case: Starting a new project for a data pipeline or Airflow deployment, then iteratively updating dependencies and settings as the project evolves.

Quick Start

Run astro dev init to create the project skeleton, then edit airflow_settings.yaml to configure connections and variables. Install dependencies by updating requirements.txt and restart the environment with astro dev restart as needed.

Frequently Asked Questions about setting-up-astro-project

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

FAQPage Schema
How do I initialize an Astro project with the correct Airflow directory structure?

To initialize an Astro project, run astro dev init to generate the standard Airflow directory skeleton, including dags/, include/, plugins/, tests/, and configuration files like Dockerfile and requirements.txt.

How do I configure Airflow connections and variables for local development?

You configure Airflow connections and variables by editing the airflow_settings.yaml file, which prepares your environment for local development or containerized deployments.

What is the best way to manage Python dependencies in an Airflow project?

Managing Python dependencies in an Airflow project involves updating the requirements.txt file, while system-level packages go into packages.txt, followed by restarting the environment with astro dev restart.

Does this project setup support containerized Airflow deployments?

Yes, the project setup supports containerized Airflow deployments by generating a Dockerfile and providing guided setup and validation steps for local or containerized environments.

Why does my Airflow environment need a restart after updating dependencies?

Your Airflow environment needs a restart after updating dependencies to apply the new packages defined in requirements.txt, which is done using the astro dev restart command.