opencode-skills-collection 4.1.14 → 4.1.16

package/bundled-skills/monte-carlo-remediation/references/safety.md

@@ -0,0 +1,160 @@
+# Safety Rails
+
+Detailed safety protocols for the remediation skill. These rules are non-negotiable — they apply in every remediation scenario, regardless of severity or urgency.
+
+## Core principles
+
+1. **Investigate before acting.** Never propose a fix without completing the investigation workflow.
+2. **Explain before executing.** Never run a remediation action without telling the user what you're about to do and why.
+3. **Confirm before destroying.** Any action that modifies data, restarts a pipeline, or changes configuration requires explicit user confirmation.
+4. **One step at a time.** Execute one remediation action, verify it, then decide on the next step.
+5. **Document everything.** Record all findings and actions on the alert.
+6. **Escalate when uncertain.** A clear "I don't know" is safer than a confident wrong fix.
+
+## Confirmation protocol
+
+### Actions that ALWAYS require confirmation
+
+These actions must not be executed without the user explicitly saying "yes", "go ahead", "proceed", or similar:
+
+- **Pipeline triggers:** Starting DAG runs, triggering dbt jobs, launching pipeline executions
+- **Data modifications:** Any SQL that includes INSERT, UPDATE, DELETE, DROP, ALTER, TRUNCATE
+- **Configuration changes:** Modifying pipeline parameters, changing schedules, updating credentials
+- **Code changes:** Creating PRs, committing code, merging branches
+- **Incident escalation:** Paging on-call via PagerDuty, creating high-severity incidents
+- **Alert status changes:** Marking alerts as FIXED, EXPECTED, or NO_ACTION_NEEDED
+
+### Actions that do NOT require confirmation
+
+These are safe to execute without asking:
+
+- **Read-only investigation:** All Monte Carlo investigation tools (getAlerts, getTable, getAssetLineage, etc.)
+- **Adding comments:** `createOrUpdateAlertComment` — documenting findings is always safe
+- **Acknowledging alerts:** `updateAlert(status="ACKNOWLEDGED")` — this just signals awareness
+- **Setting ownership:** `setAlertOwner` — assigning someone to look at it
+- **Sending non-urgent notifications:** Posting informational messages to Slack channels (not paging)
+- **Status updates:** `updateAlert(status="WORK_IN_PROGRESS")` — tracking progress
+
+### How to ask for confirmation
+
+Present the action clearly and wait for an explicit response:
+
+> "I'd like to trigger a rerun of the Airflow DAG `etl_orders_daily`. This will:
+> - Start a new run of all tasks in the DAG
+> - Expected duration: ~45 minutes based on recent runs
+> - Risk: minimal — this is a standard rerun, not a backfill
+>
+> Should I proceed?"
+
+**Do NOT proceed on ambiguous responses.** "Maybe", "I guess", "hmm" are not confirmation. Ask again clearly: "Just to confirm — should I trigger the DAG rerun? (yes/no)"
+
+## Destructive operation handling
+
+### Definition
+
+A "destructive operation" is any action that:
+- Deletes or modifies existing data
+- Cannot be easily undone
+- Affects multiple systems or tables
+- Changes infrastructure or configuration
+
+### Required protocol for destructive operations
+
+1. **State the action explicitly:** "I want to execute: `DELETE FROM orders WHERE created_at < '2024-01-01'`"
+2. **Explain the impact:** "This will remove approximately 1.2M rows from the `orders` table"
+3. **Describe the rollback plan:** "If this causes issues, the data can be restored from the daily backup at s3://backups/orders/2024-01-15/"
+4. **Wait for explicit confirmation**
+5. **Execute the action**
+6. **Immediately verify the result**
+7. **Document what was done**
+
+### Actions that are NEVER automated
+
+Even with user confirmation, suggest these be done manually rather than by the agent:
+
+- Dropping tables or databases
+- Modifying production credentials or secrets
+- Changing IAM roles or permissions
+- Directly modifying production infrastructure (scaling, networking)
+- Running backfill operations that span more than 7 days of data
+
+For these, provide the exact commands and let the user execute them.
+
+## Escalation criteria
+
+### When to stop and ask the user for direction
+
+Present your findings and ask the user how to proceed when ANY of these conditions are true:
+
+1. **No clear root cause:** TSA failed or returned ambiguous results, and your manual investigation didn't identify a clear cause.
+
+2. **Multiple simultaneous alerts:** More than 3 alerts firing on related tables suggests a systemic issue that needs human judgment.
+
+3. **High blast radius + uncertain fix:** The affected table has >10 downstream consumers AND you're not confident the fix will work.
+
+4. **Data loss detected:** Any sign that data has been permanently deleted or corrupted. Do not attempt to fix data loss — stop and tell the user immediately.
+
+5. **Permission or access issues:** The root cause involves permissions, credentials, or access controls. These require human intervention.
+
+6. **Cross-system failure:** The issue spans multiple systems (e.g., ingestion + transformation + serving) and no single fix addresses it.
+
+7. **Recurring incident:** The same alert has fired 3+ times in the past week. The underlying issue needs a permanent fix, not another band-aid.
+
+8. **Production safety concern:** Any situation where the proposed fix could make things worse, even with a rollback plan.
+
+### How to hand off to the user
+
+1. **Present your findings clearly:** Summarize what you investigated, what you found, and why you're not confident in an automated fix.
+
+2. **Document on the alert:**
+   ```
+   createOrUpdateAlertComment(
+     alert_id="<alert_uuid>",
+     comment="## Investigation Summary\n\n**Findings:** [full summary]\n**Why automated remediation was not attempted:** [reason]\n**Recommended next steps:**\n1. [specific step]\n2. [specific step]"
+   )
+   ```
+
+3. **Set status to WORK_IN_PROGRESS:**
+   ```
+   updateAlert(alert_id="<alert_uuid>", status="WORK_IN_PROGRESS")
+   ```
+
+4. **Ask the user for next steps:** They may want to notify their team, page on-call, investigate further, or take a manual action you can assist with.
+
+## What "uncertain" means in practice
+
+You should consider yourself "uncertain" and ask the user for direction when:
+
+- You can identify multiple plausible root causes and can't narrow it down
+- The TSA summary says one thing but your manual investigation suggests something different
+- The proposed fix addresses a symptom but not necessarily the root cause
+- You've never seen this pattern before in the reference examples
+- The fix requires making an assumption about the system that you can't verify
+- The user seems uncertain or is asking "are you sure?" — respect their caution
+
+**When in doubt, state your confidence level:**
+
+**Example:**
+> "I'm moderately confident (60-70%) that the root cause is [X], based on [evidence]. However, [alternative explanation] is also possible. I'd recommend [safer action] first. If that doesn't resolve it, the data platform team may need to investigate further. How would you like to proceed?"
+
+## Rollback planning
+
+Before executing any remediation action, have a rollback plan:
+
+### For pipeline restarts
+- **Rollback:** If the rerun produces bad data, the previous good state is usually available in the warehouse's time travel / versioning feature. Note the timestamp before triggering.
+
+### For dbt reruns
+- **Rollback:** dbt models can be rebuilt from source. If a rerun produces bad results, fix the model and rerun again. For incremental models, note the last successful run timestamp.
+
+### For code changes (PRs)
+- **Rollback:** Revert the PR. Always create changes as PRs (not direct commits) so they can be cleanly reverted.
+
+### For data modifications
+- **Rollback:** Before any data modification, recommend the user:
+  1. Create a backup: `CREATE TABLE backup_<table>_<timestamp> AS SELECT * FROM <table>`
+  2. Or verify that time travel / snapshots are available for recovery
+  3. Document the rollback command alongside the modification
+
+### For configuration changes
+- **Rollback:** Document the previous configuration value before changing it. If available, use version-controlled configuration.

