Find AI tools for building data pipelines, ETL processes, and data transformation workflows.
Of the 10 data pipeline tools here, the best one to start with is unstract (rated SAFE by our security scan, ★ 7.3k). LLM-Driven Extraction of Unstructured Data — Built for API Deployments & ETL Pipeline Workflows
Data Pipeline Tools are AI-powered software designed to help developers and teams tackle data pipeline-related tasks more efficiently. These tools are typically published as open-source projects on GitHub and can be integrated into existing workflows via MCP (Model Context Protocol), Claude Skills, or standalone agent frameworks. On Agent Skills Hub, we index 10 quality-scored Data Pipeline Tools across languages including Rust, Python, Go.
In 2026, the AI agent ecosystem is maturing rapidly. Data Pipeline Tools can significantly boost development efficiency by automating repetitive tasks, reducing human error, and providing intelligent suggestions. The top 3 tools — duckle, unstract, dagu — have earned an average of 1,555 GitHub stars, reflecting strong community validation. 10 of the listed tools come with clear open-source licenses, ensuring freedom to use and modify.
When choosing among Data Pipeline Tools, consider these factors: 1) Community activity — GitHub stars and recent commit frequency indicate reliability; 2) Integration method — check if it supports MCP, Claude, or your preferred agent framework; 3) Language compatibility — the most common language in this list is Rust; 4) Quality score — Agent Skills Hub's composite score evaluates code quality, documentation completeness, and maintenance activity. Our recommendation: start with duckle — it ranks highest in both star count and quality score.
Open-source ETL and ELT tool on DuckDB. No-Code/Low-code visual data pipelines or SQL: 385 components, dbt, CDC, data quality, reverse ETL, lineage, MCP for AI agents.
LLM-Driven Extraction of Unstructured Data — Built for API Deployments & ETL Pipeline Workflows
Self-hostable workflow orchestrator for teams whose main work isn't orchestration. Declarative YAML over your scripts, SSH commands, containers, etc; keep workflows separate from business logic. One binary, no database, runs on limited H/W resources. Alternative to Airflow / Cron / Job Scheduler.
A collection of AI skills for working with Dagster
```
/plugin marketplace add dagster-io/skills
/plugin install dagster-expert@dagster-skills
/dagster-expert "What's an asset?"
```Structured Data Extractor for AI Agents. Search your documents or the web for specific data and get it back in JSON or Markdown in a single tool call.
Production-ready PySpark ETL template for Databricks — medallion architecture, DABs, tests, DQX, CI/CD, and agentic development with Claude Code.
Observability platform for Digital Employee, providing real-time tracing, session insights, and cost analysis for multi-agent workflows
| Tool | Stars | Score |
|---|---|---|
| duckle | ★ 1.1k | 65 |
| unstract | ★ 7.3k | 72 |
| dagu | ★ 4.3k | 73 |
| Seal-Report | ★ 1.6k | 69 |
| agents | ★ 451 | 74 |
| skills | ★ 211 | 64 |
| open-extract | ★ 189 | 62 |
| databricks-template | ★ 86 | 70 |
| opsrobot | ★ 135 | 50 |
| cocoindex-claude | ★ 81 | 63 |
The top data pipeline tools in 2026 are duckle, unstract, dagu. Agent Skills Hub ranks 10 options by GitHub stars, quality score (6 dimensions including completeness, examples, and agent readiness), and recent activity. The list is rebuilt every 8 hours from live GitHub data.
duckle (1.1k stars) is the most adopted choice for general data pipeline workflows, written in Rust. unstract (7.3k stars) is a strong alternative and uses Python instead. Pick by your existing stack: match the language and runtime your team already uses to minimize integration cost. If unsure, start with duckle — it has the deepest community and the most examples online.
Avoid pre-built data pipeline tools when (1) your use case requires deep customization that the tool's plugin system doesn't support, (2) you have strict compliance requirements that ban third-party dependencies, (3) the tool's maintenance is inactive (last commit >6 months ago), or (4) your data volume is small enough that a 50-line custom script is cheaper than learning the tool. For most production workflows above 100 requests/day, the time savings from a maintained tool outweigh the customization loss.
Data Pipeline focuses specifically on find ai tools for building data pipelines, etl processes, and data transformation workflows. Web Scraping is a related but distinct category — see https://agentskillshub.top/best/web-scraping/ for those tools. The two often appear in the same agent pipeline but solve different problems: choose data pipeline when your primary goal is the specific task, and web scraping when the workflow is broader.
For most teams, yes. duckle has 1.1k stars worth of community testing, handles edge cases you haven't thought of, and ships with documentation. Build your own only when (1) your requirements are deeply non-standard, (2) you have a security/compliance reason to avoid OSS dependencies, or (3) the maintenance burden is small enough (<200 lines of code) that you'll save time long-term. The break-even point is usually around 2-3 weeks of dev time saved.
Most data pipeline tools listed are open source under permissive licenses (MIT, Apache 2.0). A handful offer paid managed/cloud versions on top of free self-hosted core. Always check the LICENSE file on each tool's GitHub repository before commercial use — some use AGPL or non-commercial restrictions that may not fit your deployment model.
Grades come from a rule-based scan built on the SlowMist agent-security taxonomy, covering 11 red-flag categories including credential harvesting, data exfiltration, and curl | sh installers. It is a first-layer scan, not a manual audit — we say so rather than overstate it.
The scale of the problem is documented independently: Liu et al. (2026), in a study of 31,132 agent skills, report that 26.1% contain security vulnerabilities. Our own full-catalog census is published as a citable open dataset.
Sources & who's responsible: