managing-astro-local-env
Manage local Airflow environment with Astro CLI (Docker and standalone modes). Use when the user wants to start, stop, or restart Airflow, view logs, query the Airflow API, troubleshoot, or fix environment issues. For project setup, see setting-up-astro-project.
76
93%
Does it follow best practices?
Impact
—
No eval scenarios have been run
Passed
No known issues
Quality
Discovery
100%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This is a strong skill description that clearly defines its scope (local Airflow environment management via Astro CLI), lists concrete actions users would request, includes an explicit 'Use when' clause with natural trigger terms, and even disambiguates from a related skill. It follows all best practices including third-person voice and concise phrasing.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: start, stop, restart Airflow, view logs, query the Airflow API, troubleshoot, fix environment issues. Also specifies Docker and standalone modes. | 3 / 3 |
Completeness | Clearly answers both 'what' (manage local Airflow environment with Astro CLI in Docker and standalone modes) and 'when' (explicit 'Use when...' clause listing trigger scenarios). Also includes a helpful cross-reference to a related skill for disambiguation. | 3 / 3 |
Trigger Term Quality | Includes natural keywords users would say: 'start', 'stop', 'restart Airflow', 'view logs', 'Airflow API', 'troubleshoot', 'Astro CLI', 'Docker', 'standalone'. These cover common user phrasings well. | 3 / 3 |
Distinctiveness Conflict Risk | Clearly scoped to local Airflow environment management via Astro CLI, with explicit disambiguation from the 'setting-up-astro-project' skill. The niche is well-defined and unlikely to conflict with other skills. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
87%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a high-quality, well-structured reference skill that provides comprehensive, actionable coverage of Astro CLI local environment management. Its greatest strength is the density of executable commands with clear context, especially the thorough API section. The main weakness is the lack of explicit validation checkpoints in multi-step workflows like upgrades and environment resets, where confirming success before proceeding would prevent errors.
Suggestions
Add a validation step after `astro dev upgrade-test` (e.g., 'Review output for breaking changes before proceeding') and after `astro dev start` in the upgrade workflow (e.g., 'Verify with `astro dev ps` and check `astro api airflow get_import_errors`').
In the Reset Environment section, add a verification step: after `astro dev start`, confirm the environment is healthy with `astro dev ps` and optionally `astro dev parse`.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is lean and efficient throughout. It avoids explaining what Airflow, Docker, or CLI tools are, assumes Claude's competence, and every section delivers concrete commands without padding. The few explanatory notes (e.g., standalone requirements, proxy behavior) are brief and necessary. | 3 / 3 |
Actionability | Nearly every section provides copy-paste ready commands with specific flags, parameters, and real examples. The API section is especially thorough with concrete operation IDs, flag usage, and jq filter examples. The upgrade section gives an executable two-step process with a real Dockerfile snippet. | 3 / 3 |
Workflow Clarity | Individual commands and their purposes are clear, but multi-step workflows lack explicit validation checkpoints. For example, the upgrade workflow doesn't mention verifying the upgrade-test results before proceeding, and the reset workflow is just 'kill then start' without confirming success. The troubleshooting table is helpful but reactive rather than integrated into workflows as validation steps. | 2 / 3 |
Progressive Disclosure | Content is well-organized into clearly labeled sections with a logical progression from basic (start/stop) to advanced (API querying, troubleshooting, upgrades). Cross-references to related skills are clear and one-level deep. The standalone mode callout within the Docker section is well-signaled. No bundle files are needed for this reference-style skill. | 3 / 3 |
Total | 11 / 12 Passed |
Validation
100%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 11 / 11 Passed
Validation for skill structure
No warnings or errors.
- Repository
- astronomer/agents
- Commit
535a040
- Reviewed
Table of Contents
Is this your skill?
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.