opencode-skills-collection 4.1.14 → 4.1.16

package/bundled-skills/arrowspace/SKILL.md

@@ -30,7 +30,7 @@ Spectral vector search that augments nearest-neighbour search with graph Laplaci
 ### Step 1: Install and import
 
 ```bash
-pip install arrowspace
+python3 -m pip install "arrowspace==0.28.1" numpy  # review/pin remaining dependencies in an isolated environment
 ```
 
 ```python
@@ -43,17 +43,16 @@ import numpy as np
 Pass an (N, d) float64 NumPy array of embedding vectors:
 
 ```python
-items = np.array([[0.1, 0.2, 0.3],
-                  [0.0, 0.5, 0.1],
-                  [0.9, 0.1, 0.0]], dtype=np.float64)
+rng = np.random.default_rng(7)
+items = rng.normal(size=(32, 8)).astype(np.float64)
+items /= np.linalg.norm(items, axis=1, keepdims=True)
 ```
 
 ### Step 3: Configure graph parameters
 
 ```python
-graph_params = {"eps": 0.2, "k": 6, "topk": 3, "p": 2.0, "sigma": 1.0}
-builder = ArrowSpaceBuilder(items, graph_params=graph_params)
-aspace = builder.build()
+graph_params = {"eps": 0.5, "k": 6, "topk": 3, "p": 2.0, "sigma": None}
+aspace, graph = ArrowSpaceBuilder().build(graph_params, items)
 ```
 
 ### Step 4: Query
@@ -63,18 +62,19 @@ lambdas = aspace.lambdas()           # array indexed by insertion order
 sorted_res = aspace.lambdas_sorted()  # (score, index) pairs ascending
 ```
 
-Higher λτ values indicate items that are both semantically close and structurally central.
+These are per-item spectral signatures, not graph eigenvalues or query-dependent relevance scores. Sorting them alone is not nearest-neighbor retrieval; do not infer closeness to a query or graph centrality from a large signature.
 
 ## Examples
 
 ### Example 1: Basic spectral retrieval
 
 ```python
-items = np.random.randn(100, 64).astype(np.float64)
-builder = ArrowSpaceBuilder(items, graph_params={"eps": 0.5, "k": 10, "topk": 5, "p": 2.0, "sigma": None})
-aspace = builder.build()
-scores = aspace.lambdas()
-top_indices = np.argsort(scores)[-5:]
+# Reuse the normalized corpus and graph above; verify degenerate scores first.
+if np.any(np.abs(aspace.lambdas()) < 1e-12):
+    raise ValueError("Tune graph parameters for this corpus before searching")
+query = items[0].copy()
+hits = aspace.search(query, graph, tau=0.7, k=5)
+# hits contains query-dependent (item_index, score) pairs, not a lambda-only ranking.
 ```
 
 ### Example 2: Compare spectral vs cosine ranking
@@ -82,28 +82,30 @@ top_indices = np.argsort(scores)[-5:]
 ```python
 from sklearn.metrics.pairwise import cosine_similarity
 cos_sim = cosine_similarity(items)
-cosine_order = np.argsort(cos_sim[0])[::-1]
-spectral_order = np.argsort(aspace.lambdas())[::-1]
+cosine_order = np.argsort(cos_sim[0])[::-1][:5]
+spectral_order = [index for index, score in aspace.search(items[0], graph, tau=0.7, k=5)]
+# For retrieval evaluation, exclude self-matches and use held-out relevance labels.
 ```
 
 ## Best Practices
 
 - ✅ Normalise embeddings to unit norm before passing to ArrowSpace
-- ✅ Start with eps proportional to 1/sqrt(dim) and tune from there
-- ✅ Use k between 3 and 25 depending on dataset size (rule: N/50)
-- ✅ Set sigma=None to auto-select kernel width from distance distribution
-- ❌ Don't use with fewer than 10 items (graph structure is not meaningful)
+- ✅ Treat graph parameters as corpus-dependent; inspect disconnected/degenerate scores and tune using an explicitly selected objective
+- ✅ Choose k relative to the actual corpus and library constraints; N/50 is not a universal quality guarantee
+- ✅ In the reviewed 0.28 API, sigma=None uses the eps-dependent default; it is not automatic distribution fitting
+- ✅ Small corpora can illustrate the API, but retrieval quality requires corpus-appropriate evaluation; ten items is not a mathematical validity threshold
 - ❌ Don't use for real-time streaming data (ArrowSpace is batch-oriented)
 
 ## Limitations
 
