opencode-skills-collection 4.1.14 → 4.1.16

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

@@ -0,0 +1,67 @@
+# Freshness Investigation Playbook
+
+Use this when a table hasn't updated on its expected schedule.
+
+## Investigation steps
+
+### 1. Confirm the freshness delay
+
+Call `get_table_freshness` with the table's `full_table_id` and `resource_id`. Also call `get_table` with the same `full_table_id` — its response includes the table's `mcon`, which the lineage and query tools below need. Check:
+- When was the last successful update?
+- What's the normal update cadence? (hourly, daily, etc.)
+- How long has the delay been?
+
+### 2. Check the ETL pipeline
+
+The table is populated by an ETL pipeline. Check if the pipeline failed:
+
+**Airflow:**
+- Call `get_etl_jobs` with `platform="airflow"` to find which DAGs/tasks write to this table
+- Call `get_etl_issues` with `platform="airflow"` and a time range — look for task failures, retries, or SLA misses
+
+**dbt:**
+- Call `get_etl_jobs` with `platform="dbt"` to find which dbt jobs/models produce this table
+- Call `get_etl_issues` with `platform="dbt"` — look for compilation errors, test failures, or timeouts
+
+**Databricks:**
+- Call `get_etl_jobs` with `platform="databricks"` to find relevant jobs
+- Call `get_etl_issues` with `platform="databricks"` — look for notebook failures, cluster issues
+
+### 3. Check the write queries
+
+Call `get_queries_for_table(mcon=table_mcon, query_type="destination")` to see recent write queries:
+- Did write queries stop running entirely? → pipeline scheduling issue
+- Did write queries run but with errors? → data or permission issue
+- Did write queries run successfully but produce no rows? → upstream data issue
+
+### 4. Check upstream freshness
+
+Call `get_asset_lineage(mcons=[table_mcon], direction="UPSTREAM")` to find upstream tables, then:
+- Call `get_table_freshness` on each upstream table
+- If an upstream table is also stale, the issue is propagating from there
+- Recurse upstream until you find the root source of the delay
+
+### 5. Check ETL job performance
+
+Call `get_jobs_performance` to check if the ETL job's runtime has degraded:
+- Is the job taking longer than usual? (compare `avgDuration` to 7-day trend)
+- Is the job failing more often? (check `failureRate`)
+- Is the job currently running or stuck? (check last run status)
+- A job that's running but taking 3x longer than normal may explain the freshness delay without an outright failure
+
+Also call `get_etl_jobs` with the relevant `platform` and the table MCONs to find which specific jobs write to this table, then check their issues with `get_etl_issues`.
+
+### 6. Check for query changes
+
+Call `get_query_changes` — did someone modify the ETL query recently?
+- New JOINs that produce empty results
+- Changed WHERE clauses that filter out all data
+- Modified schedule or dependency
+
+## Common root causes
+
+- **Pipeline scheduling failure** — cron job stopped, DAG was paused, permissions revoked
+- **Upstream freshness cascade** — an upstream table is stale, blocking this table's refresh
+- **Query timeout** — the refresh query is taking too long and timing out
+- **Resource contention** — warehouse is overloaded, queries are queued
+- **Permission change** — service account lost access to source data

package/bundled-skills/monte-carlo-analyze-root-cause/references/intake-no-incident.md

