How do I install the Managing Astro Local Env skill?

Run npx skillmds@latest add vanducng/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. 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. This skill is licensed under MIT.

Who published Managing Astro Local Env?

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

Managing Astro Local Env by vanducng

Name: Managing Astro Local Env
Author: vanducng

Managing Astro Local Env

Manage a local Astronomer/Airflow environment with Astro CLI. Use when the user says astro dev start/stop/restart, local scheduler, astro dev parse, astro dev pytest, local task logs, localhost Airflow UI, or Makefile wrappers like make airflow / make scheduler-restart. Not for staging/prod inspection (vd:astro-airflow) and not for YAML DAG authoring (vd:dag-factory).

vanducng Updated Sep 17, 2026

File contents

managing-astro-local-env

Local Airflow via Astro CLI. Docker mode is the default. Do not assume port 8080 - read the project config.

Port and credentials

astro config get          # webserver port, postgres port, mode
astro dev ps

Check .astro/config.yaml and airflow_settings.yaml for the UI port. Default credentials are admin / admin unless the project overrides them.

Lifecycle

astro dev start                 # UI on the configured port
astro dev stop                  # keep volumes
astro dev kill                  # wipe volumes
astro dev restart
astro dev restart --scheduler   # faster than full restart after DAG edits
astro dev parse                 # import errors without waiting for the scheduler
astro dev pytest
astro dev logs --scheduler
astro dev logs -f
astro dev bash
astro dev run airflow dags list

Restart after requirements.txt, packages.txt, or Dockerfile changes (kill then start if packages fail to install).

If the repo Makefile already wraps these, prefer the target that exists (airflow, scheduler-restart, dags-import-errors, dags-reparse). Do not invent Make targets.

Local API

Prefer a configured af instance named local (see vd:astro-airflow). Otherwise:

# Astro CLI (local only) - operation ids, not raw paths
astro api airflow ls
astro api airflow get_import_errors
astro api airflow get_dags -q '.dags[].dag_id'
astro api airflow get_dag_runs -p dag_id=<dag_id>

astro api airflow defaults to localhost + admin/admin. Override with --api-url / --username / --password when the project is not on 8080.

For remote staging/prod, stop using this skill and use vd:astro-airflow.

Parse loop (new or edited DAG)

astro dev parse
# or: make dags-import-errors

YAML/loader errors show up here, not as a failed task. After parse is clean, unpause before the first trigger.

Troubleshooting

Issue	Fix
Port in use	`astro config get`; stop the other stack or change the project port
DAG missing	`astro dev parse`; missing `from airflow import DAG` in the loader
Scheduler not picking up YAML	`astro dev restart --scheduler` or the repo's reparse target
Package install failed	requirements syntax; then `astro dev kill && astro dev start`
Disk full	`docker system prune`
`Variable.get` ImportError at parse	Airflow 3 parse isolation; wrap or use YAML `AIRFLOW_VARIABLE__` params

Standalone / proxy (only if the user asks)

astro dev start --standalone needs Airflow 3 + uv, no Docker. Pass --standalone on every follow-up command unless astro config set dev.mode standalone. Reverse proxy: astro dev proxy status (default 6563) for multiple local projects.

Remote Astro: vd:astro-airflow
YAML DAGs: vd:dag-factory
Otto: vd:delegating-to-otto
Upstream: https://github.com/astronomer/agents/blob/main/skills/managing-astro-local-env/SKILL.md

---name: managing-astro-local-envdescription: Manage a local Astronomer/Airflow environment with Astro CLI. Use when the user says astro dev start/stop/restart, local scheduler, astro dev parse, astro dev pytest, local task logs, localhost Airflow UI, or Makefile wrappers like make airflow / make scheduler-restart. Not for staging/prod inspection (vd:astro-airflow) and not for YAML DAG authoring (vd:dag-factory).license: MIT---# managing-astro-local-envLocal Airflow via Astro CLI. Docker mode is the default. Do not assume port 8080 - read the project config.## Port and credentials```bashastro config get # webserver port, postgres port, modeastro dev ps```Check `.astro/config.yaml` and `airflow_settings.yaml` for the UI port. Default credentials are `admin` / `admin` unless the project overrides them.## Lifecycle```bashastro dev start # UI on the configured portastro dev stop # keep volumesastro dev kill # wipe volumesastro dev restartastro dev restart --scheduler # faster than full restart after DAG editsastro dev parse # import errors without waiting for the schedulerastro dev pytestastro dev logs --schedulerastro dev logs -fastro dev bashastro dev run airflow dags list```Restart after `requirements.txt`, `packages.txt`, or `Dockerfile` changes (`kill` then `start` if packages fail to install).If the repo Makefile already wraps these, prefer the target that exists (`airflow`, `scheduler-restart`, `dags-import-errors`, `dags-reparse`). Do not invent Make targets.## Local APIPrefer a configured `af` instance named `local` (see `vd:astro-airflow`). Otherwise:```bash# Astro CLI (local only) - operation ids, not raw pathsastro api airflow lsastro api airflow get_import_errorsastro api airflow get_dags -q '.dags[].dag_id'astro api airflow get_dag_runs -p dag_id=<dag_id>````astro api airflow` defaults to localhost + admin/admin. Override with `--api-url` / `--username` / `--password` when the project is not on 8080.For remote staging/prod, stop using this skill and use `vd:astro-airflow`.## Parse loop (new or edited DAG)```bashastro dev parse# or: make dags-import-errors```YAML/loader errors show up here, not as a failed task. After parse is clean, unpause before the first trigger.## Troubleshooting| Issue | Fix ||---|---|| Port in use | `astro config get`; stop the other stack or change the project port || DAG missing | `astro dev parse`; missing `from airflow import DAG` in the loader || Scheduler not picking up YAML | `astro dev restart --scheduler` or the repo's reparse target || Package install failed | requirements syntax; then `astro dev kill && astro dev start` || Disk full | `docker system prune` || `Variable.get` ImportError at parse | Airflow 3 parse isolation; wrap or use YAML `AIRFLOW_VARIABLE__` params |## Standalone / proxy (only if the user asks)`astro dev start --standalone` needs Airflow 3 + `uv`, no Docker. Pass `--standalone` on every follow-up command unless `astro config set dev.mode standalone`. Reverse proxy: `astro dev proxy status` (default 6563) for multiple local projects.## Related- Remote Astro: `vd:astro-airflow`- YAML DAGs: `vd:dag-factory`- Otto: `vd:delegating-to-otto`- Upstream: https://github.com/astronomer/agents/blob/main/skills/managing-astro-local-env/SKILL.md

Frequently asked questions