-- This skill does not replace environment-specific validation, testing, or expert review.
+- API examples target the reviewed 0.28 interface; [immutable upstream skill](https://github.com/Genefold/arrowspace-skills/blob/8d9e8e30be314292e2ee60b84f0c163963660d41/SKILL.md) documents the builder, graph return value and query-aware search. These examples were checked against source documentation, not executed here.
+- Fit graph parameters and tau on held-out retrieval evidence; λτ signatures alone do not prove better recall or structural importance.
 - ArrowSpace is batch-oriented and not designed for real-time indexing of streaming data.
 
 ## Common Pitfalls
 
 - **Problem:** eps is too small, producing a disconnected graph
-  **Solution:** Increase eps, or set it proportional to 1/sqrt(embedding_dim)
+  **Solution:** Inspect graph connectivity and degenerate scores, then tune eps against the actual data; no dimension-only formula is guaranteed
 
 - **Problem:** k is too large, producing a dense graph with washed-out spectral features
   **Solution:** Keep k ≤ 25 for most datasets

package/bundled-skills/ask-questions-if-underspecified/SKILL.md

@@ -31,7 +31,7 @@ Treat a request as underspecified if after exploring how to perform the work, so
 - Identify environment (language/runtime versions, OS, build/test runner)
 - Clarify safety/reversibility (data migration, rollout/rollback, risk)
 
-If multiple plausible interpretations exist, assume it is underspecified.
+Multiple interpretations justify a question only when they materially change the outcome or risk; resolve routine reversible details from the existing context.
 
 ### 2) Ask must-have questions first (keep it small)
 
@@ -52,9 +52,9 @@ Until must-have answers arrive:
 - Do not run commands, edit files, or produce a detailed plan that depends on unknowns
 - Do perform a clearly labeled, low-risk discovery step only if it does not commit you to a direction (e.g., inspect repo structure, read relevant config files)
 
-If the user explicitly asks you to proceed without answers:
-- State your assumptions as a short numbered list
-- Ask for confirmation; proceed only after they confirm or correct them
+If the user explicitly authorizes proceeding with reasonable assumptions:
+- State the assumptions briefly and continue within that authorized scope; do not ask for the same confirmation again.
+- Keep only genuinely missing consequential authorization or indispensable inputs pending, while completing independent safe work.
 
 ### 4) Confirm interpretation, then proceed
 

package/bundled-skills/audit-logging/SKILL.md

@@ -10,8 +10,8 @@ source_type: community
 date_added: '2026-09-20'
 license: MIT
 license_source: https://github.com/BagelHole/DevOps-Security-Agent-Skills/blob/main/LICENSE
-compatibility: Checklist and framework guidance; no privileged tooling required. Apply
-  controls through your own change process.
+compatibility: Linux infrastructure examples require the matching logging services and
+  authorized administrator access. Application examples require a writable approved log destination.
 metadata:
   author: devops-skills
   version: '1.0'
@@ -26,7 +26,7 @@ Implement comprehensive audit logging for compliance, security monitoring, and f
 - Setting up centralized logging for compliance frameworks (SOC 2, HIPAA, PCI DSS)
 - Implementing security event monitoring and alerting
 - Building audit trails for regulatory requirements
-- Configuring log retention and tamper-proof storage
+- Configuring log retention and integrity-protected storage
 - Integrating application logs with SIEM platforms
 
 ## Log Categories
@@ -161,10 +161,10 @@ from datetime import datetime, timezone
 from functools import wraps
 
 class AuditLogger:
-    def __init__(self, service_name, logger_name="audit"):
+    def __init__(self, service_name, log_path, logger_name="audit"):
         self.service = service_name
         self.logger = logging.getLogger(logger_name)
-        handler = logging.FileHandler("/var/log/app/audit.log")
+        handler = logging.FileHandler(log_path)
         handler.setFormatter(logging.Formatter("%(message)s"))
         self.logger.addHandler(handler)
         self.logger.setLevel(logging.INFO)
@@ -239,7 +239,7 @@ def audit_trail(audit_logger, resource_name):
                     resource=resource_name,
                     action=func.__name__,
                     result="failure",
-                    metadata={"error": str(e)},
+                    metadata={"error_code": "operation_failed"},
                 )
                 raise
         return wrapper
