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.
96
95%
Does it follow best practices?
Impact
Pending
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-crafted description that clearly defines its scope (project initialization and configuration for Astro/Airflow), provides explicit trigger conditions, and helpfully delineates its boundary from a related skill. The main area for improvement is adding more concrete, specific actions beyond the somewhat general 'initialize', 'configure', and 'set up' verbs.
| 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' (when 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 disambiguation. | 3 / 3 |
Trigger Term Quality | Includes strong natural keywords users would say: 'new project', 'set up dependencies', 'configure connections', 'variables', 'project structure', 'Astro', 'Airflow'. These cover common variations of how users would phrase requests about project initialization and configuration. | 3 / 3 |
Distinctiveness Conflict Risk | Clearly scoped to project initialization and configuration, with an explicit boundary distinguishing it from the local environment management skill ('For running the local environment, see managing-astro-local-env'). The Astro/Airflow domain is specific enough to avoid conflicts with generic project setup skills. | 3 / 3 |
Total | 11 / 12 Passed |
Implementation
100%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is an excellent skill file that is concise, actionable, and well-structured. It provides complete, executable examples for every step of project setup while maintaining tight token efficiency. The cross-references to related skills are clear and appropriately placed, and the validation step provides a useful checkpoint before proceeding to run the environment.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is lean and efficient. It avoids explaining what Airflow or Astro is, assumes Claude knows the ecosystem, and every section delivers concrete information without padding. The brief directory structure comments and inline notes are minimal and useful. | 3 / 3 |
Actionability | Every section provides copy-paste ready commands, file contents, and configuration examples. The `astro dev init`, `astro dev parse`, Dockerfile, requirements.txt, and airflow_settings.yaml examples are all fully executable and specific. | 3 / 3 |
Workflow Clarity | The skill follows a clear logical sequence: initialize → add dependencies → configure connections → validate. The validation step (`astro dev parse`) serves as an explicit checkpoint before running. The note about restarting after dependency changes is a useful operational checkpoint. For a setup/configuration skill, this workflow is well-sequenced. | 3 / 3 |
Progressive Disclosure | The skill provides a concise overview with clear, one-level-deep references to related skills (managing-astro-local-env, authoring-dags, testing-dags, deploying-airflow). The cross-references at the top and bottom are well-signaled, and the content is appropriately scoped to setup without bleeding into adjacent concerns. | 3 / 3 |
Total | 12 / 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.