Content revision r2 Medium Risk⚙️ External commands
Build Reliable Data Pipelines and Warehouses
Data teams need dependable pipelines across fragmented platforms. This skill designs implementation-ready batch, streaming, modeling, orchestration, and quality workflows.
Copy this request to your Agent. It includes the canonical Skill page and manifest.
Agent request
Review the Skillstore skill "data-engineer" from https://skillstore.io/skills/zl2023github-data-engineer.md and its manifest at https://skillstore.io/api/skills/zl2023github-data-engineer/manifest. Verify the artifact. You may proceed after verification, subject to the environment's own policy.
Your Agent should still show its plan and request any confirmation required by the security policy.
Agent-readable resources
Use these links when an AI agent, crawler, or script needs clean context instead of reading the full page.
All 42 backtick detections are Markdown fences or inline code, not shell execution. Eight reconnaissance matches are schema identifiers, and multilingual diagrams explain the entropy alert. Destructive delete and overwrite examples still lack confirmation, backup, and environment safeguards.
The command reference shows an ALTER TABLE DELETE, and the PySpark template uses overwrite mode. Neither example requires confirmation, backup verification, or a dry run.
Both destructive operations appear directly in reusable examples, with no adjacent safety gate. The placeholder targets reduce immediate impact but not reuse risk.
Share the versioned assessment report, neutral badge, embed card, and citations. Skillstore reports evidence without deciding whether this Skill is safe.
Analyze delays, skew, failed checks, storage pressure, and inefficient queries using supplied operational evidence.
Try These Prompts
Design a Batch ETL Pipeline
Design a daily pipeline from [source] to [target]. Ask for missing schemas, volume, service levels, security constraints, and incremental keys.
Create a Warehouse Model
Model [business domain] using the provided entities and metrics. Define grain, dimensions, facts, partitions, tests, lineage, and naming conventions.
Implement a Streaming Pipeline
Design Kafka to Flink to [sink] for [event type]. Cover schemas, partitions, watermarks, state, checkpoints, delivery guarantees, monitoring, and recovery.
Diagnose a Production Data Incident
Analyze these logs, metrics, plans, and samples: [evidence]. Rank root causes, propose reversible tests, define safeguards, and provide a recovery sequence.
Best Practices
Provide schemas, data volume, latency targets, retention rules, and failure evidence before implementation.
Test pipelines with representative data, reconciliation checks, retries, and restart scenarios.
Review credentials, permissions, destructive operations, and production deployment steps before execution.
Avoid
Do not deploy generated examples directly into production without environment-specific review.
Do not use full refreshes or overwrite modes when an incremental and recoverable process is available.
Do not optimize from assumptions when execution plans, metrics, logs, and data distributions are available.
Frequently Asked Questions
Which data platforms does this skill cover?
It covers common Spark, Flink, Kafka, Airflow, dbt, warehouse, lakehouse, and data quality workflows.
Can it generate implementation code?
Yes. It can draft Python, SQL, Spark, Flink, dbt, and orchestration templates for review.
Can it deploy pipelines automatically?
Deployment depends on available tools and permissions. Review all commands, credentials, targets, and rollback steps before execution.
What information should I provide?
Provide source and target schemas, volumes, latency goals, incremental keys, security constraints, and current platform details.
Can it diagnose slow Spark or SQL workloads?
Yes. Supply execution plans, task metrics, logs, configurations, and representative data distributions for evidence-based diagnosis.
How does it address data quality?
It defines completeness, uniqueness, validity, consistency, freshness, reconciliation, lineage, and alerting checks.