@@ -337,80 +337,13 @@ def audit_trail(audit_logger, resource_name):
 }
 ```
 
-## Retention Policy by Compliance Framework
+## Retention and integrity requirements
 
-```yaml
-retention_requirements:
-  soc2:
-    minimum: 1 year
-    recommended: 3 years
-    notes: "Based on audit period and report requirements"
-
-  hipaa:
-    minimum: 6 years
-    notes: "From date of creation or last effective date"
-
-  pci_dss:
-    minimum: 1 year
-    immediately_available: 3 months
-    notes: "Req 10.7 - retain for at least one year, 3 months immediately available"
-
-  gdpr:
-    minimum: "As long as necessary for processing purpose"
-    notes: "Apply data minimization; delete when no longer needed"
-
-  fedramp:
-    minimum: 3 years
-    notes: "AU-11 control requirement"
-
-  iso27001:
-    minimum: "Defined by organization policy"
-    recommended: 3 years
-    notes: "A.12.4.1 - retention period must be defined"
-```
-
-## Log Integrity Verification Script
-
-```bash
-#!/usr/bin/env bash
-# verify-log-integrity.sh - Verify log file checksums against stored hashes
-
-LOG_DIR="/var/log/app"
-HASH_FILE="/var/log/app/.checksums"
-ALERT_WEBHOOK="${ALERT_WEBHOOK_URL}"
-
-verify_logs() {
-  local failures=0
-  while IFS='  ' read -r stored_hash filename; do
-    if [ -f "$filename" ]; then
-      current_hash=$(sha256sum "$filename" | awk '{print $1}')
-      if [ "$stored_hash" != "$current_hash" ]; then
-        echo "TAMPER DETECTED: $filename"
-        failures=$((failures + 1))
-        curl -s -X POST "$ALERT_WEBHOOK" \
-          -H "Content-Type: application/json" \
-          -d "{\"text\":\"ALERT: Audit log tamper detected on $(hostname): $filename\"}"
-      fi
-    else
-      echo "MISSING: $filename"
-      failures=$((failures + 1))
-    fi
-  done < "$HASH_FILE"
-
-  return $failures
-}
+Define a retention register with framework/version, applicable control, data type, purpose, jurisdiction, legal hold, owner, approved period and authoritative evidence. Do not apply a single framework duration to every log type; documentation-retention obligations and operational-log retention differ. Obtain qualified review of legal and contractual requirements before applying deletion or export policies. The 365-day infrastructure examples are capacity-policy illustrations, not minimum compliance requirements.
 
-update_checksums() {
-  find "$LOG_DIR" -name "*.log" -type f -exec sha256sum {} \; > "$HASH_FILE"
-  chmod 440 "$HASH_FILE"
-}
+Checksums and the illustrative in-process hash chain detect some changes only when compared with a separately protected trusted checkpoint. They do not make storage immutable, survive restart without persistence, prevent a privileged actor rewriting both log and hashes, or establish regulatory compliance. Use independently protected append-only storage, authenticated checkpoints and restoration tests appropriate to the threat model.
 
-case "${1:-verify}" in
-  verify)  verify_logs ;;
-  update)  update_checksums ;;
-  *)       echo "Usage: $0 {verify|update}" ;;
-esac
-```
+For local verification, use a project-reviewed manifest with a fixed approved directory, reject traversal/symlinks and missing files, and report failures locally. Do not automatically regenerate the trusted baseline after failure. Uploading audit logs, enabling forwarding and sending webhook alerts require explicit destination/data authorization; no notification is sent by this guide itself.
 
 ## SIEM Integration Checklist
 

package/bundled-skills/automated-triage/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 Automated Triage
 

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

@@ -0,0 +1,12 @@
+# Upstream helpers for automated-triage
+
+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/triage-stages.md` | `skills/automated-triage/references/triage-stages.md` | `0432f8e5a40db4af4ff1f79d1df6d53df5b806e4` | text-only trailing whitespace and EOF blank lines normalized |
+| `references/triage-example.md` | `skills/automated-triage/references/triage-example.md` | `e18c39fd7cd6af2f24c76e93687dddb62eb47a95` | text-only trailing whitespace and EOF blank lines normalized |

package/bundled-skills/automated-triage/references/triage-example.md

