zscaler

Investigate Alerts — Development skill for Claude Code

Development community

Investigate active and historical ZDX alerts to understand scope, root cause, and impact.

How to install Investigate Alerts

Installs to ~/.claude/skills/zscaler-zscaler-mcp-server-investigate-alerts/SKILL.md

Terminal

mkdir -p ~/.claude/skills/zscaler-zscaler-mcp-server-investigate-alerts && curl -fsSL https://raw.githubusercontent.com/zscaler/zscaler-mcp-server/HEAD/commands/investigate-alerts.md -o ~/.claude/skills/zscaler-zscaler-mcp-server-investigate-alerts/SKILL.md

Restart Claude Code, or start a new session, for it to be picked up.

What Investigate Alerts does

name: investigate-alerts disable-model-invocation: true argument-hint: "[since_hours] [severity: all|critical|warning]" description: "Investigate active and historical ZDX alerts to understand scope, root cause, and impact."

Investigate ZDX Alerts

Investigate alerts: **$ARGUMENTS**

Step 1: Parse Input

Extract:

Time window in hours (default: 24)
Severity filter (default: all)

Step 2: List Active Alerts

zdx_list_alerts(since=)
```text

## Step 3: F

Alternatives in Development

Root Cause Tracing — Use when errors occur deep in execution and you need to trace back to find the original trigger 102.5k ★
Triage PRs — Classify all open PRs by module, review state, scope, and architectural impact — produces a prioritized triage 12.6k ★
Skill.Color Expert — Agent skill for color science expertise 426 ★