package/bundled-skills/monte-carlo-remediation/references/tool-discovery.md

@@ -0,0 +1,172 @@
+# Tool Discovery at Runtime
+
+This reference explains how to discover what remediation tools are available to you at runtime. You have three categories of tools to check: MCP servers, CLI tools (via shell access), and APIs (via `curl` or language-specific clients). Check all three before deciding what's possible.
+
+## Category 1: MCP servers
+
+In Claude Code and other MCP-capable editors, MCP tools follow the naming convention:
+
+```
+mcp__<server_name>__<tool_name>
+```
+
+For example:
+- `mcp__airflow__trigger_dag_run` — an Airflow MCP tool
+- `mcp__dbt_cloud__trigger_run` — a dbt Cloud MCP tool
+- `mcp__github__create_pull_request` — a GitHub MCP tool
+
+Monte Carlo's own tools are bundled by this plugin and namespaced under the plugin server — see the **Monte Carlo tool routing** block at the top of the skill. Examples:
+- `mcp__plugin_mc-agent-toolkit_monte-carlo-mcp__get_alerts`
+- `mcp__plugin_mc-agent-toolkit_monte-carlo-mcp__search`
+
+Scan your tool list for any `mcp__*__*` patterns and group by server name.
+
+## Category 2: CLI tools
+
+You have shell access. Many remediation actions can be done via CLI tools that may already be installed:
+
+| CLI Tool | Capability | Example Commands |
+| -------- | ---------- | ---------------- |
+| `gh` | GitHub operations | `gh pr create`, `gh issue create`, `gh api` |
+| `git` | Code changes | `git checkout -b fix/...`, `git commit`, `git push` |
+| `dbt` | dbt operations | `dbt run --select <model>`, `dbt test`, `dbt retry` |
+| `airflow` | Airflow operations | `airflow dags trigger <dag_id>`, `airflow tasks run` |
+| `montecarlo` | Monte Carlo CLI | `montecarlo monitors apply`, `montecarlo collectors test-connection` |
+| `curl` | Any HTTP API | Call REST APIs directly for any service with an API |
+| `snowsql` / `bq` / `databricks` | Warehouse CLIs | Execute SQL queries, check table state |
+
+**Check availability** by running `which <tool>` or `<tool> --version` before using a CLI tool.
+
+## Category 3: APIs (via curl or HTTP)
+
+If neither an MCP server nor a CLI tool is available for a service, you can often call its REST API directly using `curl`. This is the most flexible option — any service with an API is reachable.
+
+Examples:
+```
+# Trigger an Airflow DAG via REST API
+curl -X POST "https://airflow.example.com/api/v1/dags/<dag_id>/dagRuns" \
+  -H "Authorization: Bearer $AIRFLOW_TOKEN" \
+  -H "Content-Type: application/json" \
+  -d '{"conf": {}}'
+
+# Trigger a dbt Cloud job via REST API
+curl -X POST "https://cloud.getdbt.com/api/v2/accounts/<account_id>/jobs/<job_id>/run/" \
+  -H "Authorization: Token $DBT_CLOUD_TOKEN" \
+  -H "Content-Type: application/json" \
+  -d '{"cause": "Triggered by remediation skill"}'
+```
+
+**Note:** API calls require credentials. If you don't have the right tokens or environment variables, ask the user — don't guess at authentication.
+
+## Discovery procedure
+
+### Step 1: Check MCP servers
+
+Scan your tool list for `mcp__*__*` patterns. Common MCP servers relevant to remediation:
+
+| Server Name Pattern | Capability |
+| ------------------- | ---------- |
+| `*airflow*` | Pipeline orchestration — trigger DAG runs, retry failed tasks |
+| `*dagster*` | Pipeline orchestration — launch runs, check status |
+| `*prefect*` | Pipeline orchestration — create flow runs, check status |
+| `*dbt*` | dbt operations — trigger job runs, get status, list jobs |
+| `*github*` | Code changes — create PRs, issues, branches |
+| `*gitlab*` | Code changes — create merge requests, issues |
+| `*snowflake*` | Warehouse access — execute queries, get table info |
+| `*bigquery*` | Warehouse access — execute queries, get table info |
+| `*databricks*` | Warehouse access + orchestration — queries, trigger jobs |
+| `*fivetran*` | Ingestion — trigger connector sync, check status |
+| `*jira*` | Issue tracking — create issues, update status |
+
+### Step 2: Check CLI tools
+
+For any capability not covered by MCP, check if a relevant CLI tool is available. The most common:
+
+- `gh` — covers GitHub operations (PRs, issues, API calls) without needing a GitHub MCP
+- `dbt` — covers dbt operations (run, test, retry) without needing a dbt Cloud MCP
+- `git` — always available for code changes
+- `curl` — always available for calling any REST API
+
+### Step 3: Assess coverage
+
+For the current remediation task, determine:
+
+1. **Can I investigate?** — Monte Carlo MCP is always needed. If it's not connected, you cannot proceed.
+2. **Can I execute the fix?** — Check MCP servers first, then CLI tools, then API access.
+
+### Step 4: Report capabilities
+
+Present what you found to the user before proceeding:
+
+> "For this remediation, I can:
+> - ✅ Investigate the issue (Monte Carlo MCP)
+> - ✅ Restart the Airflow DAG (Airflow MCP connected)
+> - ✅ Create a code fix (`gh` CLI available — no GitHub MCP needed)
+> - ❌ Rerun the dbt job (no dbt Cloud MCP or `dbt` CLI found)"
+
+## Graceful degradation
+
+When no tool (MCP, CLI, or API) is available for a needed action:
+
+### Priority 1: Provide actionable instructions
+
+Give the user the exact commands or steps to execute themselves:
+
+```
+# If no Airflow tool is available but you identified the DAG:
+"The DAG `etl_orders_daily` needs to be triggered. Run:
+  airflow dags trigger etl_orders_daily
+Or via the Airflow UI: navigate to DAGs → etl_orders_daily → Trigger DAG"
+
+# If no dbt tool is available:
+"dbt model `stg_orders` needs to be rebuilt. Run:
+  dbt run --select stg_orders+
+Or via dbt Cloud UI: Jobs → Daily Transform → Run Now"
+
+# If no GitHub tool is available:
+"File `models/staging/stg_orders.sql` needs line 14 changed from
+  `user_id` to `customer_id`. Create a branch and PR with this change."
+```
+
+### Priority 2: Present findings and ask for next steps
+
+Tell the user what you found, what the fix is, and ask how they'd like to proceed. They may run the commands themselves, notify their team, or take a different approach.
+
+### Priority 3: Document on the alert
+
+Always, regardless of what other tools are available:
+
+```
+createOrUpdateAlertComment(
+  alert_id="<alert_uuid>",
+  comment="## Remediation Plan\n\n**Root cause:** [summary]\n**Required action:** [specific fix]\n**Manual steps:**\n1. [step]\n2. [step]\n\n**Investigated by:** AI agent via remediation skill"
+)
+```
+
+## Tool-specific notes
+
+### Airflow
+
+**MCP tools:** `trigger_dag_run`, `get_dag_runs`, `get_task_instances`, `clear_task_instances`
+**CLI:** `airflow dags trigger <dag_id>`, `airflow tasks run <dag_id> <task_id> <execution_date>`
+**API:** `POST /api/v1/dags/<dag_id>/dagRuns`
+
+**Caution:** `trigger_dag_run` starts a NEW run. If the issue was a failed task in an existing run, `clear_task_instances` (retry) may be more appropriate than starting fresh.
+
+### dbt
+
+**MCP tools:** `trigger_run` / `trigger_job`, `get_run`, `list_jobs`, `cancel_run`
+**CLI:** `dbt run --select <model>`, `dbt retry`, `dbt test --select <model>`
+**API:** `POST /api/v2/accounts/<id>/jobs/<id>/run/`
+
+**Note:** dbt Cloud jobs often include multiple models. Triggering a job reruns ALL models in that job, not just the failed one. The `dbt` CLI with `--select` gives more granular control.
+
+### GitHub
+
+**MCP tools:** `create_pull_request`, `create_issue`, `create_or_update_file`, `create_branch`
+**CLI:** `gh pr create`, `gh issue create`, `gh api`
+**Git:** `git checkout -b`, `git commit`, `git push`
+
+The `gh` CLI is often the most practical option — it doesn't require a GitHub MCP server and supports the full GitHub API via `gh api`.
+
+**Best practice:** For code fixes, create a branch → make the change → open a PR. Don't push directly to main.

