flux-pipeline

Included with Lifetime

$97 forever

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

General

What this skill does


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

Files: 2

Size: 3.7 KB

Complexity: 14/100

Category: General

Source: https://github.com/jeremylongshore/claude-code-plugins-plus-skills/tree/main/plugins/ai-agency/tonone/skills/flux-pipeline

Related in General

modeling-omnistudio-epc-catalog

Included

Salesforce Industries CME EPC product-modeling skill for Product2-based catalog creation. Use when creating EPC products, configuring product attributes, building offer bundles with Product Child Items, or reviewing EPC DataPack JSON metadata for product catalog changes. TRIGGER when: user creates or updates Product2 EPC records, AttributeAssignment payloads, AttributeMetadata/AttributeDefaultValues, Offer bundles, or ProductChildItem relationships. DO NOT TRIGGER when: designing OmniScripts/FlexCards/Integration Procedures (use building-omnistudio-omniscript, building-omnistudio-flexcard, or building-omnistudio-integration-procedure), implementing Apex business logic (use generating-apex), or troubleshooting deployment pipelines (use deploying-metadata).

Generalscripts

relationship-science-coach

Included

Use this skill for direct, practical adult relationship coaching: couples conflict, repair, trust, marriage, dating, flirting, attachment patterns, emotional connection, sex, desire differences, eroticism, kink negotiation, affection, love languages, breakups, and long-term passion. Draw on Gottman, EFT and Hold Me Tight, attachment science, modern sex research, Perel, Nagoski, Kerner, Schnarch, Love and Stosny, and flexible love-language tools. Be concrete and low-hedge. Redirect only for imminent danger, abuse, coercive control, minors, non-consent, self-harm, stalking, or medical/legal/psychiatric decisions.

Generalscripts

building-sf-integrations

Included

Salesforce integration architecture and runtime plumbing with 120-point scoring. Use this skill to set up Named Credentials, External Credentials, External Services, REST/SOAP callout patterns, Platform Events, and Change Data Capture. TRIGGER when: user sets up Named Credentials, External Services, REST/SOAP callouts, Platform Events, CDC, or touches .namedCredential-meta.xml files. DO NOT TRIGGER when: Connected App/OAuth config (use configuring-connected-apps), Apex-only logic (use generating-apex), or data import/export (use handling-sf-data).

Generalscripts

venue-templates

Included

Access comprehensive LaTeX templates, formatting requirements, and submission guidelines for major scientific publication venues (Nature, Science, PLOS, IEEE, ACM), academic conferences (NeurIPS, ICML, CVPR, CHI), research posters, and grant proposals (NSF, NIH, DOE, DARPA). This skill should be used when preparing manuscripts for journal submission, conference papers, research posters, or grant proposals and need venue-specific formatting requirements and templates.

Generalscripts

let-fate-decide

Included

Draws the 12 Houses of the Zodiac Tarot spread to inject entropy into planning when prompts are vague, ambiguous, or casually delegated. Interprets the spread to guide next steps. Use when the user says 'let fate decide', 'YOLO', 'whatever', 'idk', or other nonchalant phrases, makes Yu-Gi-Oh references, or when you are about to arbitrarily pick between multiple reasonable approaches. Prefer over ask-questions-if-underspecified when the user's tone is casual or playful rather than precision-seeking.

Generalscripts

net-ops

Included

Cross-platform network troubleshooting (Windows, macOS, Linux) via local or remote shell. Use for: DNS broken, can't resolve hostnames, nslookup/dig works but apps fail, NRPT, WFP, scutil, /etc/resolver, systemd-resolved, /etc/resolv.conf, NetworkManager, VPN DNS leak residue (ProtonVPN/Mullvad/WireGuard/AnyConnect), AV/firewall blocking DNS or DoH, Tailscale DNS interaction, intermittent connectivity, remote diagnostics over SSH.

Generalscripts