Agent skill

Setting Up Astro Project

Initialize and configure Astro/Airflow projects. An agent skill from astronomer/agents.

Apache-2.0Auto-check passedData & Analytics

Install Setting Up Astro Project

skills CLI

$ npx skills add astronomer/agents --skill setting-up-astro-project -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI

$ gh skill install astronomer/agents setting-up-astro-project --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy

$ git clone --depth 1 https://github.com/astronomer/agents.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/setting-up-astro-project .claude/skills/setting-up-astro-project && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Paste into Claude Code

Install the "setting-up-astro-project" agent skill from https://github.com/astronomer/agents/tree/main/skills/setting-up-astro-project into .claude/skills/setting-up-astro-project/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "setting-up-astro-project", then confirm the skill loads.

Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

$skill-installer

$skill-installer install https://github.com/astronomer/agents/tree/main/skills/setting-up-astro-project

Type this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.

skills CLI

$ npx skills add astronomer/agents --skill setting-up-astro-project -a codex

Project install goes to .agents/skills/; add -g for ~/.codex/skills/.

GitHub CLI

$ gh skill install astronomer/agents setting-up-astro-project --agent codex

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/astronomer/agents.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/setting-up-astro-project .agents/skills/setting-up-astro-project && rm -rf skills-src

Use ~/.agents/skills/ instead of .agents/skills for a personal install.

Codex skills documentation · loads skills from .agents/skills/

Paste into Codex

Install the "setting-up-astro-project" agent skill from https://github.com/astronomer/agents/tree/main/skills/setting-up-astro-project into .agents/skills/setting-up-astro-project/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "setting-up-astro-project", then confirm the skill loads.

Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

skills CLI

$ npx skills add astronomer/agents --skill setting-up-astro-project -a cursor

Project install goes to .agents/skills/; add -g for ~/.cursor/skills/.

GitHub CLI

$ gh skill install astronomer/agents setting-up-astro-project --agent cursor

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/astronomer/agents.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/setting-up-astro-project .cursor/skills/setting-up-astro-project && rm -rf skills-src

Use ~/.cursor/skills/ instead of .cursor/skills for a personal install.

Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/

Paste into Cursor

Install the "setting-up-astro-project" agent skill from https://github.com/astronomer/agents/tree/main/skills/setting-up-astro-project into .cursor/skills/setting-up-astro-project/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "setting-up-astro-project", then confirm the skill loads.

Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

gemini skills install

$ gemini skills install https://github.com/astronomer/agents.git --path skills/setting-up-astro-project

--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.

skills CLI

$ npx skills add astronomer/agents --skill setting-up-astro-project -a gemini-cli

Project install goes to .agents/skills/; add -g for ~/.gemini/skills/.

GitHub CLI

$ gh skill install astronomer/agents setting-up-astro-project --agent gemini-cli

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/astronomer/agents.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/setting-up-astro-project .gemini/skills/setting-up-astro-project && rm -rf skills-src

Use ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.

Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/

Paste into Gemini CLI

Install the "setting-up-astro-project" agent skill from https://github.com/astronomer/agents/tree/main/skills/setting-up-astro-project into .gemini/skills/setting-up-astro-project/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "setting-up-astro-project", then confirm the skill loads.

Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

GitHub CLI

$ gh skill install astronomer/agents setting-up-astro-project

Installs for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).

skills CLI

$ npx skills add astronomer/agents --skill setting-up-astro-project -a github-copilot

Project install goes to .agents/skills/; add -g for ~/.copilot/skills/.

Manual copy

$ git clone --depth 1 https://github.com/astronomer/agents.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/setting-up-astro-project .github/skills/setting-up-astro-project && rm -rf skills-src

Use ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.

GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/

Paste into GitHub Copilot

Install the "setting-up-astro-project" agent skill from https://github.com/astronomer/agents/tree/main/skills/setting-up-astro-project into .github/skills/setting-up-astro-project/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "setting-up-astro-project", then confirm the skill loads.

GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

skills CLI

$ npx skills add astronomer/agents --skill setting-up-astro-project -a opencode

OpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.

GitHub CLI

$ gh skill install astronomer/agents setting-up-astro-project --agent opencode

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/astronomer/agents.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/setting-up-astro-project .opencode/skills/setting-up-astro-project && rm -rf skills-src

Use ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.

OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/

Paste into OpenCode

Install the "setting-up-astro-project" agent skill from https://github.com/astronomer/agents/tree/main/skills/setting-up-astro-project into .opencode/skills/setting-up-astro-project/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "setting-up-astro-project", then confirm the skill loads.

OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

Facts

Skill name: setting-up-astro-project
GitHub stars: 451
Token cost: ~802 tokens
SKILL.md length: 208 words
Files: 1
Skills in repo: 34
Repo updated: Oct 7, 2026
First seen: Oct 7, 2026
Licence: Apache-2.0

At a glance

Initialize and configure Astro/Airflow projects. An agent skill from astronomer/agents.

The user wants to create a new project
SKILL.md covers Initialize a New Project, Adding Dependencies, Configuring Connections &… and Validate Before Running, plus 1 more section
Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
Set up dependencies

What it does

Setting Up Astro Project is an agent skill from astronomer/agents. 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.

Its SKILL.md is about 800 tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in Data & Analytics, covering Static sites and blogs and Data pipelines and ETL. It works with Astro, Apache Airflow and Docker. The repository describes itself as: AI agent tooling for data engineering workflows. The licence is Apache-2.0.

When your agent uses it

The user wants to create a new project
Set up dependencies
Configure connections/variables
Understand project structure

Example prompts

“/setting-up-astro-project”

Requirements

Python 3
Docker

What it can do on your machine

Read from SKILL.md and the folder at commit 486ee63. It shows what the files ask for, not the result of running them.

Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md (its code samples are bash, dockerfile and yaml).
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Setting Up Astro Project loads about 802 tokens when it runs. Until then it costs about 69 tokens; SKILL.md has 208 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it: ~69
When it runs · the whole SKILL.md, loaded when a task matches: ~802

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from astronomer/agents at commit 486ee63, republished under its Apache-2.0 licence (© astronomer). 208 words, ~802 tokens.

