Skip to main content
plugin

data-engineering · datawithbaraa — Claude Code plugin: features and installation

The data-engineering Claude Code plugin gives data engineers skills for investigating pipeline failures, reviewing changes, and documenting data. The set covers 16 tasks across a data platform’s lifecycle.

MIT ★ 106 updated 2026-11-06

Install into Claude Code · Plugin marketplace All methods and platforms ↓
/plugin marketplace add DataWithBaraa/claude-code-data-engineering-skills
/plugin install data-engineering@data-with-baraa
Open on GitHub

What data-engineering does

The plugin brings together 16 skills for data engineering work, from inspecting a new source and describing tables to investigating incidents, reviewing changes, and planning migrations. Other skills compare figures, assess table quality, and examine compute and storage costs.

The skills produce reports and documentation, often as HTML pages that open in a browser. Each one has its own SKILL.md, and sample outputs are stored in references/. Claude Code must be used with a Claude Pro, Max, Team, or Enterprise plan, or a Claude Console account. Plugin updates do not install automatically.

What it helps with

  • trace a failed data pipeline to its cause
  • map the impact of a table or function change
  • find why two figures disagree
  • document tables and data projects

Example prompts for the agent

  • Profile the new source at data/landing/purchasing with /data-engineering:profile.
  • Investigate the failure from 2026-08-19 using /data-engineering:incident.
  • Review this pull request against the project standards with /data-engineering:pr-review.

How to install data-engineering

Plugin marketplace

/plugin marketplace add DataWithBaraa/claude-code-data-engineering-skills
/plugin install data-engineering@data-with-baraa

Step by step, with commands for each platform: Claude Code plugins: marketplaces, installing, and building your own

Questions about data-engineering

How do I install data-engineering in Claude Code?

In Claude Code, run /plugin marketplace add DataWithBaraa/claude-code-data-engineering-skills, then run /plugin install data-engineering@data-with-baraa.

What does data-engineering do?

It adds 16 skills for data engineering work, including source profiling, data quality checks, incident investigation, code review, and documentation.

What is required to use data-engineering?

You need Claude Code with a Claude Pro, Max, Team, or Enterprise plan, or a Claude Console account.

Source text

SKILL.md · MIT
# Claude Code skills for data engineers

![The incident report of a failed run, one of the pages these skills write](docs/hero.png)

16 Claude Code skills for the work of a data engineer beyond writing code: profiling a new source, investigating a failed pipeline, building the metadata, reviewing changes, documenting, and keeping the platform clean. Most of them end in a web page you can read and share.

⭐ If these skills help you, star the repository so other data engineers can find them too.