@@ -0,0 +1,115 @@
+# Triage Example Workflow
+
+This is a complete triage workflow that supports two modes:
+
+- **Recommendation mode** — runs the full investigation and tells you what it would do, without writing anything to your environment. Use this while tuning your triage prompt.
+- **Action mode** — runs the full workflow and applies actions (comments, status updates) for real.
+
+Run in recommendation mode first. Once the classifications and recommendations match how your team would respond manually, switch to action mode.
+
+---
+
+## What this workflow does
+
+1. Asks whether to run in recommendation or action mode
+2. Fetches all alerts from the last 3 hours
+3. Scores every alert by incident likelihood and potential impact (in parallel)
+4. Fires deep troubleshooting on all high-signal alerts simultaneously, classifying each as results arrive
+5. In **action mode**: posts a triage comment on every alert and updates statuses
+   In **recommendation mode**: outputs what it would comment and what status it would set — no writes
+
+---
+
+## Procedure
+
+### Step 1: Choose mode
+
+Ask: "Run in **recommendation mode** (no writes — I'll show you what actions would be taken) or **action mode** (comments and status updates applied for real)?"
+
+Also ask: "Run all stages **straight through**, or **step by step** — pausing after each stage to show results before continuing?"
+
+Wait for both answers before proceeding. In step-by-step mode, after each stage completes, summarise what it produced, proactively suggest alternatives or adjustments based on what you observed, and wait for confirmation before moving to the next.
+
+### Step 2: Fetch alerts
+
+Call `get_alerts` for the last 3 hours.
+
+If no alerts are returned, report: "No alerts in the last 3 hours." and stop.
+
+### Step 3: Score each alert
+
+Call `alert_assessment` in parallel for every alert from step 2, in batches of up to 10 at a time. Each result includes `incident_likelihood`, `alert_impact` (HIGH/MEDIUM/LOW each), `alert_description` (plain-language description of what happened in the incident), and `triage_summary` (the key reasoning behind the incident likelihood and potential impact scores). Use `alert_description` and `triage_summary` to inform the triage comment in step 4 for alerts that don't go through troubleshooting.
+
+### Step 4: Troubleshoot and classify high-signal alerts
+
+For each alert where BOTH `incident_likelihood` AND `alert_impact` are MEDIUM or HIGH, call `run_troubleshooting_agent` (default `async_mode=True`). Fire all eligible alerts simultaneously — each call returns immediately with one of: `success` (previous results available immediately), `queued` (accepted, not started yet), or `running` (in progress).
+
+Skip any alert where either value is LOW — troubleshooting is expensive and not warranted for low-signal alerts.
+
+For each job that returned `queued` or `running`, poll with `get_troubleshooting_agent_results(incident_id=...)` — start at ~30 seconds, then increase to 60s intervals. Classify each alert as its result arrives (`success`), before moving on. If a job returns `failed`, note it and continue.
+
+**Classifications:**
+
+| Classification                | When to use                                                                                                           |
+| ----------------------------- | --------------------------------------------------------------------------------------------------------------------- |
+| **Intentional change**        | Planned migrations, feature releases, or bug fixes                                                                    |
+| **Natural data variation**    | Seasonal patterns or expected volatility                                                                              |
+| **Possible data incident**    | Anything that requires further investigation                                                                          |
+| **Resolved incident**         | A real incident that has already been resolved                                                                        |
+| **Verified ongoing incident** | A clear incident that has not resolved, where troubleshooting identified the root cause (e.g. query change or infrastructure failure) |
+| **Other**                     | Does not fit the above                                                                                                |
+
+Alerts that did not go through troubleshooting are left unclassified.
+
+### Step 5: Comments and status updates
+
+**Action mode:**
+
+Call `create_or_update_alert_comment` for each alert:
+- **Untroubleshot alerts**: one sentence describing the anomaly and the incident likelihood/potential impact scores. Do not explain why it wasn't troubleshot. No recommendations.
+- **Troubleshot alerts**: 2–4 sentences covering classification, reasoning from the troubleshooting output, any action taken, and a recommendation.
+
+Then call `update_alert` for each classified alert:
+
+| Classification              | Status               |
+| --------------------------- | -------------------- |
+| Natural data variation      | `NO_ACTION_NEEDED`   |
+| Intentional change          | `EXPECTED`           |
+| Resolved incident           | `FIXED`              |
+| Verified ongoing incident   | `ACKNOWLEDGED`       |
+| Possible data incident      | *(no change)*        |
+| Other                       | *(no change)*        |
+
+For alerts classified as **natural data variation**, also call `mark_event_as_normal` — this signals the ML threshold detector to recalibrate and avoid re-alerting on the same pattern. Only has an effect on monitors using automated (ML-based) thresholds.
+
+Do not update status for untroubleshot alerts.
+
+**Recommendation mode:**
+
+Do not call any write tools. Instead, for each alert output:
+- The comment you would post
+- The status you would set (or "no change")
+- Whether you would call `mark_event_as_normal`
+
+---
+
+## Output
+
+After completing all steps, produce a summary table:
+
+| Alert ID | Type | Incident Likelihood | Potential Impact | Classification | Action Taken |
+|----------|------|---------------------|------------------|----------------|--------------|
+
+Include every alert from step 1. For untroubleshot alerts, leave Classification blank and set Action Taken to "Comment only".
+
+---
+
+## Adapting this example
+
+Common adjustments:
+
+- **Change the time window** in step 2 (e.g. last 1 hour for a continuous loop, last 24 hours for a daily run)
+- **Adjust the troubleshooting filter** in step 4
+- **Add Slack or ticket creation** in step 5 for confirmed incidents
+- **Customise `alert_assessment` scoring** via `user_instructions` to tune emphasis for your environment (see `triage-stages.md`)
+- **Run step-by-step when tuning** — a useful pattern is to run the full workflow straight through first to see end-to-end behaviour, then re-run in step-by-step mode to inspect each stage's output and make decisions before proceeding