@@ -0,0 +1,67 @@
+# Intake Flow: No Incident ID
+
+Use this when the user describes a data problem but doesn't have a specific Monte Carlo alert or incident ID.
+
+## Goal
+
+Narrow down: **which table**, **what type of issue**, **when it started**, and whether Monte Carlo already detected it.
+
+## Steps
+
+### 1. Ask clarifying questions
+
+Get the essentials from the user:
+- **What table or data asset** is affected? (table name, dashboard, report)
+- **What looks wrong?** (stale data, wrong numbers, missing rows, new columns, etc.)
+- **When did you notice it?** (approximate timestamp helps scope the search)
+- **Which warehouse?** (if they have multiple)
+
+### 2. Find the table
+
+Call `search(query="table_name")` to find the table's MCON and metadata.
+
+If the user mentions a dashboard or report, search for it and then trace lineage upstream to find the source table:
+- `search(query="dashboard_name")`
+- `get_asset_lineage(mcons=[dashboard_mcon], direction="UPSTREAM")`
+
+### 3. Search for existing alerts
+
+Call `get_alerts` with a recent time range (last 7-14 days):
+- Filter by the affected table if possible
+- Look for alerts that match the user's description (freshness, volume, schema, field metric)
+- If a matching alert exists, use its details to drive the investigation — proceed as if the user provided an incident ID
+
+### 4. Check table health
+
+Even without an alert, check the table directly:
+
+- **Freshness:** `get_table_freshness` — when was it last updated? Is it overdue?
+- **Volume:** `get_table_size_history` — has the row count changed unexpectedly?
+- **Schema:** `get_table(mcon=..., include_fields=true)` — check current schema
+- **Query activity:** `get_queries_for_table` — are write queries still running?
+
+### 5. Classify the issue type
+
+Based on the evidence gathered, determine the issue type:
+
+| Symptom | Issue Type | Next Step |
+|---------|-----------|-----------|
+| Table hasn't updated recently | Freshness | `references/freshness-investigation.md` |
+| Row count spiked or dropped | Volume | `references/volume-investigation.md` |
+| Columns added/removed/changed | Schema | `references/schema-investigation.md` |
+| Data values look wrong (nulls, weird averages) | Field anomaly | `references/field-anomaly-investigation.md` |
+| Pipeline failed or errored | ETL failure | `references/etl-failure-investigation.md` |
+| Query was modified | Query change | `references/query-change-investigation.md` |
+| Problem is about an AI agent (quality, latency, traces, conversations) | Agent issue | Hand off — read and follow `../../troubleshoot-agent-traces/SKILL.md` |
+
+### 6. Proceed to investigation
+
+Once you've identified the table, issue type, and approximate timeline, continue with Step 2 (Map the blast radius) from the main SKILL.md workflow.
+
+> **TSA note.** This intake path intentionally does **not** invoke the Troubleshooting Agent (TSA), because `run_troubleshooting_agent` requires a Monte Carlo incident UUID and this path starts without one. If Step 3 above identifies a matching alert, treat the user as having provided that alert's incident ID and re-enter the main `SKILL.md` flow at Step 1 — Step 1.5 there will auto-invoke TSA. If no matching alert is found, run the manual investigation only.
+
+## Tips
+
+- **Users often know the symptom but not the cause.** "The dashboard shows yesterday's numbers" = freshness issue. "Revenue is way too high" = volume or field anomaly.
+- **Check downstream first if the user reports a dashboard issue.** The bad data might originate several tables upstream.
+- **Multiple alerts on the same table at the same time** usually have a single root cause.

package/bundled-skills/monte-carlo-analyze-root-cause/references/query-change-investigation.md

