correlated-triage skillA
correlated-triage is agent-read markdown (skill) from papadopouloskyriakos/agentic-chatops: When multiple hosts alert simultaneously (burst), create a master YouTrack issue, run per-host triage, link children, analyze correlation, and escalate the master to Claude Code..
Indexed from public GitHub and served as immutable, content-addressed versions. Install it pinned to an exact SHA-256 with the mdr CLI, and every file is verified against the hash recorded here before it reaches your agent. The deterministic audit below grades the latest version, and the same file always earns the same grade.
What the file says
# Correlated Alert Triage (Multi-Host Burst) When you receive a message containing `correlated-triage.sh` in `#infra-nl-prod` or `#infra-gr-prod`, you MUST immediately execute the triage using the `exec` tool. Do NOT ask questions — just execute. ## Execution Use the `exec` tool to run the correlated triage script: ```bash source /home/app-user/.openclaw/workspace/.env && ./skills/correlated-triage/correlated-triage.sh "<comma-separated-hosts>" "<comma-separated-rules>" "<comma-separated-severities>" ``` The script will: 1. Create a MASTER YouTrack issue summarizing the burst 2. Run per-host triage (reusing `infra-triage.sh`) without individual escalation 3. Link each child issue as a subtask of the master 4. Post a correlation analysis comment on the master issue 5. Escalate the MASTER issue only to Claude Code (Level 3) ## CRITICAL RULES 1. **ALWAYS use the `exec` tool** to run the command. Do NOT describe what to do — execute it. 2. **Run the ENTIRE command as given.** Do not modify arguments or split into multiple calls. 3. **Do NOT run individual infra-triage.sh calls** — the correlated script handles all hosts sequentially. …
Read the whole file at its exact version.
How to install
mdr add papadopouloskyriakos/agentic-chatops/correlated-triage@git:20260919.c129a05mdr add papadopouloskyriakos/agentic-chatops/correlated-triage@sha256:d68884106df67804Pin to a label to follow the author's releases, or to a sha256 to freeze the exact bytes forever. Either way the resolved hash is written to mdr.lock, and mdr install reproduces it on any machine.
[](https://markdownregistry.com/a/art_njndtfxbasd3vpdm)
1 badge views in 30 days
Versions
Audit of the latest version
- pass: Frontmatter block present
- pass: Frontmatter declares a name
- pass: Frontmatter declares a description
- pass: Size between 200 bytes and 200 KB (1566 bytes)
- pass: No zero-width or bidi control characters
- pass: No instruction hidden inside an HTML comment
- pass: No link to an exfiltration or paste host
- pass: No credential-shaped string
- pass: No instruction to send local credentials anywhere
- pass: No text hidden with inline styles
- pass: No prompt-injection phrasing
- pass: No curl or wget piped into a shell
- pass: No recursive delete of root, home or parent
- pass: No instruction to read or print local credentials
- pass: No base64 blob over 200 characters
- pass: No link to a raw IP address
- pass: No script tag
Source
papadopouloskyriakos/agentic-chatops · 107 stars · license none · pushed 2026-09-21 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_njndtfxbasd3vpdm GET https://markdownregistry.com/api/v1/resolve?ref=papadopouloskyriakos/agentic-chatops/correlated-triage GET https://markdownregistry.com/api/v1/blob/d68884106df67804d709266480c6110a9d09001016cddab9358c0499afb87cb0
Your agent does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.