Skip to content
Skills Library
Data & analytics · Testing

testing-dags

/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".

Licence
Apache-2.0
Last repository change
02.06.2026

Assessment and security

90/ 100Class: good
Format25 / 25
Frontmatter with name and description, valid name, description up to 1,024 characters, name matching the folder.
Discoverability25 / 25
Description explains when to use the skill, has a reasonable length and uses third person.
Content25 / 35
At least 150 words and at most 500 lines, headings, step lists, examples or code.
Hygiene15 / 15
No placeholders such as TODO, no Windows paths, with a licence.
Riskno signals detected in the scan
Files in this package
1
Scripts
0
HTML comments
0
URLs in SKILL.md
0
Deprecation

No signals detected. Repository changed on 02.06.2026, without references to retired models or APIs.

Licence

Apache-2.0, otwarta: można używać i zmieniać, z zachowaniem licencji i informacji o zmianach.

What it does and when to use it

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".

Triggers from the description

test this dag and fix it if it failstest and debugrun the pipeline and troubleshoot issues
Original author description

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".

How it works

  1. First Action: Trigger the DAG
  2. Testing Workflow Overview
  3. Phase 1: Trigger and Monitor
  4. Phase 2: Debug Failures
  5. Phase 3: Fix and Retest
  6. Notes
Original SKILL.md headings · 50 lines, 202 words
SKILL.md preview
---
name: testing-dags
description: 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".
---

# DAG Testing Skill

Use the Airflow VS Code extension tools to test, debug, and fix DAGs in iterative cycles.

## First Action: Trigger the DAG

When the user asks to test a DAG, your first action should be:

- `trigger_dag_run` with the provided DAG ID and config

Do not do pre-flight checks unless the user asks for them.

## Testing Workflow Overview

1. Trigger and monitor
2. If success, summarize
3. If failed, debug
4. Fix and retest

## Phase 1: Trigger and Monitor

1. Trigger: `trigger_dag_run`
2. Monitor:
   - Use `get_dag_runs` to check state
   - If a specific run ID is known, use `get_dag_run_detail`

### Response Interpretation

- Success: summarize duration and outcome
- Failed: move to Phase 2
- Running: ask whether to keep polling

## Phase 2: Debug Failures

1. Use `analyse_dag_latest_run` for a full analysis of the latest run
2. If a specific run ID is known, use `get_dag_run_detail`
3. If task logs are needed, open `go_to_dag_log_view`

## Phase 3: Fix and Retest

1. Apply fixes in the DAG or related systems
2. Re-trigger with `trigger_dag_run`
3. Re-check with `get_dag_runs` or `get_dag_run_detail`

## Notes

- Prefer `analyse_dag_latest_run` for fast triage
- Use `get_dag_history` when comparing across days

Versions

RepositoryScoreLicence
This page · necatiarslan/airflow-vscode-extension90Apache-2.0
astronomer/agents100Apache-2.0
420company/artemis95MIT

Database snapshot: 13.11.2026 · package version 303d24559bb2 (SHA-256 digest of the entire package)

Downloads in the last 30 days: 0 · ranking

Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.

Similar skills

  • 95authoring-dags
    Workflow and best practices for writing Apache Airflow DAGs. Use when the user wants to create a new DAG, write pipeline code, or asks about DAG patterns and conventions. For testing and debugging DAGs, see the testing-dags skill.
  • 90debugging-dags
    Comprehensive DAG failure diagnosis and root cause analysis. Use for complex debugging requests requiring deep investigation like "diagnose and fix the pipeline" or "full root cause analysis".
  • 90authoring-dags
    Workflow and best practices for writing Apache Airflow DAGs. Use when the user wants to create a new DAG, write pipeline code, or asks about DAG patterns and conventions. For testing and debugging DAGs, see the testing-dags skill.
  • 100authoring-dags
    Workflow and best practices for writing Apache Airflow DAGs. Use when creating a new DAG, write pipeline code, handling questions about DAG patterns and conventions or extending an existing DAG with a follow-up/downstream task. ANY request shaped like 'add a DAG named X', 'write…
  • 100debugging-dags
    Comprehensive DAG failure diagnosis and root-cause analysis with structured investigation and prevention recommendations. Use when deep failure investigation is needed, a DAG fails to import/parse or 'airflow dags list' errors on a file; a task or run is failing and must be…
  • 95debugging-dags
    Comprehensive DAG failure diagnosis and root cause analysis. Use for complex debugging requests requiring deep investigation like "diagnose and fix the pipeline", "full root cause analysis", "why is this failing and how to prevent it". For simple debugging ("why did dag fail",…

Feedback and reports

Your message goes to Bartosz Sokoliński. An email address is needed only for a reply. See the privacy policy.