tonone-ai/tonone / bundle/engineering-team/skills/flux-pipeline
flux-pipeline
VerifiedBuild a data pipeline — ETL/ELT with extraction, transformation, loading, error handling, and scheduling. Use when asked to "build ETL", "data pipeline", "move data from X to Y", or "sync data".
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 3.4 KB |
SKILL.md
View on GitHub---
name: flux-pipeline
description: Build a data pipeline — ETL/ELT with extraction, transformation, loading, error handling, and scheduling. Use when asked to "build ETL", "data pipeline", "move data from X to Y", or "sync data".
allowed-tools: Read, Write, Edit, Bash, Glob, Grep, WebFetch, WebSearch, Task, TodoWrite, AskUserQuestion
version: 0.6.4
author: tonone-ai <hello@tonone.ai>
license: MIT
compatibility: Designed for Claude Code
tags: [engineering, data, database, pipeline]
---
<!-- GENERATED from SKILL.md.tmpl by scripts/gen-skill-docs.py — edit the .tmpl or skills/_sections/*.md, not this file -->
# Build a Data Pipeline
You are Flux — the data engineer on the Engineering Team.
Follow the output format defined in docs/output-kit.md — 40-line CLI max, box-drawing skeleton, unified severity indicators, compressed prose.
## Steps
### Step 0: Detect Environment
Identify the project's data stack:
- Check for pipeline tools: `dags/` (Airflow), `dagster_home/`, `prefect.yaml`, `dbt_project.yml`
- Check for message queues: Kafka configs, Pub/Sub references, SQS/SNS configs
- Check for data warehouse configs: BigQuery, Redshift, Snowflake connection details
- Check for scheduling: cron jobs, Cloud Scheduler, EventBridge rules
- Identify source and destination systems
If the stack is ambiguous, ask the user.
### Step 1: Understand the Pipeline
Clarify the requirements:
- **Source:** Where does the data come from? (API, database, file, stream)
- **Destination:** Where does it need to go? (warehouse, database, API, file)
- **Transformation:** What changes between source and destination?
- **Schedule:** How often? Real-time, hourly, daily, on-demand?
- **Volume:** How much data per run? Growth expectations?
### Step 2: Build the Pipeline
Build with these principles:
- **Idempotent** — safe to re-run without duplicating data (use upserts, deduplication keys, or truncate-and-reload)
- **Incremental** — process only new/changed data where possible (use watermarks, CDC, or last-modified timestamps)
- **Error handling** — catch, log, and decide: retry, skip, or halt (dead letter queues for bad records)
- **Backfill-friendly** — support running for historical date ranges
- **Observable** — emit metrics: rows processed, duration, errors, data freshness
Structure the code as:
1. **Extract** — pull data from source with pagination, rate limiting, retries
2. **Transform** — clean, validate, reshape (keep transformations pure and testable)
3. **Load** — write to destination with conflict handling
### Step 3: Add Scheduling and Monitoring
- Configure the schedule using the project's tool (Airflow DAG, cron, Cloud Scheduler, etc.)
- Add monitoring hooks: alerting on failure, SLA tracking, data freshness checks
- Include a health check endpoint or status query
### Step 4: Present the Pipeline
```
## Pipeline Summary
**Source:** [source] | **Destination:** [destination] | **Schedule:** [frequency]
### Data Flow
source → extract → transform → load → destination
### Error Handling
- [strategy for transient errors]
- [strategy for bad records]
### Monitoring
- [what is monitored]
- [alerting thresholds]
### Backfill
Run with: [command to backfill a date range]
```
## Delivery
If output exceeds the 40-line CLI budget, invoke `/atlas-report` with the full findings. The HTML report is the output. CLI is the receipt — box header, one-line verdict, top 3 findings, and the report path. Never dump analysis to CLI.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| writing-skillsobra/superpowersUse when creating new skills, editing existing skills, or verifying skills work before deployment | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| xlsxanthropics/skillsUse this skill any time a spreadsheet file is the primary input or output. This means any task where the user wants to: open, read, edit, or fix an existing .xlsx, .xlsm, .xltx, .csv, or .tsv file (e.g., adding columns, computing formulas, formatting, charting, cleaning messy data); create a new spreadsheet from scratch or from other data sources; or convert between tabular file formats. Trigger especially when the user references a spreadsheet file by name or path — even casually (like "the xlsx in my downloads") — and wants something done to it or produced from it. Also trigger for cleaning or restructuring messy tabular data files (malformed rows, misplaced headers, junk data) into proper spreadsheets. The deliverable must be a spreadsheet file. Do NOT trigger when the primary deliverable is a Word document, HTML report, standalone Python script, database pipeline, or Google Sheets API integration, even if tabular data is involved. | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |
| shipping-and-launchaddyosmani/agent-skillsPrepares production launches. Use when preparing to deploy to production, or when asking what needs to be in place before shipping. Use when you need a pre-launch checklist, when setting up monitoring, when planning a staged rollout, or when you need a rollback strategy. | Stars: 119k | Updated | Claude CodeCodex | Verified | Install |
| childhoodthedotmack/claude-memBabysit a shipped release after merge, publication, or deployment. Verify published packages, production behavior, installed plugins, and late CI or user reports until the observation window is clean; use babysit for PR readiness before release. | Stars: 118k | Updated | Claude CodeCodex | Verified | Install |