opencode-skills-collection 4.1.15 → 4.1.17

package/bundled-skills/tune-monitor/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/tune-monitor/UPSTREAM-NOTICE.md

@@ -0,0 +1,14 @@
+# Upstream helpers for tune-monitor
+
+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/metric-monitor.md` | `skills/tune-monitor/references/metric-monitor.md` | `057523088dba3359b4908cce65f621b30ad4ce7f` | text-only trailing whitespace and EOF blank lines normalized |
+| `references/custom-sql-monitor.md` | `skills/tune-monitor/references/custom-sql-monitor.md` | `4c8fc4ab3119bbfb9fb2bd0898910a12a3c7f7c4` | text-only trailing whitespace and EOF blank lines normalized |
+| `references/validation-monitor.md` | `skills/tune-monitor/references/validation-monitor.md` | `7babe93690acec64fcc2468ccc25406f750fc029` | text-only trailing whitespace and EOF blank lines normalized |
+| `references/table-monitor.md` | `skills/tune-monitor/references/table-monitor.md` | `7e016e96a7319c77807ec423ae9838ba98c986a1` | text-only trailing whitespace and EOF blank lines normalized |

package/bundled-skills/tune-monitor/references/custom-sql-monitor.md

@@ -0,0 +1,112 @@
+# Tuning Custom SQL Monitors
+
+This reference covers type-specific tuning guidance for custom SQL monitors (custom rules).
+Read this file after determining the monitor type in Phase 1.5.
+
+## Config fields to extract
+
+Extract these from the `get_monitors` config response for your Phase 2 analysis:
+
+- SQL query text (`sql` or `custom_sql`)
+- Alert conditions — each has an `operator` and either a `threshold_value` (explicit) or ML
+  threshold configuration
+- Warehouse name
+- Schedule interval
+
+**IMPORTANT:** Determine whether the monitor uses **ML thresholds** or **explicit thresholds**.
+This affects which tuning levers are available. ML-threshold monitors support sensitivity tuning
+(covered in Phase 3 of SKILL.md). Explicit-threshold monitors require direct threshold adjustment
+(covered below).
+
+---
+
+## Threshold adjustment (explicit thresholds)
+
+For monitors with explicit thresholds (`GT`, `LT`, `GTE`, `LTE`, `EQ`, `NE`):
+
+**When to recommend loosening a threshold:**
+- Anomalies are consistently marginal — the observed value just barely crosses the threshold
+- The margin between observed and threshold is small relative to the metric's natural variance
+- Most alerts are assessed as normal variation, not genuine issues
+
+**CRITICAL:** Always explain what the threshold value represents in business terms before
+recommending a change. The user needs to understand what "changing GT 0 to GT 5" means for their
+data quality.
+
+**Common pattern:** If the query returns a count of "bad" rows and the threshold is 0, but normal
+operations produce 1-3 rows that match the condition (e.g., stale records, delayed updates),
+recommend raising the threshold to a reasonable floor based on observed values.
+
+**Examples:**
+```yaml
+# Before: fires on any bad row
+alert_conditions:
+  - operator: GT
+    threshold_value: 0
+
+# After: tolerates up to 5 (based on observed noise floor of 1-3)
+alert_conditions:
+  - operator: GT
+    threshold_value: 5
+```
+
+**NEVER** recommend a threshold change without citing the observed anomaly values from the report.
+
+---
+
+## SQL query modifications
+
+When the SQL itself contributes to noise, recommend targeted modifications:
+
+**When to recommend SQL changes:**
+- The query lacks time-window filters and picks up stale data
+- Certain dimensions or categories are known-noisy and should be excluded
+- NULL handling is missing and causes spurious results
+- The query could benefit from a more targeted WHERE clause
+
+**NEVER** rewrite the full SQL without showing a diff. Present the original query and the proposed
+change side by side so the user can review exactly what changed.
+
+**IMPORTANT:** SQL syntax varies by warehouse. When suggesting modifications, match the warehouse
+dialect:
+
+| Warehouse | Date arithmetic example |
+|-----------|------------------------|
+| Snowflake | `DATEADD('day', -7, CURRENT_TIMESTAMP())` |
+| BigQuery | `TIMESTAMP_SUB(CURRENT_TIMESTAMP(), INTERVAL 7 DAY)` |
+| Redshift | `DATEADD(day, -7, GETDATE())` |
+| Databricks | `DATE_SUB(CURRENT_TIMESTAMP(), 7)` |
+
+---
+
+## Applying changes
+
+Use `create_or_update_sql_monitor` to update the monitor in place.
+
+1. **Always pass `monitor_uuid=<uuid>`** so the tool updates the existing monitor rather than
+   creating a new one. Use the monitor UUID from Phase 1.
+2. **Always dry-run first** (`dry_run=True`, the default) — show the user the YAML preview
+   returned in `result.yaml` and ask for confirmation before applying.
+3. **On confirmation**, call again with `dry_run=False` (and the same `monitor_uuid` plus the
+   same other parameters). The response carries the monitor's UUID in `result.monitor_uuid` and
+   a deep link in `result.instructions` — surface that to the user. `result.yaml` is `None` on
+   the live call by design.
+4. **Stale-uuid handling.** If the monitor was deleted between read and write, the tool raises a
+   clear error instructing you to retry without `monitor_uuid` (turning the intent from "update"
+   into "create"). Confirm with the user before recreating.
+
+### Common mistakes
+
+- **NEVER** omit `monitor_uuid` — this creates a duplicate monitor instead of updating.
+- **NEVER** apply changes without showing the dry-run preview first.
+- **CRITICAL: PUT semantics.** `create_or_update_sql_monitor` with `monitor_uuid` fully replaces
+  the monitor's configuration — fields you omit revert to tool defaults, they are NOT left
+  untouched. The full config from Phase 1's `get_monitors(monitor_ids=[<uuid>],
+  include_fields=["config"])` call is your source of truth: re-pass every field you want to
+  keep (sql, all alert_conditions, schedule, warehouse, audiences, notes, priority, tags, etc.)
+  alongside the ones you're changing.
+- **Diff the preview against the original.** Before running `dry_run=False`, compare the
+  rendered YAML returned in `result.yaml` against the original config — if anything you meant to
+  preserve is missing or changed, fix the call before committing.
+- **CRITICAL:** When modifying the SQL query, ensure the query still returns a single numeric
+  value. A query that returns multiple rows or non-numeric data will break the monitor.

package/bundled-skills/tune-monitor/references/metric-monitor.md

@@ -0,0 +1,118 @@
+# Tuning Metric Monitors
+
+This reference covers type-specific tuning guidance for metric monitors. Read this file after
+determining the monitor type in Phase 1.5.
+
+## Config fields to extract
+
+Extract these from the `get_monitors` config response for your Phase 2 analysis:
+
+- Monitor metric (e.g., `RELATIVE_ROW_COUNT`, `NULL_RATE`, `NUMERIC_MEAN`)
+- Segment field(s) (`segment_fields`)
+- WHERE condition (`where_condition`)
+- Aggregation bucket (`aggregate_by`: `hour`, `day`, `week`, `month`)
+- Aggregation time field (`aggregate_time_field`)
+- Collection lag (`collection_lag_minutes`)
+
+---
+
+## Threshold adjustment (explicit thresholds)
+
+For metric monitors using explicit thresholds (`GT`, `LT`, `GTE`, `LTE`, `EQ`, `NE`) instead of
+`AUTO`:
+
+- If anomalies are consistently marginal — the observed value just barely crosses the threshold —
+  recommend loosening the threshold based on observed values from the report.
+- **CRITICAL:** Always explain what the threshold value represents in the context of the metric
+  before recommending a change. For example, "NULL_RATE GT 0.05 means alert when more than 5% of
+  values are null."
+- **NEVER** recommend a threshold change without citing observed anomaly values from the report.
+
+---
+
+## WHERE condition / segment exclusion
+
+**When to recommend a WHERE condition:**
+- One or more specific segment values fire repeatedly and are assessed as expected behavior
+  (e.g., a sparse/bursty event type, a scheduled batch event)
+- The noisy segments are identifiable from the incident history
+
+**Syntax examples:**
+```yaml
+where_condition: "event_type NOT IN ('inactive_monitor', 'agent_evaluation_anom')"
+```
+```yaml
+where_condition: "status != 'test'"
+```
+
+**IMPORTANT:** Always verify the column name and values exist in the table before recommending a
+WHERE condition. Reference specific segment values from the monitor report.
+
+**High-cardinality segments:**
+- If the segment field has very high cardinality with many sparse values → recommend
+  `"high_segment_count": true` or consider removing segmentation entirely
+- **NEVER** recommend removing segmentation without explaining what signal would be lost
+
+---
+
+## Aggregation bucket changes
+
+If the monitor aggregates by `hour` and anomalies are caused by sparse or bursty segments
+(e.g., event types that fire only at certain hours), switching to `"aggregate_by": "day"` can
+dramatically reduce false positives. The daily bucket smooths out intra-day spikes that are
+normal over a 24-hour window.
+
+**When to recommend:**
+- Anomaly values are marginal at the hour level but would be within range at the daily level
+- The segment naturally has low and variable hourly counts
+
+**Trade-off:** You lose hourly granularity and may detect issues later. Always state this.
+
+**CRITICAL:** Do not recommend changing `aggregate_by` without also checking whether the
+`interval_minutes` needs to align. Hourly aggregation requires a schedule ≥60 min; daily
+requires ≥1440 min.
+
+---
+
+## Monitor restructure
+
+Recommend splitting into separate monitors when:
+- Different segment values have fundamentally different expected behaviors (e.g., one segment
+  is bursty by design, another should be steady)
+- No single `where_condition` can cleanly separate noisy segments from signal-carrying ones
+
+Recommend reviewing whether the metric and field combination is the right approach when:
+- The monitor consistently fires on patterns that are inherent to the data shape
+- A different metric would better capture the actual data quality concern
+
+---
+
+## Applying changes
+
+Use `create_or_update_metric_monitor` to update the monitor in place.
+
+1. **Always pass `monitor_uuid=<uuid>`** so the tool updates the existing monitor rather than
+   creating a new one. Use the monitor UUID from Phase 1.
+2. **Always dry-run first** (`dry_run=True`, the default) — show the user the YAML preview
+   returned in `result.yaml` and ask for confirmation before applying.
+3. **On confirmation**, call again with `dry_run=False` (and the same `monitor_uuid` plus the
+   same other parameters). The response carries the monitor's UUID in `result.monitor_uuid` and
+   a deep link in `result.instructions` — surface that to the user. `result.yaml` is `None` on
+   the live call by design.
+4. **Stale-uuid handling.** If the monitor was deleted between read and write, the tool raises a
+   clear error instructing you to retry without `monitor_uuid` (turning the intent from "update"
+   into "create"). Confirm with the user before recreating.
+
+### Common mistakes
+
+- **NEVER** omit `monitor_uuid` — this creates a duplicate monitor instead of updating.
+- **NEVER** apply changes without showing the dry-run preview first.
+- **CRITICAL: PUT semantics.** `create_or_update_metric_monitor` with `monitor_uuid` fully
+  replaces the monitor's configuration — fields you omit revert to tool defaults, they are NOT
+  left untouched. The full config from Phase 1's `get_monitors(monitor_ids=[<uuid>],
+  include_fields=["config"])` call is your source of truth: re-pass every field you want to
+  keep (schedule, audiences, segment_fields, where_condition, sensitivity, collection_lag_hours,
+  notes, priority, tags, etc.) alongside the ones you're changing.
+- **Diff the preview against the original.** Before running `dry_run=False`, compare the
+  rendered YAML returned in `result.yaml` against the original config — if anything you meant to
+  preserve is missing or changed, fix the call before committing.

package/bundled-skills/tune-monitor/references/table-monitor.md

@@ -0,0 +1,138 @@
+# Tuning Table Monitors
+
+This reference covers type-specific tuning guidance for table monitors. Read this file after
+determining the monitor type in Phase 1.5.
+
+Table monitors cover multiple tables and metrics (freshness, volume change, unchanged size,
+schema). Each (table, metric) pair can be tuned independently.
+
+## Config fields to extract
+
+Extract these from the monitor report for your Phase 2 analysis:
+
+- Which tables and metrics the monitor covers
+- Per (table, metric) pair: current sensitivity or explicit threshold
+- Which (table, metric) pairs are firing and how often
+- The metric type for each anomaly: `last_updated_on` (freshness), `total_row_count` /
+  `total_byte_count` (volume change), `total_row_count_last_changed_on` /
+  `total_byte_count_last_changed_on` (unchanged size), or schema
+
+---
+
+## Key constraint: one recommendation per (table, metric) pair
+
+Each recommendation **MUST** target exactly one table MCON and one metric. Do NOT group multiple
+tables into a single recommendation, even if the change is identical. The apply step makes one
+tool call per recommendation.
+
+---
+
+## Correlated anomalies
+
+When multiple (table, metric) pairs fire within a short window (minutes to a few hours), they
+likely share a common cause — e.g., a delayed pipeline affects freshness across several tables,
+or a bulk load triggers volume anomalies on related tables. Before counting anomalies per pair,
+group alerts by time proximity and assess whether they stem from the same upstream event. A burst
+of correlated alerts is one noise source, not many independent ones — address the root cause
+rather than tuning each pair separately.
+
+---
+
+## Minimum anomaly threshold
+
+Only recommend tuning a (table, metric) pair if it has **3 or more anomalies** in the report.
+A pair with 1-2 anomalies is not a clear noise pattern — it could be legitimate.
+
+For pairs with only 3-4 anomalies, require **strong supporting evidence**: consistent marginal
+breaches, TSA confirming normal variation, or NOT_ACKNOWLEDGED status on all. A handful of
+anomalies alone is not enough — the pattern must clearly indicate noise.
+
+---
+
+## Tuning levers by metric
+
+### Freshness (`last_updated_on`)
+
+- **Sensitivity**: LOW / MEDIUM / HIGH. Lower when tables have known late-arriving data.
+- **Explicit threshold**: set a fixed threshold in minutes. Use when the table has a known SLA
+  (e.g., "this table updates every 6 hours -> set threshold to 420 minutes").
+- Use the delay and threshold values from the incident to judge whether the current sensitivity
+  is too tight.
+
+### Volume change (`total_row_count`, `total_byte_count`)
+
+- **Sensitivity**: LOW / MEDIUM / HIGH. Lower for tables with bursty or seasonal patterns.
+- **Explicit thresholds**: set `upper_threshold_pct` and `lower_threshold_pct` (e.g., 50 means
+  50% change). Also requires `threshold_lookback_minutes`.
+- Check the delta vs threshold in the incident — if deltas are consistently just above the auto
+  threshold, lower sensitivity. If the expected range is known, use explicit thresholds.
+
+### Unchanged size (`total_row_count_last_changed_on`, `total_byte_count_last_changed_on`)
+
+- **Sensitivity**: LOW / MEDIUM / HIGH. Lower for tables that legitimately go quiet (weekends,
+  batch jobs).
+- **Explicit threshold**: set a fixed threshold in minutes for how long the table can remain
+  unchanged before alerting.
+- Check "time since update" vs threshold in the incident — if the table regularly goes quiet
+  for known periods, set an explicit threshold above that period.
+
+### Schema anomalies
+
+**Do NOT recommend changes for schema anomalies** — they are not tunable via the
+asset-rule tool. (Schema change is a separate per-table on/off flag via
+`create_or_update_table_monitor_asset_rule` with `rule_type="schema_monitor"`,
+but that's a different intent from tuning detector sensitivity.)
+
+---
+
+## Sensitivity vs explicit thresholds
+
+For ML thresholds (`threshold_type=auto`), always try **lowering sensitivity first**. Only
+switch to explicit thresholds if:
+- The lowest sensitivity still fires on expected behavior, OR
+- The user has a clear SLA or schedule that makes a fixed threshold more appropriate
+
+---
+
+## Applying changes
+
+Table monitor tuning uses **`create_or_update_table_monitor_asset_rule`** — **not**
+`create_or_update_table_monitor`. The single tool covers all three OOTB detectors;
+pick the per-metric variant via `rule_type`:
+
+| Metric | `rule_type` arg |
+|---|---|
+| Freshness (`last_updated_on`) | `last_updated_on` |
+| Volume change (`total_row_count`) | `total_row_count` |
+| Unchanged size (`total_row_count_last_changed_on`) | `total_row_count_last_changed_on` |
+
+Each tool call targets one `(table, rule_type)` pair. Pass the MCON in the `table`
+arg (the warehouse is parsed from it). For each `rule_type`, pick **one of two
+paths**:
+
+- **AUTO sensitivity** (default lever):
+  - `rule_type="last_updated_on"`: pass `threshold_sensitivity` (`low` / `medium` / `high`).
+  - `rule_type="total_row_count"` (volume): pass `alert_conditions=[{"type": "lookback", "operator": "AUTO", "threshold_sensitivity": "low"|"medium"|"high"}]`.
+  - `rule_type="total_row_count_last_changed_on"` (UCS): pass `alert_conditions=[{"type": "threshold", "operator": "AUTO", "threshold_sensitivity": "low"|"medium"|"high"}]`.
+  - Omit `schedule_type` — the platform's existing schedule is preserved.
+- **Explicit threshold + fixed cadence**:
+  - `rule_type="last_updated_on"`: pass `freshness_threshold_minutes=<int>` (single duration).
+  - `rule_type="total_row_count"`: pass `alert_conditions=[{"type": "lookback", "operator": "OUTSIDE_RANGE", "lower_threshold": <pct>, "upper_threshold": <pct>, "threshold_lookback_minutes": <minutes>}]` — thresholds are relative percentages (e.g. -50 / 50 = ±50 %).
+  - `rule_type="total_row_count_last_changed_on"`: pass `alert_conditions=[{"type": "threshold", "operator": "GT", "threshold_value": <minutes>, "threshold_lookback_minutes": <minutes>}]` — `threshold_value` is duration in minutes.
+  - **Must** also pass `schedule_type="fixed"` plus an `interval_minutes` (or `interval_crontab`) cadence — the threshold's meaning depends on how often the check runs.
+
+1. **Always preview first** — show the user the planned changes per `(table, rule_type)` pair
+   and ask for confirmation before applying.
+2. **On confirmation**, make one tool call per recommendation.
+
+### Common mistakes
+
+- **NEVER** apply changes without showing the preview first.
+- **NEVER** group multiple tables into one recommendation — one tool call per
+  `(table, rule_type)`.
+- **NEVER** recommend tuning schema anomalies — they are not supported.
+- **NEVER** combine AUTO sensitivity with `schedule_type="fixed"` or explicit cadence
+  args — AUTO preserves the platform schedule. Conversely, **always** pass
+  `schedule_type="fixed"` + a cadence when setting an explicit threshold.
+- **IMPORTANT:** These mutations are full replacements. Pass `tags` if the current
+  config has any — omitting tags clears them.