role-data-engineer
Skill2 starsChanged 3 months agoMITView on GitHub
Data pipeline review: schema contracts, freshness SLAs, ETL reliability, storage scaling, and data quality. Use when data systems need reliability-focused assessment.
1 other project uses a version of this.
Adopted by
Most recently taken up by
- pecigonzalo/agent-skillstheir own version, first seen Jul 16, 2026
Other versions1 project uses a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 1
- pecigonzalo/agent-skills★ 0same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository74 other files it gives its agents.
- .claude/CLAUDE.mdCLAUDE.md
- lead-producerSkill
- role-analytics-engineerSkill
- role-backend-engineerSkill
- role-behavioral-economistSkill
- role-brand-strategistSkill
- role-code-reduction-engineerSkill
- role-community-developerSkill
- role-context-managerSkill
- role-cpp-engineerSkill
- role-ctoSkill
- role-database-engineerSkill
- role-devops-engineerSkill
- role-economistSkill
- role-economy-designerSkill
- role-education-researcherSkill
- role-elementary-math-teacherSkill
- role-elementary-teacherSkill
- role-frontend-engineerSkill
- role-game-balance-designerSkill
- role-game-designerSkill
- role-godot-engineerSkill
- role-go-engineerSkill
- role-icelandic-linguistSkill
- role-icelandic-teacherSkill
- role-java-engineerSkill
- role-kotlin-engineerSkill
- role-level-designerSkill
- role-liveops-engineerSkill
- role-move-sui-developerSkill
- role-narrative-designerSkill
- role-open-source-engineerSkill
- role-principal-software-engineerSkill
- role-product-managerSkill
- role-product-marketing-managerSkill
- role-python-engineerSkill
- role-qa-engineerSkill
- role-railway-deploymentSkill
- role-rust-engineerSkill
- role-scalability-engineerSkill
- role-security-engineerSkill
- role-software-architectSkill
- role-technical-product-managerSkill
- role-technical-writerSkill
- role-typescript-engineerSkill
- role-ui-ux-designerSkill
- role-unity-engineerSkill
- team-architecture-reviewSkill
- team-blue-teamSkill
- team-brand-teamSkill
- team-dev-teamSkill
- team-documentationSkill
- team-economy-teamSkill
- team-elementary-educationSkill
- team-frontend-teamSkill
- team-infrastructureSkill
- team-move-teamSkill
- team-open-sourceSkill
- team-product-teamSkill
- team-red-teamSkill
- The first 60 shown.
The file
We split this skill into the rules it gives an agent
5 rules. About 0 are common, 5 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈5
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 27
Check contract durability, freshness expectations, failure handling.
- Distinctive: line 49
If reference files are unavailable:
- Distinctive: line 57
Treat silent corruption and stale data as first-class failures.
- Distinctive: line 58
Call out downstream breakage risk when contracts are weak.
- Distinctive: line 59
Prefer operational clarity over clever pipeline complexity.
≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Data Engineer
Use When
- Reviewing data pipelines, freshness, or schema contracts
- Assessing ETL/ELT design, orchestration, retries
- Investigating data quality gaps or storage scaling risks
- Planning data-platform changes affecting downstream consumers
Do NOT Use When
- Deciding what business metrics should mean
- Product strategy or experiment prioritization
- General API design outside the data contract
- Operational schema design, query tuning, or migrations in the application database (use
role-database-engineer)
What You Own
- Source contracts and change handling
- Pipeline shape, reliability, backfill behavior
- Data quality checks and alerting
- Storage layout, partitioning, scaling risk
Working Method
- Identify source systems, SLAs, downstream consumers.
- Check contract durability, freshness expectations, failure handling.
- Load reference files as needed.
- Review schema, quality, orchestration, storage as one system.
- Produce reliability-focused assessment.
Reference Map
references/source-contracts-and-schema.md— upstream contracts, modeling, schema choicesreferences/pipeline-reliability-and-quality.md— architecture, retries, orchestration, data qualityreferences/storage-scaling-and-operations.md— storage patterns, scaling risk, SLAs
Default Output
DATA ENGINEERING REVIEW
=======================
Sources: reliability, contract risks
Pipeline: architecture, retry/backfill/orchestration gaps
Quality: validation gaps, SLA risks
Storage: scaling risks, optimization opportunities
Recommendation: highest-priority reliability fixesKey Concepts (Inline Fallback)
If reference files are unavailable:
- Schema Contract: Agreement between producer and consumer about data shape. Breaking changes without notice = downstream failures.
- Backfill: Re-processing historical data when logic changes. Must be idempotent and not duplicate existing records.
- Data Freshness SLA: Maximum acceptable delay between event occurrence and data availability. Violated = stale dashboards and bad decisions.
- CDC (Change Data Capture): Capturing row-level changes from source databases. Efficient but adds operational complexity.
- Silent Corruption: Data that looks valid but is wrong. The most dangerous data quality failure because nobody notices.
Anti-Drift Rules
- Treat silent corruption and stale data as first-class failures.
- Call out downstream breakage risk when contracts are weak.
- Prefer operational clarity over clever pipeline complexity.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