Seven of them are from the video [How I Use Claude Code as a Data Engineer](https://youtu.be/F5lZj1bQyUw) on the [Data With Baraa](https://www.youtube.com/@DataWithBaraa) YouTube channel. The example pages describe a fictional company with fictional data.

> [!NOTE]
> This is the first draft. We will expand and enhance the skills over time. Questions, ideas, or a skill of your own to share? Join the [🤖・claude-code channel on Discord](https://discord.gg/AFZet4FXF).

## Install

You need Claude Code with a Claude Pro, Max, Team or Enterprise plan, or a Claude Console account.

```bash
git clone https://github.com/DataWithBaraa/claude-code-data-engineering-skills.git
mkdir -p your-project/.claude/skills
cp -r claude-code-data-engineering-skills/skills/* your-project/.claude/skills/
```

Or install them as a plugin, inside Claude Code:

```text
/plugin marketplace add DataWithBaraa/claude-code-data-engineering-skills
/plugin install data-engineering@data-with-baraa
```

Then type a skill and what it needs, for example `/profile data/landing/purchasing` or `/incident 2026-08-19`. As a plugin, it is `/data-engineering:profile`. Read a skill before you use it: each one says what it reads, what it writes and what it never does.

To get new versions, pull the repo and copy the skills again, or update the plugin under `/plugin`. Plugin updates are not automatic.

## The skills

**When new data arrives**
- [profile](skills/profile/SKILL.md): understand a new source before you build anything on it.
- [contract](skills/contract/SKILL.md): the data contract with the source system, in the Open Data Contract Standard.
- [metadata](skills/metadata/SKILL.md): every table and column described, the types from the data, the descriptions from the documents.

**When something breaks**
- [incident](skills/incident/SKILL.md): a failed run, from the error to the root cause, the fix options, the email drafts and the log entry.
- [quality](skills/quality/SKILL.md): which checks failed or warned, and whether each table is safe to use today.
- [reconcile](skills/reconcile/SKILL.md): two numbers that should agree, where they diverge and why.

**Before a change goes in**
- [impact](skills/impact/SKILL.md): what a change to a table, a column or a function breaks, and the safe order of the change.
- [test-data](skills/test-data/SKILL.md): test data with the edge cases, and the expected result written first.
- [pr-review](skills/pr-review/SKILL.md): a pull request reviewed pass by pass against your standards, with pushback.

**When you need the big picture**
- [toolkit](skills/toolkit/SKILL.md): the documentation site of the project, built from the repo.
- [big-review](skills/big-review/SKILL.md): the whole platform from the query logs and the repo, with proposals.
- [cost-review](skills/cost-review/SKILL.md): where the compute and the storage money goes, and what to cut.

**When others use your data**
- [data-product](skills/data-product/SKILL.md): everything a consumer needs for one table, from the guide to the contract.
- [docs](skills/docs/SKILL.md): the runbook and the how-to guides, matching the code.

**When the project grows**
- [knowledge-refresh](skills/knowledge-refresh/SKILL.md): the knowledge Claude Code reads, checked against the code and the data.
- [migration](skills/migration/SKILL.md): an old estate of jobs and tables, inventoried, rated and planned into waves.

The seven from the video are profile, metadata, incident, toolkit, data-product, pr-review and big-review. In the video the incident skill is called `/incidents`.

## What they make

<table>
<tr>
<td width="50%"><img src="docs/profile.png" alt="The profile of a new source"><br><sub><b>profile:</b> one new source on one page</sub></td>
<td width="50%"><img src="docs/incident-root-cause.png" alt="The root cause of a failed run"><br><sub><b>incident:</b> the root cause, and the same failure in the incident log</sub></td>
</tr>
<tr>
<td width="50%"><img src="docs/impact-graph.png" alt="What a change to the orders table reaches"><br><sub><b>impact:</b> what a change to one table reaches</sub></td>
<td width="50%"><img src="docs/quality-verdict.png" alt="The verdict per table"><br><sub><b>quality:</b> a verdict for every table</sub></td>
</tr>
<tr>
<td width="50%"><img src="docs/toolkit-architecture.png" alt="The architecture page of the toolkit"><br><sub><b>toolkit:</b> the architecture, drawn from what runs</sub></td>
<td width="50%"><img src="docs/data-product.png" alt="The page of one data product"><br><sub><b>data-product:</b> one data product for its consumers</sub></td>
</tr>
</table>

Each skill is one `SKILL.md` with the job, the input, the steps, the output, what it reads, what it writes and what it never does. Most have an example result in `references/`. Open the HTML files in your browser, because GitHub only shows their code.

## Make them yours

The skills are generic on purpose. Add your own paths, standards and rules to the steps. [CLAUDE.md](CLAUDE.md) is the instructions file from the video: copy it into the root of your project and adapt it. Other Claude apps may reject the `argument-hint` line, so remove it before you upload a skill there.

## License

MIT, see [LICENSE](LICENSE). The fonts of the example pages are under the SIL Open Font License, see [OFL.txt](OFL.txt).

© Data With Baraa · MIT · DataWithBaraa/claude-code-data-engineering-skills

Similar plugins

All plugins for Data and databases →

data-engineering by other authors comes first.

data-engineering Seth Hobson data-engineering — a plugin for Claude, Claude and Cursor that helps build ETL pipelines, design data warehouses and write batch processing jobs. CX Codex ★ 42,780repo stars data-quality-frameworks Seth Hobson The data-quality-frameworks skill sets up data checks with Great Expectations, dbt tests, and data contracts. Use it for validation pipelines, CI/CD checks, and schema rules. CX Codex +1 11,230installs data-engineering-study-material reason-machines data-engineering-study-material — a study guide skill for data engineering: explains concepts, shows pipeline examples, and helps with interview prep. CX Codex +1 2,000installs data-engineer VoltAgent The data-engineer subagent investigates ETL, ingestion, and pipeline failures, then proposes a scoped fix. Use it when data contracts or reprocessing behavior need a closer look. CX Codex ★ 6,505repo stars data_engineer AgenticOrgLab The data_engineer Claude Code subagent designs batch and streaming data pipelines from stated requirements. It returns a Markdown specification covering data flow, quality checks, and operations. CX Codex ★ 776repo stars datatalks-data-engineering-zoomcamp reason-machines datatalks-data-engineering-zoomcamp is a Claude Code skill for the 9-week Data Engineering Zoomcamp, with setup guidance and code templates for Docker, Terraform, Kestra, and GCP. CX Codex +1 2,400installs agentic-bundle-aas-data-engineering-platform sickn33 and contributors The agentic-bundle-aas-data-engineering-platform plugin for Claude Code bundles skills for data engineering tasks. Marketplace installation takes two commands. CX Codex ★ 50,109repo stars

From the same set15

The whole set →
knowledge-refresh knowledge-refresh — a Claude Code skill that checks project knowledge against code and data after a release. It proposes fixes for stale or inaccurate files. CX Codex +1 ★ 106repo stars data-product Builds a data product page for people using a table. It runs when a table is released, changed, or served to consumers. CX Codex +1 ★ 106repo stars toolkit The toolkit Claude Code skill builds a project documentation site from the repository. It covers architecture, data lineage, code calls, quality checks, and runs. CX Codex +1 ★ 106repo stars migration Plans the move from legacy jobs and tables to a new platform. It lays out migration scenarios, acceptance criteria, a parallel run, and rollback. CX Codex +1 ★ 106repo stars metadata This Claude Code skill builds or extends metadata for a data source. It runs when table and column details need to be gathered from source files and documentation. CX Codex +1 ★ 106repo stars pr-review The pr-review Claude Code skill reviews a file, diff, or branch before a change is merged. It checks the work against project standards and produces an HTML report. CX Codex +1 ★ 106repo stars contract This Claude Code skill writes a data contract between a data platform and a source system. It runs when a source is added or changes how it delivers data. CX Codex +1 ★ 106repo stars profile This Claude Code skill inspects incoming files or tables and produces a data profile. It runs before work begins on a data contract or pipeline. CX Codex +1 ★ 106repo stars

Project sponsors

Companies that keep this analytics open