testing-dags
Complex DAG testing workflows with debugging and fixing cycles. Use for multi-step testing requests like "test this dag and fix it if it fails", "test and debug", "run the pipeline and troubleshoot issues". For simple test requests ("test dag", "run dag"), the airflow entrypoint skill handles it directly. This skill is for iterative test-debug-fix cycles.
Install
With your agent
Install OMGSkills skill "astronomer/agents:testing-dags" into this agent's normal skills directory: call the OMGSkills MCP get_install_plan tool for your agent and run the script it returns (it installs only the pinned commit and verifies SKILL.md), and stop if MCP or the pin is unavailable. Do not overwrite or change existing skills without asking me.
Manual command
git clone https://github.com/astronomer/agents /tmp/agents && ln -s /tmp/agents/skills/testing-dags ~/.claude/skills/testing-dags
From README
DAG Testing Skill Use af commands to test, debug, and fix DAGs in iterative cycles. Running the CLI These commands assume af is on PATH. Run via astro otto to get it automatically, or standalone with uv tool astro-airflow-mcp. --- Quick Validation with Astro CLI If the user has the Astro CLI available, these commands provide fast feedback without needing a running Airflow instance: Use these for quick validation during development. For full end-to-end testing against a live Airflow instance, continue to the trigger-and-wait workflow below. --- FIRST ACTION: Just Trigger the DAG When the user asks to test a DAG, your FIRST AND ONLY action should be: DO NOT: Call af dags list first Call af dags get first Call af dags errors first Use grep or ls or any other bash command Do any "pre-flight checks" Just trigger the DAG. If it fails, THEN debug. --- Testing Workflow Overview Philosophy: Try first, debug on failure.
