setting-up-astro-project
Initialize and configure Astro/Airflow projects. Use when the user wants to create a new project, set up dependencies, configure connections/variables, or understand project structure. For running the local environment, see managing-astro-local-env.
72
88%
Does it follow best practices?
Impact
—
No eval scenarios have been run
Passed
No known issues
Quality
Discovery
89%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 well-structured skill description that clearly communicates its purpose and when to use it. The explicit boundary with the related 'managing-astro-local-env' skill is a strong differentiator. The main area for improvement is adding more concrete, specific actions beyond the general 'initialize and configure' framing.
Suggestions
Add more specific concrete actions, e.g., 'run astro dev init, configure requirements.txt/packages.txt, set up Airflow connections and variables in settings.yaml, scaffold DAG directories'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (Astro/Airflow projects) and some actions (initialize, configure, set up dependencies, configure connections/variables, understand project structure), but the actions are somewhat general and could be more concrete (e.g., 'create astro project with astro dev init', 'configure airflow connections in settings.yaml'). | 2 / 3 |
Completeness | Clearly answers both 'what' (initialize and configure Astro/Airflow projects) and 'when' (Use when the user wants to create a new project, set up dependencies, configure connections/variables, or understand project structure). Also includes a helpful boundary reference to a related skill for running the local environment. | 3 / 3 |
Trigger Term Quality | Includes strong natural keywords users would say: 'Astro', 'Airflow', 'new project', 'dependencies', 'connections', 'variables', 'project structure'. These cover common variations of how users would phrase requests about project initialization and configuration. | 3 / 3 |
Distinctiveness Conflict Risk | Clearly scoped to Astro/Airflow project initialization and configuration, with an explicit boundary drawn against the 'managing-astro-local-env' skill. The domain is specific enough to avoid conflicts with generic project setup or other tool-specific skills. | 3 / 3 |
Total | 11 / 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 strong, well-structured skill that provides concrete, actionable guidance for Astro project initialization and configuration. It excels at conciseness and actionability with real commands and config examples. The main weakness is that the validation step (`astro dev parse`) is somewhat disconnected from the workflow rather than integrated with explicit error-recovery guidance.
Suggestions
Integrate `astro dev parse` into the workflow more explicitly — e.g., after adding dependencies or connections, add a checkpoint: 'Run `astro dev parse` to validate. If errors occur, check DAG syntax and dependency availability, then re-parse.'
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is lean and efficient. It avoids explaining what Airflow or Astro is, assumes Claude knows how Dockerfiles and YAML work, and every section delivers actionable information without padding. The callout about not passing `--airflow-version` is genuinely useful non-obvious guidance. | 3 / 3 |
Actionability | Every section provides concrete, copy-paste-ready commands and configuration examples — from `astro dev init` to the full `airflow_settings.yaml` structure, Dockerfile customization, and `astro dev parse` for validation. No pseudocode or vague instructions. | 3 / 3 |
Workflow Clarity | The skill covers setup steps clearly but lacks an explicit end-to-end sequenced workflow with validation checkpoints. The `astro dev parse` validation step is present but disconnected — it appears at the end rather than integrated into a workflow (e.g., after modifying dependencies or adding connections). There's no feedback loop for what to do if `astro dev parse` fails. | 2 / 3 |
Progressive Disclosure | The skill serves as a clear overview with well-signaled references to related skills (managing-astro-local-env, authoring-dags, testing-dags, deploying-airflow). Content is appropriately scoped to project setup, and the cross-references at both the top and bottom are clearly organized and one level deep. | 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.