opencode-skills-collection 4.1.15 → 4.1.17

package/bundled-skills/monte-carlo-analyze-root-cause/UPSTREAM-LICENSE.txt

@@ -0,0 +1,201 @@
+                                 Apache License
+                           Version 2.0, January 2004
+                        http://www.apache.org/licenses/
+
+   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
+
+   1. Definitions.
+
+      "License" shall mean the terms and conditions for use, reproduction,
+      and distribution as defined by Sections 1 through 9 of this document.
+
+      "Licensor" shall mean the copyright owner or entity authorized by
+      the copyright owner that is granting the License.
+
+      "Legal Entity" shall mean the union of the acting entity and all
+      other entities that control, are controlled by, or are under common
+      control with that entity. For the purposes of this definition,
+      "control" means (i) the power, direct or indirect, to cause the
+      direction or management of such entity, whether by contract or
+      otherwise, or (ii) ownership of fifty percent (50%) or more of the
+      outstanding shares, or (iii) beneficial ownership of such entity.
+
+      "You" (or "Your") shall mean an individual or Legal Entity
+      exercising permissions granted by this License.
+
+      "Source" form shall mean the preferred form for making modifications,
+      including but not limited to software source code, documentation
+      source, and configuration files.
+
+      "Object" form shall mean any form resulting from mechanical
+      transformation or translation of a Source form, including but
+      not limited to compiled object code, generated documentation,
+      and conversions to other media types.
+
+      "Work" shall mean the work of authorship, whether in Source or
+      Object form, made available under the License, as indicated by a
+      copyright notice that is included in or attached to the work
+      (an example is provided in the Appendix below).
+
+      "Derivative Works" shall mean any work, whether in Source or Object
+      form, that is based on (or derived from) the Work and for which the
+      editorial revisions, annotations, elaborations, or other modifications
+      represent, as a whole, an original work of authorship. For the purposes
+      of this License, Derivative Works shall not include works that remain
+      separable from, or merely link (or bind by name) to the interfaces of,
+      the Work and Derivative Works thereof.
+
+      "Contribution" shall mean any work of authorship, including
+      the original version of the Work and any modifications or additions
+      to that Work or Derivative Works thereof, that is intentionally
+      submitted to Licensor for inclusion in the Work by the copyright owner
+      or by an individual or Legal Entity authorized to submit on behalf of
+      the copyright owner. For the purposes of this definition, "submitted"
+      means any form of electronic, verbal, or written communication sent
+      to the Licensor or its representatives, including but not limited to
+      communication on electronic mailing lists, source code control systems,
+      and issue tracking systems that are managed by, or on behalf of, the
+      Licensor for the purpose of discussing and improving the Work, but
+      excluding communication that is conspicuously marked or otherwise
+      designated in writing by the copyright owner as "Not a Contribution."
+
+      "Contributor" shall mean Licensor and any individual or Legal Entity
+      on behalf of whom a Contribution has been received by Licensor and
+      subsequently incorporated within the Work.
+
+   2. Grant of Copyright License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      copyright license to reproduce, prepare Derivative Works of,
+      publicly display, publicly perform, sublicense, and distribute the
+      Work and such Derivative Works in Source or Object form.
+
+   3. Grant of Patent License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      (except as stated in this section) patent license to make, have made,
+      use, offer to sell, sell, import, and otherwise transfer the Work,
+      where such license applies only to those patent claims licensable
+      by such Contributor that are necessarily infringed by their
+      Contribution(s) alone or by combination of their Contribution(s)
+      with the Work to which such Contribution(s) was submitted. If You
+      institute patent litigation against any entity (including a
+      cross-claim or counterclaim in a lawsuit) alleging that the Work
+      or a Contribution incorporated within the Work constitutes direct
+      or contributory patent infringement, then any patent licenses
+      granted to You under this License for that Work shall terminate
+      as of the date such litigation is filed.
+
+   4. Redistribution. You may reproduce and distribute copies of the
+      Work or Derivative Works thereof in any medium, with or without
+      modifications, and in Source or Object form, provided that You
+      meet the following conditions:
+
+      (a) You must give any other recipients of the Work or
+          Derivative Works a copy of this License; and
+
+      (b) You must cause any modified files to carry prominent notices
+          stating that You changed the files; and
+
+      (c) You must retain, in the Source form of any Derivative Works
+          that You distribute, all copyright, patent, trademark, and
+          attribution notices from the Source form of the Work,
+          excluding those notices that do not pertain to any part of
+          the Derivative Works; and
+
+      (d) If the Work includes a "NOTICE" text file as part of its
+          distribution, then any Derivative Works that You distribute must
+          include a readable copy of the attribution notices contained
+          within such NOTICE file, excluding those notices that do not
+          pertain to any part of the Derivative Works, in at least one
+          of the following places: within a NOTICE text file distributed
+          as part of the Derivative Works; within the Source form or
+          documentation, if provided along with the Derivative Works; or,
+          within a display generated by the Derivative Works, if and
+          wherever such third-party notices normally appear. The contents
+          of the NOTICE file are for informational purposes only and
+          do not modify the License. You may add Your own attribution
+          notices within Derivative Works that You distribute, alongside
+          or as an addendum to the NOTICE text from the Work, provided
+          that such additional attribution notices cannot be construed
+          as modifying the License.
+
+      You may add Your own copyright statement to Your modifications and
+      may provide additional or different license terms and conditions
+      for use, reproduction, or distribution of Your modifications, or
+      for any such Derivative Works as a whole, provided Your use,
+      reproduction, and distribution of the Work otherwise complies with
+      the conditions stated in this License.
+
+   5. Submission of Contributions. Unless You explicitly state otherwise,
+      any Contribution intentionally submitted for inclusion in the Work
+      by You to the Licensor shall be under the terms and conditions of
+      this License, without any additional terms or conditions.
+      Notwithstanding the above, nothing herein shall supersede or modify
+      the terms of any separate license agreement you may have executed
+      with Licensor regarding such Contributions.
+
+   6. Trademarks. This License does not grant permission to use the trade
+      names, trademarks, service marks, or product names of the Licensor,
+      except as required for reasonable and customary use in describing the
+      origin of the Work and reproducing the content of the NOTICE file.
+
+   7. Disclaimer of Warranty. Unless required by applicable law or
+      agreed to in writing, Licensor provides the Work (and each
+      Contributor provides its Contributions) on an "AS IS" BASIS,
+      WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
+      implied, including, without limitation, any warranties or conditions
+      of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
+      PARTICULAR PURPOSE. You are solely responsible for determining the
+      appropriateness of using or redistributing the Work and assume any
+      risks associated with Your exercise of permissions under this License.
+
+   8. Limitation of Liability. In no event and under no legal theory,
+      whether in tort (including negligence), contract, or otherwise,
+      unless required by applicable law (such as deliberate and grossly
+      negligent acts) or agreed to in writing, shall any Contributor be
+      liable to You for damages, including any direct, indirect, special,
+      incidental, or consequential damages of any character arising as a
+      result of this License or out of the use or inability to use the
+      Work (including but not limited to damages for loss of goodwill,
+      work stoppage, computer failure or malfunction, or any and all
+      other commercial damages or losses), even if such Contributor
+      has been advised of the possibility of such damages.
+
+   9. Accepting Warranty or Additional Liability. While redistributing
+      the Work or Derivative Works thereof, You may choose to offer,
+      and charge a fee for, acceptance of support, warranty, indemnity,
+      or other liability obligations and/or rights consistent with this
+      License. However, in accepting such obligations, You may act only
+      on Your own behalf and on Your sole responsibility, not on behalf
+      of any other Contributor, and only if You agree to indemnify,
+      defend, and hold each Contributor harmless for any liability
+      incurred by, or claims asserted against, such Contributor by reason
+      of your accepting any such warranty or additional liability.
+
+   END OF TERMS AND CONDITIONS
+
+   APPENDIX: How to apply the Apache License to your work.
+
+      To apply the Apache License to your work, attach the following
+      boilerplate notice, with the fields enclosed by brackets "[]"
+      replaced with your own identifying information. (Don't include
+      the brackets!)  The text should be enclosed in the appropriate
+      comment syntax for the file format. We also recommend that a
+      file or class name and description of purpose be included on the
+      same "printed page" as the copyright notice for easier
+      identification within third-party archives.
+
+   Copyright [yyyy] [name of copyright owner]
+
+   Licensed under the Apache License, Version 2.0 (the "License");
+   you may not use this file except in compliance with the License.
+   You may obtain a copy of the License at
+
+       http://www.apache.org/licenses/LICENSE-2.0
+
+   Unless required by applicable law or agreed to in writing, software
+   distributed under the License is distributed on an "AS IS" BASIS,
+   WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+   See the License for the specific language governing permissions and
+   limitations under the License.

