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.
95
93%
Does it follow best practices?
Impact
Pending
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 with 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 third-person voice and is concise without being vague.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: start, stop, restart Airflow, view logs, query the Airflow API, troubleshoot, and 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 strong natural keywords users would say: 'Airflow', 'Astro CLI', 'Docker', 'start', 'stop', 'restart', 'logs', 'Airflow API', 'troubleshoot', 'environment issues'. These cover a wide range of natural user queries. | 3 / 3 |
Distinctiveness Conflict Risk | Clearly scoped to local Airflow environment management via Astro CLI, which is a distinct niche. The cross-reference to 'setting-up-astro-project' explicitly disambiguates from a related skill, reducing conflict risk. | 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 skill that provides comprehensive, actionable coverage of Astro CLI local environment management. Its greatest strength is the extensive, copy-paste ready command examples, especially for the Airflow API section. The main weakness is the lack of explicit validation/verification steps after destructive operations like `astro dev kill` and the upgrade workflow.
Suggestions
Add a verification step after `astro dev kill && astro dev start` in the upgrade workflow (e.g., `astro dev ps` to confirm containers are healthy, or check the webserver responds).
Add a brief validation checkpoint to the Reset Environment section, such as running `astro dev ps` or checking http://localhost:8080 after restart to confirm recovery.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content 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 tables and flags are tightly formatted. | 3 / 3 |
Actionability | Nearly every section provides copy-paste ready commands with specific flags, parameters, and examples. The API querying section is especially thorough with concrete operation IDs, flag usage, and jq filter examples. | 3 / 3 |
Workflow Clarity | Steps are clearly listed for individual operations (start/stop/restart, upgrade), but the upgrade workflow lacks an explicit validation checkpoint after changing the Dockerfile version. The troubleshooting 'Reset Environment' section is just kill+start without verifying success. For destructive operations like `astro dev kill` (removes volumes/venv), there's no confirmation or verification step. | 2 / 3 |
Progressive Disclosure | The skill is well-structured with clear sections, a top-level note pointing to related skills for setup, and a Related Skills section at the bottom. Content is appropriately scoped to local environment management without inlining content that belongs elsewhere. For a skill of this scope, the single-file organization with clear headers is appropriate. | 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
0642adb
- 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.