flux-health

Included with Lifetime

$97 forever

Data quality and pipeline health check — freshness, schema drift, null rates, orphaned records, pipeline status. Use when asked about "data quality check", "pipeline health", "is our data fresh", or "schema drift".

General

What this skill does


# Data Quality and Pipeline Health

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 data stack:

- Check for databases: ORM configs, connection strings, migration directories
- Check for pipelines: Airflow DAGs, Dagster jobs, Prefect flows, dbt models, cron jobs
- Check for data warehouses: BigQuery, Redshift, Snowflake configs
- Check for monitoring: alerting configs, health check endpoints, dashboards
- Identify what tables and pipelines exist

If the stack is ambiguous, ask the user.

### Step 1: Check Data Freshness

For each key table or data source:

- Find `updated_at` or equivalent timestamp columns
- Query for the most recent record — how old is it?
- Compare against expected freshness (real-time data should be minutes old, daily pipelines should be < 24h)
- Flag anything stale

### Step 2: Check Schema Drift

Compare actual schema against expected:

- Read the ORM/migration-defined schema (the "expected" state)
- Check for columns that exist in the database but not in code (added manually?)
- Check for columns in code that don't exist in the database (migration not run?)
- Check for type mismatches between ORM definitions and actual column types
- Check for missing indexes that the schema defines

### Step 3: Check Data Quality

Scan for common data quality issues:

- **Null rates** on critical columns — columns that should never be null
- **Orphaned records** — foreign key references to rows that don't exist
- **Broken foreign keys** — if FK constraints are missing, check referential integrity manually
- **Duplicate records** — rows that appear to be duplicates based on natural keys
- **Constraint violations** — values outside expected ranges or enum sets

### Step 4: Check Pipeline Status

For each pipeline or scheduled job:

- Last successful run — when was it?
- Last failure — when, and was it resolved?
- Average duration — is it trending longer?
- Error rate — how often does it fail?

### Step 5: Report

Present findings by severity:

```
## Data Health Report

### Critical
- [issue] — [impact] — [remediation]

### Warning
- [issue] — [impact] — [remediation]

### Healthy
- [positive observation]

### Freshness
| Table/Source | Last Updated | Expected | Status |
|---|---|---|---|
| [table] | [timestamp] | [SLA] | [status] |

### Pipeline Status
| Pipeline | Last Run | Duration | Status |
|---|---|---|---|
| [pipeline] | [timestamp] | [duration] | [status] |
```

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

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