package/bundled-skills/monte-carlo-analyze-root-cause/UPSTREAM-NOTICE.md

@@ -0,0 +1,19 @@
+# Upstream helpers for monte-carlo-analyze-root-cause
+
+The files listed below were recovered from [monte-carlo-data/mc-agent-toolkit](https://github.com/monte-carlo-data/mc-agent-toolkit) at commit `f1ea90fa2b7fa1ece98e52a45d887c609f2a8de6`. The repository ID is `1166903665`.
+
+They retain the upstream **Apache-2.0** license reproduced in [UPSTREAM-LICENSE.txt](UPSTREAM-LICENSE.txt). This notice applies to the listed support files; it does not replace the license metadata of other catalog files. Preserve the upstream license and this attribution when redistributing them.
+
+License wording is unchanged; text-only trailing whitespace and EOF blank lines are normalized. Original license: https://github.com/monte-carlo-data/mc-agent-toolkit/blob/f1ea90fa2b7fa1ece98e52a45d887c609f2a8de6/LICENSE
+
+| Local file | Original upstream path | Original Git blob SHA | Import changes |
+| --- | --- | --- | --- |
+| `references/data-exploration.md` | `skills/analyze-root-cause/references/data-exploration.md` | `da5500bcffb6a73768afd47fad68e388925ba411` | text-only trailing whitespace and EOF blank lines normalized |
+| `references/intake-no-incident.md` | `skills/analyze-root-cause/references/intake-no-incident.md` | `446691aec627ccead96df649171fa1ff229c9eb5` | text-only trailing whitespace and EOF blank lines normalized |
+| `references/common-root-causes.md` | `skills/analyze-root-cause/references/common-root-causes.md` | `4c68668a6622a4e844438aa6427895182df9b67c` | text-only trailing whitespace and EOF blank lines normalized |
+| `references/freshness-investigation.md` | `skills/analyze-root-cause/references/freshness-investigation.md` | `bcdf5bbbaaf15b8883fb3531f11fc104d73cba0d` | text-only trailing whitespace and EOF blank lines normalized |
+| `references/volume-investigation.md` | `skills/analyze-root-cause/references/volume-investigation.md` | `ad967b28967bf034c8f1abc4e62ae486430f861f` | text-only trailing whitespace and EOF blank lines normalized |
+| `references/schema-investigation.md` | `skills/analyze-root-cause/references/schema-investigation.md` | `1e9eb0608e3c8061a259aaa73a9e11fb418b6474` | text-only trailing whitespace and EOF blank lines normalized |
+| `references/etl-failure-investigation.md` | `skills/analyze-root-cause/references/etl-failure-investigation.md` | `8062d1d034e582215c347b66ebb076852809781e` | text-only trailing whitespace and EOF blank lines normalized |
+| `references/query-change-investigation.md` | `skills/analyze-root-cause/references/query-change-investigation.md` | `a65b7fd423ebc832c9d779bd12551980cffc32d0` | text-only trailing whitespace and EOF blank lines normalized |
+| `references/field-anomaly-investigation.md` | `skills/analyze-root-cause/references/field-anomaly-investigation.md` | `06959a4956841b4b12e7d7ba311408c62f999f5e` | text-only trailing whitespace and EOF blank lines normalized |

package/bundled-skills/monte-carlo-analyze-root-cause/references/common-root-causes.md

@@ -0,0 +1,79 @@
+# Common Root Cause Catalog
+
+After gathering evidence, match your findings against these known root cause patterns. Each pattern has a signature (what the evidence looks like) and a typical fix.
+
+## ETL & Pipeline Causes
+
+### Pipeline scheduling failure
+**Signature:** Table freshness delayed. No write queries in the expected window. ETL platform shows task failure or no task execution.
+**Fix:** Check pipeline scheduler (cron, Airflow scheduler, dbt Cloud). Restart the job. Check for permission changes on the service account.
+
+### Upstream cascade
+**Signature:** Table is stale AND at least one upstream table is also stale. The upstream staleness started first.
+**Fix:** Fix the upstream table first — this table will refresh automatically once its input is fresh.
+
+### Resource contention / timeout
+**Signature:** Queries are running but taking much longer than usual. Pipeline timeouts. Warehouse queue depth is high.
+**Fix:** Scale the warehouse, optimize the query, or schedule during off-peak hours.
+
+### Permission / credential change
+**Signature:** Queries fail with "access denied" or "permission denied" errors. Worked fine before a specific date.
+**Fix:** Check service account permissions. Re-grant access to the source data.
+
+---
+
+## Query & Code Causes
+
+### Query regression
+**Signature:** Query text changed around the time of the incident. New SQL produces different output (more/fewer rows, different values, nulls).
+**Fix:** Review the query change. Revert or fix the SQL. Compare old vs new output.
+
+### JOIN cardinality change
+**Signature:** Row count changed dramatically. Query change shows JOIN modification (INNER ↔ LEFT, new JOIN added, JOIN key changed).
+**Fix:** Review the JOIN logic. Check for fanout (1-to-many producing duplicates) or dropped rows (INNER JOIN filtering more than expected).
+
+### Filter/WHERE clause change
+**Signature:** Row count dropped or spiked. Query change shows WHERE clause modification.
+**Fix:** Review the filter logic. Check if the filter is too restrictive or too permissive.
+
+---
+
+## Data Quality Causes
+
+### Source data quality issue
+**Signature:** Upstream table has unexpected values. Field lineage traces the bad data to a specific upstream column. The upstream column has new NULL values, outliers, or unexpected categories.
+**Fix:** Fix the upstream data. Add data quality checks (validation monitors) at the source.
+
+### Late-arriving data / backfill
+**Signature:** Volume spike. New rows have old timestamps (data arrived late). No query change.
+**Fix:** This may be intentional (backfill). Verify with the team. Adjust monitoring windows if needed.
+
+### Schema drift
+**Signature:** Source system changed its schema (added/removed columns, changed types). Downstream ETL failed or produced wrong results.
+**Fix:** Update the ETL to handle the new schema. Add schema change monitors on the source.
+
+---
+
+## Infrastructure Causes
+
+### Warehouse suspension / auto-suspend
+**Signature:** Queries queued for a long time, then ran. Freshness delay matches the warehouse suspension period.
+**Fix:** Adjust warehouse auto-suspend settings, or schedule a warm-up query before the critical pipeline.
+
+### Cluster/compute failure
+**Signature:** Databricks cluster failed to start, Airflow worker crashed, dbt Cloud runner timed out.
+**Fix:** Check infrastructure logs. Scale the compute. Retry the job.
+
+### Network / connectivity issue
+**Signature:** Intermittent failures across multiple tables. Error messages mention timeouts, connection refused, or DNS resolution.
+**Fix:** Check network connectivity. Review cloud provider status page.
+
+---
+
+## How to use this catalog
+
+1. After gathering evidence in Steps 1-6 of the main workflow, review the signatures above.
+2. Match your evidence to the closest pattern.
+3. Present the root cause with the specific evidence that matched.
+4. Suggest the fix from the catalog, adapted to the user's specific situation.
+5. If no pattern matches, say so — novel root causes do exist. Present the evidence and let the user draw conclusions.

package/bundled-skills/monte-carlo-analyze-root-cause/references/data-exploration.md

@@ -0,0 +1,149 @@
+# Data Exploration Patterns
+
+Use this reference when a database MCP server is available (Snowflake, BigQuery, Redshift, Databricks) for direct SQL investigation. These patterns are modeled after Monte Carlo's internal data exploration agent.
+
+**Important:** Always use fully qualified table names (`database.schema.table`). The session may not have a default database or schema.
+
+## Dialect awareness
+
+Adjust SQL syntax based on the warehouse type. Common differences:
+
+| Pattern | Snowflake | BigQuery | Redshift |
+|---------|-----------|----------|----------|
+| Date subtraction | `DATEADD('day', -7, CURRENT_TIMESTAMP())` | `DATE_SUB(CURRENT_TIMESTAMP(), INTERVAL 7 DAY)` | `DATEADD(day, -7, GETDATE())` |
+| Timestamp truncation | `DATE_TRUNC('hour', ts)` | `TIMESTAMP_TRUNC(ts, HOUR)` | `DATE_TRUNC('hour', ts)` |
+| String concatenation | `col1 || col2` | `CONCAT(col1, col2)` | `col1 || col2` |
+| Approximate count | `APPROX_COUNT_DISTINCT(col)` | `APPROX_COUNT_DISTINCT(col)` | `SELECT COUNT(DISTINCT col)` |
+
+If you're unsure of the dialect, try Snowflake syntax first — error messages will indicate the correct dialect.
+
+## Investigation queries
+
+### Sample recent rows
+
+```sql
+SELECT * FROM database.schema.table
+ORDER BY timestamp_col DESC
+LIMIT 20
+```
+
+Gives a quick feel for what the data looks like right now.
+
+### Row count over time
+
+```sql
+SELECT DATE_TRUNC('hour', timestamp_col) AS period,
+       COUNT(*) AS row_count
+FROM database.schema.table
+WHERE timestamp_col >= DATEADD('day', -7, CURRENT_TIMESTAMP())
+GROUP BY 1 ORDER BY 1
+```
+
+Reveals when volume changed — look for sudden spikes or drops.
+
+### Null rate analysis
+
+```sql
+SELECT DATE_TRUNC('day', timestamp_col) AS day,
+       COUNT(*) AS total_rows,
+       COUNT(suspect_column) AS non_null,
+       ROUND(1.0 - COUNT(suspect_column)::FLOAT / NULLIF(COUNT(*), 0), 4) AS null_rate
+FROM database.schema.table
+WHERE timestamp_col >= DATEADD('day', -14, CURRENT_TIMESTAMP())
+GROUP BY 1 ORDER BY 1
+```
+
+Shows whether null rate changed at a specific point in time.
+
+### Value distribution
+
+```sql
+SELECT suspect_column, COUNT(*) AS cnt
+FROM database.schema.table
+WHERE timestamp_col >= DATEADD('day', -1, CURRENT_TIMESTAMP())
+GROUP BY 1 ORDER BY 2 DESC
+LIMIT 30
+```
+
+Reveals if unexpected values appeared or common values disappeared.
+
+### Before vs after comparison
+
+```sql
+-- "Before" window (known good period)
+SELECT 'before' AS period,
+       COUNT(*) AS rows,
+       COUNT(DISTINCT key_col) AS unique_keys,
+       AVG(metric_col) AS avg_metric,
+       COUNT(suspect_col) AS non_null_count
+FROM database.schema.table
+WHERE timestamp_col BETWEEN 'good_start' AND 'good_end'
+
+UNION ALL
+
+-- "After" window (when issue started)
+SELECT 'after' AS period,
+       COUNT(*) AS rows,
+       COUNT(DISTINCT key_col) AS unique_keys,
+       AVG(metric_col) AS avg_metric,
+       COUNT(suspect_col) AS non_null_count
+FROM database.schema.table
+WHERE timestamp_col BETWEEN 'bad_start' AND 'bad_end'
+```
+
+Compares key metrics between a known-good period and the anomaly period.
+
+### Upstream correlation
+
+When field lineage points to an upstream source, check what upstream values correlate with the anomaly:
+
+```sql
+SELECT upstream.category_field,
+       COUNT(*) AS affected_rows,
+       AVG(downstream.anomalous_field) AS avg_value,
+       SUM(CASE WHEN downstream.anomalous_field IS NULL THEN 1 ELSE 0 END) AS null_count
+FROM database.schema.downstream_table downstream
+JOIN database.schema.upstream_table upstream
+  ON downstream.foreign_key = upstream.primary_key
+WHERE downstream.timestamp_col >= 'anomaly_start_time'
+GROUP BY 1 ORDER BY 2 DESC
+LIMIT 20
+```
+
+This reveals which upstream segments are driving the anomaly.
+
+### Duplicate detection
+
+```sql
+SELECT key_col1, key_col2, COUNT(*) AS cnt
+FROM database.schema.table
+WHERE timestamp_col >= DATEADD('day', -1, CURRENT_TIMESTAMP())
+GROUP BY 1, 2
+HAVING COUNT(*) > 1
+ORDER BY cnt DESC
+LIMIT 20
+```
+
+Checks if deduplication logic broke, introducing duplicates.
+
+### Missing expected rows
+
+```sql
+-- Find keys present yesterday but missing today
+SELECT yesterday.key_col
+FROM (SELECT DISTINCT key_col FROM database.schema.table
+      WHERE DATE(timestamp_col) = CURRENT_DATE - 1) yesterday
+LEFT JOIN (SELECT DISTINCT key_col FROM database.schema.table
+           WHERE DATE(timestamp_col) = CURRENT_DATE) today
+  ON yesterday.key_col = today.key_col
+WHERE today.key_col IS NULL
+LIMIT 20
+```
+
+## Rules for data exploration
+
+- **Always LIMIT queries** — never run unbounded SELECTs. Start with LIMIT 20, increase only if needed.
+- **Use time filters** — always scope to the relevant time window around the incident.
+- **Start broad, then narrow** — sample rows first, then targeted aggregations.
+- **Compare before vs after** — the most powerful investigation pattern.
+- **Follow the data upstream** — if this table looks wrong, check the source it reads from.

package/bundled-skills/monte-carlo-analyze-root-cause/references/etl-failure-investigation.md

@@ -0,0 +1,67 @@
+# ETL Failure Investigation Playbook
+
+Use this when an Airflow DAG, dbt model, or Databricks job failed.
+
+## Investigation steps
+
+### 1. Identify the failure
+
+Based on the alert or user description, determine which platform:
+
+**Airflow:**
+- Call `get_etl_jobs` with `platform="airflow"` and the affected table MCONs to find which DAGs/tasks write to these tables
+- Call `get_etl_issues` with `platform="airflow"` and a time range — look for:
+  - Task failure error messages
+  - Retry counts (high retries = flaky task)
+  - SLA misses
+  - Upstream task failures that blocked downstream tasks
+
+**dbt:**
+- Call `get_etl_jobs` with `platform="dbt"` and the affected table MCONs to find which dbt jobs write to these tables
+- Call `get_etl_issues` with `platform="dbt"` — look for:
+  - Compilation errors (bad SQL syntax, missing refs)
+  - Test failures (data quality assertions)
+  - Timeout errors
+  - Dependency failures (upstream model failed)
+
+**Databricks:**
+- Call `get_etl_jobs` with `platform="databricks"` and the affected table MCONs to find which Databricks jobs write to these tables
+- Call `get_etl_issues` with `platform="databricks"` — look for:
+  - Notebook execution errors
+  - Cluster startup failures
+  - Out of memory errors
+  - Permission denied errors
+
+### 2. Check what tables are affected
+
+Call `get_asset_lineage(mcons=[table_mcon], direction="DOWNSTREAM")`:
+- Which downstream tables couldn't refresh because this pipeline failed?
+- How many consumers are impacted?
+
+### 3. Check for recent changes
+
+Call `get_change_timeline` — was there a code change around the failure time?
+- Query text modifications right before the failure → code regression
+- Volume spike right before the failure → data volume overwhelmed the pipeline
+
+### 4. Check for query-level issues
+
+Call `get_query_rca` with the affected table MCONs:
+- **Failed** patterns: what errors are the queries hitting?
+- **Futile** patterns: are queries running but producing nothing?
+- Look at error messages for clues (timeout, permission, missing object)
+
+### 5. Check job runtime trends and current status
+
+Call `get_jobs_performance` to see runtime stats, failure rates, and current status:
+- Gradual slowdown → growing data volume or inefficient query
+- Sudden spike → query regression or resource contention
+
+## Common root causes
+
+- **Code deployment** — new dbt model or query has a bug
+- **Data volume spike** — source data grew faster than the pipeline can process
+- **Permission change** — service account lost access
+- **Infrastructure** — cluster sizing, warehouse suspension, network issues
+- **Dependency failure** — upstream pipeline failed, cascading downstream
+- **Schema mismatch** — upstream schema changed, breaking the ETL query

package/bundled-skills/monte-carlo-analyze-root-cause/references/field-anomaly-investigation.md

@@ -0,0 +1,107 @@
+# Field Anomaly Investigation Playbook
+
+Use this when a field-level metric drifted (null rate spike, mean shift, distribution change).
+
+## Investigation steps
+
+### 1. Understand the anomaly
+
+From the alert details, identify:
+- Which field/column is affected?
+- What metric changed? (null rate, mean, max, min, uniqueness, etc.)
+- When did the change occur?
+- What was the expected vs actual value?
+
+### 2. Trace field lineage
+
+Call `get_field_lineage` to find where this field's data comes from:
+- Which upstream table and column feeds this field?
+- Is the upstream field also anomalous?
+- Walk the field lineage chain upstream until you find the source of the bad data
+
+### 3. Check for correlated anomalies
+
+Call `get_alerts` with a time range around the incident:
+- Are there other alerts on the same table at the same time? (volume, freshness)
+- Are there alerts on upstream tables?
+- Multiple correlated anomalies often point to a single root cause
+
+### 4. Check for query changes
+
+Call `get_query_changes` — did the ETL query modify how this field is computed?
+- Changed CASE WHEN logic → different values
+- Changed COALESCE or NULL handling → null rate changes
+- Changed aggregation → mean/sum shifts
+- Changed type casting → precision changes
+
+### 5. Profile the data (if DB connector available)
+
+Run targeted queries to understand the field's behavior:
+
+```sql
+-- Null rate over time
+SELECT DATE_TRUNC('day', timestamp_col) AS day,
+       COUNT(*) AS total,
+       COUNT(field_name) AS non_null,
+       1.0 - COUNT(field_name) / COUNT(*) AS null_rate
+FROM table
+WHERE timestamp_col >= DATEADD('day', -14, CURRENT_TIMESTAMP())
+GROUP BY 1 ORDER BY 1
+
+-- Value distribution shift
+SELECT field_name, COUNT(*) AS cnt
+FROM table
+WHERE timestamp_col >= DATEADD('day', -1, CURRENT_TIMESTAMP())
+GROUP BY 1 ORDER BY 2 DESC LIMIT 20
+
+-- Check what upstream values correlate with the anomaly
+SELECT upstream_table.key_field,
+       COUNT(*) AS affected_rows,
+       AVG(this_table.anomalous_field) AS avg_value
+FROM this_table
+JOIN upstream_table ON this_table.fk = upstream_table.pk
+WHERE this_table.timestamp_col >= 'anomaly_start_time'
+GROUP BY 1 ORDER BY 2 DESC
+```
+
+See `references/data-exploration.md` for more patterns.
+
+### 6. Check upstream data quality
+
+For the upstream table/field identified in Step 2:
+- Call `get_table_freshness` — is the upstream data fresh?
+- Call `get_table_size_history` — did upstream volume change?
+- If DB connector available, profile the upstream field directly
+
+### 7. Check column correlations (if DB connector available)
+
+Identify what other columns are associated with the "bad" rows vs normal rows. This is one of the most powerful investigation techniques:
+
+```sql
+-- Compare dimension values between anomalous and normal rows
+-- Replace anomalous_field condition with the actual anomaly (e.g., IS NULL, > threshold)
+SELECT other_column,
+       COUNT(*) AS total_rows,
+       SUM(CASE WHEN anomalous_field IS NULL THEN 1 ELSE 0 END) AS bad_rows,
+       ROUND(SUM(CASE WHEN anomalous_field IS NULL THEN 1 ELSE 0 END)::FLOAT
+             / NULLIF(COUNT(*), 0), 3) AS bad_rate
+FROM database.schema.table
+WHERE timestamp_col >= 'anomaly_start_time'
+GROUP BY 1
+HAVING COUNT(*) > 10
+ORDER BY bad_rate DESC
+LIMIT 20
+```
+
+If one dimension value has a much higher "bad rate" than others, it's likely the root cause — e.g., "all rows from source_system='legacy_api' have NULL revenue, but rows from other sources are fine."
+
+Try this across multiple columns (category fields, source identifiers, date partitions) to narrow down the pattern.
+
+## Common root causes
+
+- **Upstream data quality issue** — bad data in source propagated downstream
+- **ETL logic change** — CASE/COALESCE/type handling modified
+- **New data source** — a new upstream source introduced unexpected values
+- **Schema change** — column type changed, causing implicit conversions
+- **Backfill** — historical data reprocessed with different logic
+- **Null propagation** — upstream NULL values cascading through JOINs