Skip to content
Back to search

data-with-baraa

Skills from the Data With Baraa channel.

Safety scan

A static text scan, not a guarantee. Select the badge to see what was scanned and every finding.

Checked yesterday
Badge for your README
findsafeskills safety rating

Markdown

[![findsafeskills safety rating](/api/listings/datawithbaraa--claude-code-data-engineering-skills/badge.svg)](/listings/datawithbaraa--claude-code-data-engineering-skills)

HTML

<a href="/listings/datawithbaraa--claude-code-data-engineering-skills"><img src="/api/listings/datawithbaraa--claude-code-data-engineering-skills/badge.svg" alt="findsafeskills safety rating" /></a>

Install

Install instructions from the README

As written by the repo's author. findsafeskills has not verified these steps.

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

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:

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

What was scanned

The files the safety scan read, as written by the repository's author and shown as plain text. Lines with a finding are marked.

.claude-plugin/marketplace.json · Manifest · 14 lines
  1. {
  2. "name": "data-with-baraa",
  3. "description": "Skills from the Data With Baraa channel.",
  4. "owner": {
  5. "name": "Data With Baraa"
  6. },
  7. "plugins": [
  8. {
  9. "name": "data-engineering",
  10. "source": "./",
  11. "description": "16 Claude Code skills for data engineers: profile, contract, metadata, incident, quality, reconcile, impact, toolkit, data product, docs, pull request review, big review, cost review, test data, knowledge refresh and migration."
  12. }
  13. ]
  14. }
README.md · README · 92 lines
  1. # Claude Code skills for data engineers
  2. ![The incident report of a failed run, one of the pages these skills write](docs/hero.png)
  3. 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.
  4. ⭐ If these skills help you, star the repository so other data engineers can find them too.
  5. 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.
  6. > [!NOTE]
  7. > 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).
  8. ## Install
  9. You need Claude Code with a Claude Pro, Max, Team or Enterprise plan, or a Claude Console account.
  10. ```bash
  11. git clone https://github.com/DataWithBaraa/claude-code-data-engineering-skills.git
  12. mkdir -p your-project/.claude/skills
  13. cp -r claude-code-data-engineering-skills/skills/* your-project/.claude/skills/
  14. ```
  15. Or install them as a plugin, inside Claude Code:
  16. ```text
  17. /plugin marketplace add DataWithBaraa/claude-code-data-engineering-skills
  18. /plugin install data-engineering@data-with-baraa
  19. ```
  20. 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.
  21. To get new versions, pull the repo and copy the skills again, or update the plugin under `/plugin`. Plugin updates are not automatic.
  22. ## The skills
  23. **When new data arrives**
  24. - [profile](skills/profile/SKILL.md): understand a new source before you build anything on it.
  25. - [contract](skills/contract/SKILL.md): the data contract with the source system, in the Open Data Contract Standard.
  26. - [metadata](skills/metadata/SKILL.md): every table and column described, the types from the data, the descriptions from the documents.
  27. **When something breaks**
  28. - [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.
  29. - [quality](skills/quality/SKILL.md): which checks failed or warned, and whether each table is safe to use today.
  30. - [reconcile](skills/reconcile/SKILL.md): two numbers that should agree, where they diverge and why.
  31. **Before a change goes in**
  32. - [impact](skills/impact/SKILL.md): what a change to a table, a column or a function breaks, and the safe order of the change.
  33. - [test-data](skills/test-data/SKILL.md): test data with the edge cases, and the expected result written first.
  34. - [pr-review](skills/pr-review/SKILL.md): a pull request reviewed pass by pass against your standards, with pushback.
  35. **When you need the big picture**
  36. - [toolkit](skills/toolkit/SKILL.md): the documentation site of the project, built from the repo.
  37. - [big-review](skills/big-review/SKILL.md): the whole platform from the query logs and the repo, with proposals.
  38. - [cost-review](skills/cost-review/SKILL.md): where the compute and the storage money goes, and what to cut.
  39. **When others use your data**
  40. - [data-product](skills/data-product/SKILL.md): everything a consumer needs for one table, from the guide to the contract.
  41. - [docs](skills/docs/SKILL.md): the runbook and the how-to guides, matching the code.
  42. **When the project grows**
  43. - [knowledge-refresh](skills/knowledge-refresh/SKILL.md): the knowledge Claude Code reads, checked against the code and the data.
  44. - [migration](skills/migration/SKILL.md): an old estate of jobs and tables, inventoried, rated and planned into waves.
  45. 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`.
  46. ## What they make
  47. <table>
  48. <tr>
  49. <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>
  50. <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>
  51. </tr>
  52. <tr>
  53. <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>
  54. <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>
  55. </tr>
  56. <tr>
  57. <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>
  58. <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>
  59. </tr>
  60. </table>
  61. 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.
  62. ## Make them yours
  63. 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.
  64. ## License
  65. MIT, see [LICENSE](LICENSE). The fonts of the example pages are under the SIL Open Font License, see [OFL.txt](OFL.txt).

Ratings and comments

Sign in to rate this skill.

Sign in

Free to use. If it’s helped, pass it on.