@@ -0,0 +1,55 @@
+# Query Change Investigation Playbook
+
+Use this when SQL modifications are suspected of causing a data issue.
+
+## Investigation steps
+
+### 1. Detect query changes
+
+Call `get_query_changes(mcons=[table_mcon], start_time=..., end_time=...)`:
+- Look at the time range around when the issue started
+- Compare old vs new SQL text — what changed?
+- Focus on: WHERE clauses, JOINs, GROUP BY, column selections, CTEs
+
+### 2. Correlate with the incident timeline
+
+Call `get_change_timeline` for a unified view:
+- Did the query change happen right before the anomaly?
+- Was there also a volume shift at the same time?
+- Were there ETL failures immediately after the query change?
+
+### 3. Understand the impact
+
+For each detected query change:
+- **Added/removed JOINs**: Can change cardinality (row count) dramatically
+- **Changed WHERE clause**: Can include/exclude different data subsets
+- **Modified GROUP BY**: Can change aggregation granularity
+- **New columns or removed columns**: Schema change
+- **Changed UNION**: Can add or remove entire data sources
+
+### 4. Trace to code changes
+
+**If GitHub MCP is available:**
+Search for PRs merged around the time of the query change. Look for:
+- dbt model modifications (`.sql` files in `models/`)
+- Stored procedure changes
+- ETL script updates
+- Configuration changes (e.g., different source tables)
+
+**If no GitHub MCP:**
+The `get_query_changes` output should include enough SQL diff information to understand what changed. Ask the user if they know who made the change.
+
+### 5. Verify the fix
+
+If the root cause is a bad query change:
+- Show the user the before/after SQL
+- Suggest reverting the change or fixing the query
+- If DB connector is available, run the old and new queries on a sample to compare outputs
+
+## Common patterns
+
+- **Accidental filter removal** — WHERE clause removed, producing more rows than expected
+- **JOIN type change** — INNER → LEFT JOIN introduces NULLs; LEFT → INNER drops rows
+- **Dedup logic change** — DISTINCT or ROW_NUMBER window changed, altering unique row count
+- **Source table swap** — query now reads from a different source table
+- **Aggregation change** — GROUP BY granularity changed, producing different row counts

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

@@ -0,0 +1,48 @@
+# Schema Investigation Playbook
+
+Use this when columns were added, removed, or had their types changed.
+
+## Investigation steps
+
+### 1. Identify what changed
+
+Call `get_table(mcon=table_mcon, include_fields=true)` to see the current schema.
+Compare against the alert details — what columns were added/removed/modified?
+
+### 2. Check for query changes
+
+Call `get_query_changes` — schema changes almost always come from ETL modifications:
+- New SELECT columns → column additions
+- Removed SELECT columns → column removals
+- CAST or type conversion changes → type modifications
+- CREATE TABLE AS SELECT with different schema
+
+### 3. Check downstream impact
+
+Call `get_asset_lineage(mcons=[table_mcon], direction="DOWNSTREAM")`:
+- Which downstream tables depend on the changed columns?
+- Call `get_field_lineage` to trace exactly which downstream fields are affected
+
+### 4. Check ETL pipeline
+
+Schema changes often happen during deployments:
+- Call `get_etl_issues` with `platform="dbt"` — dbt model changes are the most common source
+- Call `get_etl_issues` with `platform="airflow"` — pipeline deployment may have changed the schema
+- Check `get_change_timeline` for a correlated view
+
+### 5. Check for code changes
+
+If GitHub MCP is available, search for recent PRs that modified:
+- dbt models (`.sql` files in `models/`)
+- SQL migration scripts
+- Schema definition files
+
+If no GitHub MCP, `get_query_changes` will show the SQL modifications.
+
+## Common root causes
+
+- **dbt model change** — column added/removed in a model definition
+- **Migration script** — ALTER TABLE or CREATE TABLE AS SELECT with new schema
+- **Source schema change** — upstream system changed its schema, propagating downstream
+- **Type promotion** — implicit type coercion changed (e.g., INT → FLOAT)
+- **Column rename** — a column was renamed, breaking downstream references

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

