Keep the warehouse trustworthy: dbt tests (not_null/unique/accepted_values/relationships) gating the build in CI, source-freshness checks, model contracts at consumer boundaries, singular tests for business invariants, and anomaly detection beyond schema tests.
How this skill is triggered — by the user, by Claude, or both
Slash command
/analytics-engineering:data-quality-testingThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
not_null / unique / accepted_values / relationships on the columns that matter; **build fails** on violation. Untested transforms = silent downstream corruption.
not_null / unique / accepted_values / relationships on the columns that matter; build fails on violation. Untested transforms = silent downstream corruption.
Assert source freshness; stop rather than serve stale marts as fresh.
Model contracts (names/types/constraints) on consumer-facing models so upstream changes can't silently break a dashboard.
Singular tests for business invariants (line items sum to order total). Anomaly detection (row-count drop, distribution shift) catches what schema tests miss -> significance to applied-statistics.
npx claudepluginhub mcorbett51090/ravenclaude --plugin analytics-engineeringGuides completion of development work by verifying tests, detecting environment, and presenting structured options for merge, PR, or cleanup.
Enforces test-driven development: write failing test first, then minimal code to pass. Use when implementing features or bugfixes.
Guides creation and editing of skills using test-driven development with pressure scenarios and subagents to verify agent compliance.