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 identifies its domain (Astro/Airflow), provides explicit trigger conditions, and draws a clear boundary with a related skill. The main area for improvement is adding more concrete, specific actions beyond the somewhat general 'initialize and configure'. The cross-reference to the related skill is a strong distinguishing feature.
Suggestions
Consider listing more concrete actions such as 'scaffold project directory, install Python/pip dependencies, configure settings.yaml, set up Airflow connections and variables' to improve specificity.
| 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 scaffolding, install Python/Airflow dependencies, set up Airflow connections and variables in settings.yaml'). | 2 / 3 |
Completeness | Clearly answers both 'what' (initialize and configure Astro/Airflow projects, set up dependencies, configure connections/variables) and 'when' (when the user wants to create a new project, set up dependencies, configure connections/variables, or understand project structure). Also includes a helpful cross-reference to a related skill for disambiguation. | 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 related 'managing-astro-local-env' skill for running the local environment. This cross-reference significantly reduces conflict risk with the most likely overlapping skill. | 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 aspect of Astro project setup while maintaining tight token efficiency. The clear cross-references to related skills and the logical flow from initialization through validation make it easy to follow.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is lean and efficient. It doesn't explain what Airflow or Astro is, assumes Claude knows the ecosystem, and every section delivers actionable information without padding. The brief directory structure comments are useful, not verbose. | 3 / 3 |
Actionability | Every section provides concrete, copy-paste ready commands and configuration examples — from `astro dev init` to full YAML connection configs, Dockerfile examples, and export/import commands. Nothing is left as pseudocode or vague description. | 3 / 3 |
Workflow Clarity | The skill follows a clear logical sequence: initialize → add dependencies → configure connections → validate. The validation step (`astro dev parse`) is explicitly called out before running, and the dependency change reminder ('run astro dev restart') serves as a checkpoint. For a setup/initialization skill, this is well-sequenced. | 3 / 3 |
Progressive Disclosure | The skill serves as a focused 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 content is appropriately scoped to setup only. | 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
166c98a
- 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.