Download SKILL.mdSave it as .claude/skills/setting-up-astro-project/SKILL.md (or your agent's skills folder).

name: setting-up-astro-project
description: 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.

Astro Project Setup

This skill helps you initialize and configure Airflow projects using the Astro CLI.

To run the local environment, see the managing-astro-local-env skill. To write DAGs, see the authoring-dags skill. Open-source alternative: If the user isn't on Astro, guide them to Apache Airflow's Docker Compose quickstart for local dev and the Helm chart for production. For deployment strategies, use the deploying-airflow skill.

Initialize a New Project

bash

astro dev init

Don't pass --airflow-version or --runtime-version unless the user explicitly asks for a specific pin. Plain astro dev init resolves to the latest Astro Runtime — that's the right default. Specifying a version risks pinning to a stale value from training data. If the user wants to know what was installed, read the generated Dockerfile afterward instead of guessing.

Creates this structure:

project/
├── dags/                # DAG files
├── include/             # SQL, configs, supporting files
├── plugins/             # Custom Airflow plugins
├── tests/               # Unit tests
├── Dockerfile           # Image customization
├── packages.txt         # OS-level packages
├── requirements.txt     # Python packages
└── airflow_settings.yaml # Connections, variables, pools

Adding Dependencies

Python Packages (requirements.txt)

apache-airflow-providers-snowflake==5.3.0
pandas==2.1.0
requests>=2.28.0

OS Packages (packages.txt)

gcc
libpq-dev

Custom Dockerfile

For complex setups (private PyPI, custom scripts):

dockerfile

FROM quay.io/astronomer/astro-runtime:12.4.0

RUN pip install --extra-index-url https://pypi.example.com/simple my-package

After modifying dependencies: Run astro dev restart

Configuring Connections & Variables

airflow_settings.yaml

Loaded automatically on environment start:

yaml

airflow:
  connections:
    - conn_id: my_postgres
      conn_type: postgres
      host: host.docker.internal
      port: 5432
      login: user
      password: pass
      schema: mydb

  variables:
    - variable_name: env
      variable_value: dev

  pools:
    - pool_name: limited_pool
      pool_slot: 5

Export/Import

bash

# Export from running environment
astro dev object export --connections --file connections.yaml

# Import to environment
astro dev object import --connections --file connections.yaml

Validate Before Running

Parse DAGs to catch errors without starting the full environment:

bash

astro dev parse

managing-astro-local-env: Start, stop, and troubleshoot the local environment
authoring-dags: Write and validate DAGs (uses MCP tools)
testing-dags: Test DAGs (uses MCP tools)
deploying-airflow: Deploy DAGs to production (Astro, Docker Compose, Kubernetes)

Files

Just SKILL.md in skills/setting-up-astro-project of astronomer/agents.

Open the folder on GitHubat commit 486ee63

Compare with similar skills

Setting Up Astro Project next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Setting Up Astro Project compared with similar skills
Skill	Stars	Used in	Tokens	Auto-check	Licence	Repo updated
Setting Up Astro Project this skillastronomer/agents	451	—	~802	Automated safety check: Pass	Apache-2.0	2 days ago
Chart Testsastronomer/airflow-chart	297	—	~2.8k	Automated safety check: Pass	Custom licence	2 days ago
Functional Testsastronomer/airflow-chart	297	—	~2.2k	Automated safety check: Pass	Custom licence	2 days ago
Version Bumpergodatadriven/whirl	205	—	~1.2k	Automated safety check: Pass	Apache-2.0	8 days ago
Helm Chartastronomer/airflow-chart	297	—	~6.4k	Automated safety check: Pass	Custom licence	2 days ago
Upgrading Mwaa Environmentsaws/agent-toolkit-for-aws	2.8k	—	~7.3k	Automated safety check: Pass	Apache-2.0	yesterday

Similar skills

Chart Tests
astronomer/airflow-chart
A skill your agent uses when writing, editing, reviewing, or running Helm chart tests for the Astronomer airflow-chart repository.
297 GitHub stars~2.8k tokensUpdated 2 days ago
Data & AnalyticsAuto-check passed
Functional Tests
astronomer/airflow-chart
A skill your agent uses when writing, editing, reviewing, or running functional (end-to-end) tests for the Astronomer airflow-chart repository.
297 GitHub stars~2.2k tokensUpdated 2 days ago
Data & AnalyticsAuto-check passed
Version Bumper
godatadriven/whirl
Bump the Airflow or Python version across all project files.
205 GitHub stars~1.2k tokensUpdated 8 days ago
Data & AnalyticsAuto-check passed
Helm Chart
astronomer/airflow-chart
A skill your agent uses for Helm chart work - creating charts, modifying existing charts, values design, testing.
297 GitHub stars~6.4k tokensUpdated 2 days ago
Data & AnalyticsAuto-check passed
Upgrading Mwaa Environments
aws/agent-toolkit-for-aws
Official
Upgrades an MWAA environment to a newer Airflow version — within 2.x, within 3.x, or across the 2.x-to-3.x boundary.
2.8k GitHub stars~7.3k tokensUpdated yesterday
Data & AnalyticsAuto-check passed
Create Environment
godatadriven/whirl
Create a new Whirl environment in the envs/ directory. An agent skill from godatadriven/whirl.
205 GitHub stars~1.9k tokensUpdated 8 days ago
Backend & APIsAuto-check passed

Questions about Setting Up Astro Project

What does Setting Up Astro Project do?

Initialize and configure Astro/Airflow projects. An agent skill from astronomer/agents. Setting Up Astro Project is an agent skill from astronomer/agents. Initialize and configure Astro/Airflow projects.

When should I use Setting Up Astro Project?

Setting Up Astro Project fits situations like: the user wants to create a new project; set up dependencies; configure connections/variables; understand project structure.

How do I install Setting Up Astro Project in Claude Code?

Run `npx skills add astronomer/agents --skill setting-up-astro-project -a claude-code`. Or copy the skill folder (skills/setting-up-astro-project in astronomer/agents) into .claude/skills/setting-up-astro-project in your project. Claude Code loads it when a task matches its description.

How do I install Setting Up Astro Project in Codex?

Run `npx skills add astronomer/agents --skill setting-up-astro-project -a codex`. Or copy the skill folder (skills/setting-up-astro-project in astronomer/agents) into .agents/skills/setting-up-astro-project in your project. Codex loads it when a task matches its description.

Can I use Setting Up Astro Project in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add astronomer/agents --skill setting-up-astro-project -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/setting-up-astro-project, .gemini/skills/setting-up-astro-project, .github/skills/setting-up-astro-project and .opencode/skills/setting-up-astro-project in your project.

What does Setting Up Astro Project need to run?

SKILL.md names no scripts, command-line tools or credentials: Setting Up Astro Project is instructions for the agent only. Our summary lists: Python 3; Docker.

Does Setting Up Astro Project access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Setting Up Astro Project safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Setting Up Astro Project use?

Setting Up Astro Project is published under the Apache-2.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Setting Up Astro Project use?

About 802 tokens (SKILL.md is roughly 3.2k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Setting Up Astro Project?

Skills that share tags, products or a category with Setting Up Astro Project: Chart Tests (astronomer/airflow-chart, 297 stars), Functional Tests (astronomer/airflow-chart, 297 stars), Version Bumper (godatadriven/whirl, 205 stars) and Helm Chart (astronomer/airflow-chart, 297 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Setting Up Astro Project?

astronomer (a GitHub organization) maintains it in astronomer/agents, which has 451 GitHub stars. The repository holds 34 skills in this directory. The repository was last updated on October 7, 2026.

Source: astronomer/agents on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.

Install Setting Up Astro Project

Facts

At a glance

What it does

When your agent uses it

Example prompts

Requirements

What it can do on your machine

Tool permissions

Runs code

Network

Credentials

Context cost

Safety

SKILL.md

Astro Project Setup

Initialize a New Project

Adding Dependencies

Python Packages (requirements.txt)

OS Packages (packages.txt)

Custom Dockerfile

Configuring Connections & Variables

airflow_settings.yaml

Export/Import

Validate Before Running

Related Skills

Files

Compare with similar skills

Similar skills

More from astronomer/agents

Related

Questions about Setting Up Astro Project