@@ -0,0 +1,53 @@
+# Volume Investigation Playbook
+
+Use this when a table's row count changed unexpectedly (spike or drop).
+
+## Investigation steps
+
+### 1. Quantify the change
+
+Call `get_table_size_history` with the table's `full_table_id` and `resource_id`:
+- What was the row count before and after?
+- When exactly did the change occur?
+- Is this a sudden jump or a gradual trend?
+- Compare to the normal pattern (seasonality field may help)
+
+### 2. Check for query changes
+
+Call `get_query_changes` — did the ETL query change around the time of the volume shift?
+- New or removed WHERE clauses can dramatically change row counts
+- Changed JOINs (INNER → LEFT, or vice versa) affect output volume
+- Modified deduplication logic
+
+Call `get_change_timeline` for a unified view of all changes correlated with the volume shift.
+
+### 3. Check upstream volume
+
+Call `get_asset_lineage(mcons=[table_mcon], direction="UPSTREAM")` to find source tables.
+For each upstream table:
+- Call `get_table_size_history` — did the source data volume also change?
+- If upstream volume changed proportionally, the issue is in the source data, not this table's ETL
+
+### 4. Check for failed/futile queries
+
+Call `get_query_rca` with the table MCONs and a time range:
+- **Failed queries** with new error types may indicate broken inserts
+- **Futile queries** (ran but produced nothing) may explain missing rows
+- **QDR (query didn't run)** may explain why expected data wasn't loaded
+
+### 5. Profile the data (if DB connector available)
+
+If a database MCP server is connected:
+- Compare row counts by date partition: `SELECT date_col, COUNT(*) FROM table GROUP BY 1 ORDER BY 1`
+- Check for duplicate rows that appeared: `SELECT *, COUNT(*) FROM table GROUP BY ALL HAVING COUNT(*) > 1`
+- Check if specific segments grew/shrank: group by key dimensions
+- See `references/data-exploration.md` for more SQL patterns
+
+## Common root causes
+
+- **Source data volume change** — upstream system sent more/fewer records than usual
+- **Filter change** — ETL WHERE clause was modified, including/excluding different rows
+- **Dedup logic change** — deduplication rules changed, producing more or fewer unique rows
+- **Late-arriving data** — backfill or reprocessing loaded historical data
+- **Partition swap** — a full partition was replaced with different data
+- **Schema migration** — table was truncated and reloaded as part of a migration

package/bundled-skills/monte-carlo-asset-health/SKILL.md

@@ -9,6 +9,10 @@ date_added: 2026-07-01
 license: Apache-2.0
 license_source: https://github.com/monte-carlo-data/mc-agent-toolkit/blob/main/LICENSE
 ---
+## Bundled upstream support
+
+Supporting files are included at skill-relative paths. See [UPSTREAM-NOTICE.md](UPSTREAM-NOTICE.md) for their pinned sources, licenses, hashes, and import changes.
+
 ## When to Use
 
 - Use when the user goal matches this upstream workflow.

package/bundled-skills/monte-carlo-asset-health/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-asset-health/UPSTREAM-NOTICE.md

@@ -0,0 +1,12 @@
+# Upstream helpers for monte-carlo-asset-health
+
+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/workflows.md` | `skills/asset-health/references/workflows.md` | `9a37965124d9a82ca442cfddbbbade33f0e09fe8` | text-only trailing whitespace and EOF blank lines normalized |
+| `references/parameters.md` | `skills/asset-health/references/parameters.md` | `9e9f4b25dd08275433cafe67ae73b527e62bbda9` | text-only trailing whitespace and EOF blank lines normalized |

package/bundled-skills/monte-carlo-asset-health/references/parameters.md

@@ -0,0 +1,111 @@
+# MCP Parameter Notes
+
+Parameter details for the MCP tools used by the asset-health skill. Only covers
+the tools relevant to this skill's workflows.
+
+---
+
+## `get_alerts` — use snake_case parameters
+
+```
+created_after
+created_before
+order_by
+table_mcons
+statuses
+```
+
+Always provide `created_after` and `created_before`. Max window is 60 days.
+Pass ISO 8601 timestamps computed from the current date — e.g. for a 7-day
+window ending now: `created_after="2026-07-03T00:00:00Z"`,
+`created_before="2026-07-10T00:00:00Z"` (use the actual current date).
+
+When requesting active alerts, pass these three statuses:
+
+```
+statuses: ["NOT_ACKNOWLEDGED", "ACKNOWLEDGED", "WORK_IN_PROGRESS"]
+```
+
+Response field mapping for the alert table:
+- **Date** → `createdTime`
+- **Type** → `alert_types` (array, e.g., "Volume", "Metric anomaly", "Freshness")
+- **Priority** → `priority` (e.g., "P1", "P2", "P3")
+- **Status** → `status` (e.g., "Not acknowledged", "Acknowledged", "Work in progress")
+- **Link** → construct as `<MC_WEBAPP_URL>/alerts/<uuid>` where `MC_WEBAPP_URL`
+  comes from `get_mc_webapp_url()` (called in Phase 1). Display as bare URL.
+
+---
+
+## `search` — finding the right table identifier
+
+MC uses MCONs (Monte Carlo Object Names) as table identifiers. Always use
+`search` first to resolve a table name to its MCON before calling `get_table`,
+`get_asset_lineage`, or `get_alerts`.
+
+```
+search(query="orders_status") → returns mcon, full_table_id, warehouse, properties
+```
+
+The `properties` field contains tags (key-value pairs) associated with the asset.
+
+---
+
+## `get_table` — table metadata and stats
+
+Pass the MCON as: `mcon="<mcon>"` (single string, not an array).
+
+Key response fields used by this skill:
+- `last_updated_on` — timestamp of the most recent data update (for Last Updated metric)
+- `importance_score` — float 0-1 (for Importance in header)
+- `is_important` — boolean, true if key asset (for ⭐️ indicator)
+- `table_stats.avg_reads_per_active_day` — average reads per active day
+- `table_stats.avg_writes_per_active_day` — average writes per active day
+
+---
+
+## `get_monitors` — checking if monitors are paused
+
+When filtering by table, pass MCONs via the `mcons` parameter (not `table_mcons`).
+Check the `is_paused` field (boolean) on each monitor. Only count monitors where
+`is_paused` is false as active coverage.
+
+Response field mapping for the monitors table:
+- **Type** → `monitor_type` (e.g., "TABLE", "METRIC", "BULK_METRIC")
+- **Name** → `name` or `description`
+- **Incidents (7d)** → `seven_days_incident_count`
+- **Status** → derive from: `is_paused`, `next_execution_time`, `prev_execution_time`,
+  `seven_days_error_count`, `seven_days_timeout_count`
+  - If `is_paused` is true → "Paused"
+  - If `prev_execution_time` is null → "Never executed"
+  - If `seven_days_error_count` > 0 → "⚠️ N errors"
+  - Otherwise → "Running" (include schedule info from `next_execution_time` if available)
+
+---
+
+## `get_mc_webapp_url` — get Monte Carlo base URL
+
+Takes no arguments. Returns the regionalized base URL of the Monte Carlo web app
+(e.g., `https://getmontecarlo.com` — the actual value depends on the customer's
+environment). Call once in Phase 1 and store the result. Use it to construct all
+Monte Carlo links — never hardcode the base URL:
+- Assets/tables: `{result}/assets/{mcon}`
+- Alerts: `{result}/alerts/{alert_uuid}`
+
+---
+
+## `get_asset_lineage` — direction and edge interpretation
+
+Pass `direction` as `"UPSTREAM"` or `"DOWNSTREAM"` (uppercase).
+Pass `mcons` as an array even for a single asset: `mcons=["<mcon>"]`.
+
+Returns paginated edges (default 100 per page) where `source` and `target` are
+MCONs representing data flow direction: `source` feeds data into `target`.
+
+If `has_more` is true in the response, follow pagination using `next_offset` to
+get remaining edges. For upstream health checks, all parents must be discovered
+before Phase 3 can run — do not skip pages.
+
+For an **UPSTREAM** query on asset X:
+- Edges have `source = <upstream_parent>`, `target = X` (or intermediate nodes)
+- Extract unique MCONs from the `source` field to get the upstream parents
+- Exclude the queried asset's own MCON from the parent list