Manage local Airflow development environment with Astro CLI commands.
Works with
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 er
AI-first code editor with Composer
Before installing skills in Cursor, ensure your development environment meets these requirements:
node --versionmanaging-astro-local-envExecute the skills CLI command in your project's root directory to begin installation:
Fetches managing-astro-local-env from astronomer/agents and configures it for Cursor.
The CLI shows a list of agents. Use arrow keys and space to select Cursor:
Confirm successful installation by checking the skill directory location:
Restart Cursor to activate managing-astro-local-env. Access via /managing-astro-local-env in your agent's command palette.
We perform automated surface-level scans (Gen AI Scanner, Socket, Snyk) during installation. These checks detect common vulnerabilities but do not guarantee complete security. Always review skill source code and verify the publisher's reputation before production use.
Skills execute code in your environment. Always review source, verify the publisher, and test in isolation before production.
Submit your Claude Code skill and start earning
Create detailed user stories, acceptance criteria, and feature specs
Example
Generate user stories for 'password reset feature' with acceptance criteria, edge cases, and test scenarios
Reduce spec writing time by 50%, ensure comprehensive coverage
Research competitors, compare features, identify gaps
Example
Analyze 5 competitor products, create feature comparison matrix, suggest differentiation opportunities
Complete competitive research in 2 hours instead of 2 days
Evaluate features using frameworks (RICE, ICE, Kano) and create prioritized backlogs
Example
Score 20 feature ideas using RICE framework, generate prioritized roadmap with rationale
0
total installs
0
this week
302
GitHub stars
0
upvotes
Run in your terminal
0
installs
0
this week
302
stars
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 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
astro dev ps
# All logs
astro dev logs
# Specific component
astro dev logs --scheduler
astro dev logs --webserver
# Follow in real-time
astro dev logs -f
# Bash into scheduler container
astro dev bash
# Run Airflow CLI commands
astro dev run airflow info
astro dev run airflow dags list
| 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 |
When things are broken:
astro dev kill
astro dev start
astro dev upgrade-test
Edit Dockerfile:
FROM quay.io/astronomer/astro-runtime:13.0.0
Restart:
astro dev kill && astro dev start
Make data-driven prioritization decisions faster
Draft PRDs, status updates, and stakeholder presentations
Example
Create executive summary of Q3 roadmap, monthly progress report, feature launch announcement
Save 3-5 hours/week on communication overhead
Prerequisites
Time Estimate
30-60 minutes to see productivity improvements
Steps
Common Pitfalls
✓ Do
✗ Don't
💡 Pro Tips
✓ Use when
Use for user story writing, competitive research, roadmap prioritization, stakeholder communication, and PRD drafting. Best for reducing repetitive documentation and research work.
✗ Avoid when
Avoid for strategic product vision (requires deep customer empathy), pricing decisions (needs market and financial expertise), or when face-to-face customer discovery is more valuable than speed.
mattpocock/skills
parcadei/continuous-claude-v3
cursor/plugins
ailabs-393/ai-labs-claude-skills
pproenca/dot-skills
mattpocock/skills
managing-astro-local-env fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
managing-astro-local-env is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
managing-astro-local-env has been reliable in day-to-day use. Documentation quality is above average for community skills.
I recommend managing-astro-local-env for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
Useful defaults in managing-astro-local-env — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
Solid pick for teams standardizing on skills: managing-astro-local-env is focused, and the summary matches what you get after install.
managing-astro-local-env has been reliable in day-to-day use. Documentation quality is above average for community skills.
managing-astro-local-env reduced setup friction for our internal harness; good balance of opinion and flexibility.
Registry listing for managing-astro-local-env matched our evaluation — installs cleanly and behaves as described in the markdown.
Keeps context tight: managing-astro-local-env is the kind of skill you can hand to a new teammate without a long onboarding doc.
showing 1-10 of 74