Thread Dump Analyzer
PassAudited by ClawScan on May 1, 2026.
Overview
This instruction-only skill is coherent for diagnosing thread dumps, with only a normal operational caution around running diagnostic commands against live processes.
Safe to consider installing as an instruction-only diagnostic aid. Before using it on a live service, verify the target process, understand the runtime-specific effects of signals such as SIGQUIT or USR1, and keep generated thread dumps private because they may reveal internal application behavior.
Findings (1)
Artifact-based informational review of SKILL.md, metadata, install specs, static scan signals, and capability signals. ClawScan does not execute the skill or run runtime probes.
If a user or agent runs the examples carelessly, it could target the wrong local process, trigger runtime-specific signal behavior, or create local dump files containing internal application details.
The skill documents local diagnostic commands that can signal matching processes or read local profiling endpoints. This is central to the stated purpose, but those commands can affect live applications if used against the wrong process or in production without care.
jstack $(pgrep -f 'java.*your-app') > /tmp/thread-dump.txt 2>&1 ... kill -QUIT $(pgrep -f 'your-go-app') ... curl -s http://localhost:6060/debug/pprof/goroutine?debug=2 > /tmp/goroutine-dump.txt
Confirm the exact process ID and environment before running capture commands, prefer the least disruptive dump method available, and treat generated dump files as sensitive diagnostic artifacts.