zscaler

Diagnose Deeptrace — Development skill for Claude Code

Development community

Run a ZDX deep trace diagnostics session — start, analyze, or clean up deep traces for a user's device.

How to install Diagnose Deeptrace

Installs to ~/.claude/skills/zscaler-zscaler-mcp-server-diagnose-deeptrace/SKILL.md

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

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

What Diagnose Deeptrace does


name: diagnose-deeptrace disable-model-invocation: true argument-hint: " [application_name] [action: analyze|start|cleanup]" description: "Run a ZDX deep trace diagnostics session — start, analyze, or clean up deep traces for a user's device."

Deep Trace Diagnostics Session

Perform deep trace diagnostics for: **$ARGUMENTS**

Step 1: Parse Input

Extract:

  • Username or email (required)
  • Application name (optional — if not provided, the session covers al

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 ★
  • Claude Supermemory — Persistent memory across sessions and projects using Supermemory 2.3k ★
  • Job Watcher — Monitor and manage VASP jobs 155 ★

Full documentation available on GitHub

View Source Repository