How do I install the Managing Astro Local Env skill?

Run npx skillmds@latest add diegosouzapw/managing-astro-local-env in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Managing Astro Local Env safe to use?

This skill has not completed SkillMD's automated safety review yet. Independent scanners report: SkillSpector: PASS, Skill Scanner: PASS. Capability flags: makes network calls. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Managing Astro Local Env?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Managing Astro Local Env free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Managing Astro Local Env?

diegosouzapw (@diegosouzapw) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Managing Astro Local Env by diegosouzapw

Name: Managing Astro Local Env
Rating: 4.666666666666667 (3 reviews)
Author: diegosouzapw

Managing Astro Local Env

Manage local Airflow environment with Astro CLI. Use when the user wants to start, stop, or restart Airflow, view logs, troubleshoot containers, or fix environment issues. For project setup, see setting-up-astro-project.

diegosouzapw Updated Sep 8, 2026 54 repo stars

File contents

Astro Local Environment

This skill helps you manage your local Airflow environment using the Astro CLI.

To set up a new project, see the setting-up-astro-project skill. When Airflow is running, use MCP tools from authoring-dags and testing-dags skills.

Start / Stop / Restart

# Start local Airflow (webserver at http://localhost:8080)
astro dev start

# Stop containers (preserves data)
astro dev stop

# Kill and remove volumes (clean slate)
astro dev kill

# Restart all containers
astro dev restart

# Restart specific component
astro dev restart --scheduler
astro dev restart --webserver

Default credentials: admin / admin

Restart after modifying: requirements.txt, packages.txt, Dockerfile

Check Status

astro dev ps

View Logs

# All logs
astro dev logs

# Specific component
astro dev logs --scheduler
astro dev logs --webserver

# Follow in real-time
astro dev logs -f

Access Container Shell

# Bash into scheduler container
astro dev bash

# Run Airflow CLI commands
astro dev run airflow info
astro dev run airflow dags list

Troubleshooting

Issue	Solution
Port 8080 in use	Stop other containers or edit `.astro/config.yaml`
Container won't start	`astro dev kill` then `astro dev start`
Package install failed	Check `requirements.txt` syntax
DAG not appearing	Run `astro dev parse` to check for import errors
Out of disk space	`docker system prune`

Reset Environment

When things are broken:

astro dev kill
astro dev start

Upgrade Airflow

Test compatibility first

astro dev upgrade-test

Change version

Edit Dockerfile:

FROM quay.io/astronomer/astro-runtime:13.0.0

Restart:
```
astro dev kill && astro dev start
```

Related Skills

setting-up-astro-project: Initialize projects and configure dependencies
authoring-dags: Write DAGs (uses MCP tools, requires running Airflow)
testing-dags: Test DAGs (uses MCP tools, requires running Airflow)
deploying-airflow: Deploy DAGs to production (Astro, Docker Compose, Kubernetes)

---name: managing-astro-local-envdescription: Manage local Airflow environment with Astro CLI. Use when the user wants to start, stop, or restart Airflow, view logs, troubleshoot containers, or fix environment issues. For project setup, see setting-up-astro-project.---# Astro Local EnvironmentThis skill helps you manage your local Airflow environment using the Astro CLI.> **To set up a new project**, see the **setting-up-astro-project** skill.> **When Airflow is running**, use MCP tools from **authoring-dags** and **testing-dags** skills.---## Start / Stop / Restart```bash# Start local Airflow (webserver at http://localhost:8080)astro dev start# Stop containers (preserves data)astro dev stop# Kill and remove volumes (clean slate)astro dev kill# Restart all containersastro dev restart# Restart specific componentastro dev restart --schedulerastro dev restart --webserver```**Default credentials:** admin / admin**Restart after modifying:** `requirements.txt`, `packages.txt`, `Dockerfile`---## Check Status```bashastro dev ps```---## View Logs```bash# All logsastro dev logs# Specific componentastro dev logs --schedulerastro dev logs --webserver# Follow in real-timeastro dev logs -f```---## Access Container Shell```bash# Bash into scheduler containerastro dev bash# Run Airflow CLI commandsastro dev run airflow infoastro dev run airflow dags list```---## Troubleshooting| Issue | Solution ||-------|----------|| Port 8080 in use | Stop other containers or edit `.astro/config.yaml` || Container won't start | `astro dev kill` then `astro dev start` || Package install failed | Check `requirements.txt` syntax || DAG not appearing | Run `astro dev parse` to check for import errors || Out of disk space | `docker system prune` |### Reset EnvironmentWhen things are broken:```bashastro dev killastro dev start```---## Upgrade Airflow### Test compatibility first```bashastro dev upgrade-test```### Change version1. Edit `Dockerfile`: ```dockerfile FROM quay.io/astronomer/astro-runtime:13.0.0 ```2. Restart: ```bash astro dev kill && astro dev start ```---## Related Skills- **setting-up-astro-project**: Initialize projects and configure dependencies- **authoring-dags**: Write DAGs (uses MCP tools, requires running Airflow)- **testing-dags**: Test DAGs (uses MCP tools, requires running Airflow)- **deploying-airflow**: Deploy DAGs to production (Astro, Docker Compose, Kubernetes)

Frequently asked questions