package/bundled-skills/monte-carlo-storage-cost-analysis/SKILL.md

@@ -9,6 +9,9 @@ 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.
 
 # Monte Carlo Storage Cost Analysis Skill
 

package/bundled-skills/monte-carlo-storage-cost-analysis/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-storage-cost-analysis/UPSTREAM-NOTICE.md

@@ -0,0 +1,11 @@
+# Upstream helpers for monte-carlo-storage-cost-analysis
+
+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/output-structure.md` | `skills/storage-cost-analysis/references/output-structure.md` | `db0f8db1be9a2271271d664d21eef1dc9cff17a3` | text-only trailing whitespace and EOF blank lines normalized |

package/bundled-skills/monte-carlo-storage-cost-analysis/references/output-structure.md

@@ -0,0 +1,93 @@
+# `analyze_storage_costs` Output Structure
+
+The `analyze_storage_costs` MCP tool returns a single formatted string containing two machine-readable regions. The skill treats these regions as a contract — always preserve them verbatim when copying.
+
+## Regions
+
+### `<!-- PRESENT_AS_IS -->` ... `<!-- /PRESENT_AS_IS -->`
+
+A condensed summary block containing:
+
+- Warehouse name and totals (candidate count, total candidate bytes)
+- Safety-tier summary
+- A Top-N table of the largest candidates across all categories (default N = 30)
+- A drill-down prompt listing the available categories
+
+**Present this block verbatim as the initial response.** Do not paraphrase, re-order columns, drop rows, or strip the HTML comment markers. The markers are load-bearing: removing them breaks the drill-down flow downstream.
+
+### `<!-- CATEGORY_DETAILS -->` ... `<!-- /CATEGORY_DETAILS -->`
+
+Contains per-category sections wrapped in `<!-- CATEGORY:<key> -->` ... `<!-- /CATEGORY:<key> -->` markers. One section per category.
+
+**Do NOT present this block on the initial response.** Hold it for drill-down requests.
+
+## Category keys and keyword mapping
+
+| Key | User phrases that map to it |
+|-----|-----------------------------|
+| `temporary` | "temporary", "staging", "tmp", "stg", "test tables" |
+| `archive_snapshot` | "archive", "snapshot", "backup", "old", "historical" |
+| `other` | "uncategorized", "other", "unknown", "misc" |
+| `production` | "production", "prod", "critical", "important", "monitored" |
+
+"Show me everything" / "all categories" → present each section in order: `temporary` → `archive_snapshot` → `other` → `production`.
+
+## Drill-down rule
+
+When the user asks about a category, find the matching `<!-- CATEGORY:<key> -->` section in the `analyze_storage_costs` result already present in the conversation history and present its content verbatim. **Never re-invoke `analyze_storage_costs` for a drill-down** — the data is already there and re-fetching wastes turns.
+
+## Column layout
+
+Each per-category and Top-N table has this column order:
+
+```
+Table | Category | Type | Size | [$/mo] | Pattern | Usage & Risk
+```
+
+`$/mo` appears only for Snowflake warehouses.
+
+## The Usage & Risk column
+
+The trailing `Usage & Risk` column merges read-side activity with risk flags into a single cell:
+
+```
+{activity}                          # when no flags fire
+{activity}; {flag1, flag2, ...}     # when one or more flags fire
+```
+
+**Activity values** (always present):
+
+| Value | Meaning |
+|-------|---------|
+| `No reads` | No recorded reads |
+| `180d · 0 reads` | Last read N days ago, zero total reads |
+| `2d · 580 reads / 14 users` | Recent reads, total reads, distinct reading users |
+
+A low `days since read` is only meaningful alongside reads + users — a single backup job or security scanner is enough to reset the "last read" clock on a cold table. Interpret staleness against the full activity.
+
+**Risk flags** (appended after `; ` in this fixed order when any fire):
+
+| Flag | Meaning |
+|------|---------|
+| `high criticality` / `medium criticality` | Pre-computed criticality label. `low` is omitted. |
+| `N consumers` | Count of ALL consumers — other tables/views AND BI dashboards or non-table assets |
+| `high importance score` | `is_important == true`, which means `importance_score >= 0.6`. A computed signal from the Databricks key-table-scores job, **not** a user-applied tag. |
+| `has monitors` | Actively monitored by Monte Carlo |
+
+The `N consumers` flag counts more than the lineage tool returns: `get_asset_lineage` only yields table-to-table edges, so BI dashboards and other consumer types are included in `N consumers` but won't appear in lineage results. When the user runs a lineage check and sees fewer downstream tables than `N consumers` implied, explain the gap — the missing consumers are likely dashboards or external tools.
+
+## MCON links
+
+MCONs in the pre-formatted tables are rendered as markdown links:
+
+```
+[`db:schema.table`](https://getmontecarlo.com/assets/MCON++<account>++<resource>++<type>++<id>)
+```
+
+Preserve the full link when copying. Never output the bare MCON string as plain text — the UI depends on the link for navigation, and the skill contract forbids surfacing raw internal identifiers.
+
+## Errors and empty results
+
+- Tool returns an error → report it to the user and stop.
+- Tool returns "No optimization candidates found..." → relay the message and stop.
+- Tool returns a warehouse picker list → let the user choose, then call the tool again with the chosen `warehouse_id`.

package/bundled-skills/mtls-configuration/SKILL.md

@@ -20,7 +20,6 @@ Comprehensive guide to implementing mutual TLS for zero-trust service mesh commu
 - Clarify goals, constraints, and required inputs.
 - Apply relevant best practices and validate outcomes.
 - Provide actionable steps and verification.
-- If detailed examples are required, open `resources/implementation-playbook.md`.
 
 ## Use this skill when