Data Observability Skill

Generates monitoring configurations, alerting rules, and incident response workflows for data pipelines. Silent failures are failed engagements — this skill makes them loud.

When to Use This Skill

Activate when: Setting up freshness monitoring for data sources, detecting volume anomalies in pipeline loads, implementing schema change detection, configuring alerting (Slack, PagerDuty, email), building incident response runbooks, or establishing SLA-driven observability for data pipelines.

Don't use for:

• Writing dbt models or transformations -> use dbt-transforms
• Scheduling or orchestrating pipelines -> use data-pipelines
• Data quality testing as deliverables -> use data-testing
• Loading raw files into DuckDB without monitoring intent -> use duckdb

Scope Constraints