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), lists concrete actions, includes natural trigger terms, and explicitly states when to use it. The cross-reference to the related project setup skill is a nice touch for disambiguation. Uses proper third-person voice throughout.
| 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') and when ('Use when the user wants to start, stop, or restart Airflow, view logs, query the Airflow API, troubleshoot, or fix environment issues'). Also includes a helpful cross-reference to a related skill. | 3 / 3 |
Trigger Term Quality | Includes natural keywords users would say: 'start', 'stop', 'restart Airflow', 'logs', 'Airflow API', 'troubleshoot', 'Astro CLI', 'Docker', 'environment issues'. These cover common user phrasings well. | 3 / 3 |
Distinctiveness Conflict Risk | Clearly scoped to local Airflow environment management via Astro CLI, with distinct triggers around Airflow operations. The cross-reference to 'setting-up-astro-project' further disambiguates this skill from project setup tasks. | 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, comprehensive skill that provides excellent actionable reference material for managing local Airflow environments. Its greatest strength is the breadth and specificity of executable commands, especially the API section. The main weakness is the lack of explicit validation/verification steps in multi-step workflows like upgrading Airflow or resetting environments.
Suggestions
Add a verification step after the upgrade workflow (e.g., 'astro dev run airflow version' to confirm the new version is running)
Add a validation checkpoint to the reset environment section (e.g., 'astro dev ps' to confirm containers are healthy after restart)
| 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 filler. The tables and flags are tightly formatted. | 3 / 3 |
Actionability | Nearly every section provides copy-paste ready commands with real flags and parameters. The API section is especially strong with concrete operation IDs, flag usage, and jq filter examples. No pseudocode — all executable. | 3 / 3 |
Workflow Clarity | Steps are clearly listed for individual operations (start/stop/restart, upgrade), but there are no explicit validation checkpoints or feedback loops. The upgrade section shows 'edit Dockerfile then kill+start' without a verification step to confirm the upgrade succeeded. The troubleshooting 'reset environment' is just kill+start without checking if the reset worked. | 2 / 3 |
Progressive Disclosure | The skill is well-structured with clear sections, a concise overview, and well-signaled references to related skills (setting-up-astro-project, authoring-dags, testing-dags, deploying-airflow). Content is appropriately scoped to this skill's purpose without deeply nested references. | 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.
166c98a
Table of Contents
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.