Linux Kernel Crash Debug
v1.0.3Debug Linux kernel crashes using the crash utility and memory debugging tools. Use when users mention kernel crash, kernel panic, vmcore analysis, kernel dum...
⭐ 0· 416·3 current·3 all-time
byJames Wang@crazyss
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
OpenClaw
Benign
high confidencePurpose & Capability
The skill's name/description (kernel crash/vmcore analysis) match the instructions and reference material. The SKILL.md lists the expected debugging tools (crash, gdb, readelf, objdump, makedumpfile). Minor mismatch: registry metadata shows 'Required binaries: none' while SKILL.md documents required tools — this is likely an omission in metadata rather than malicious.
Instruction Scope
All runtime instructions are focused on vmcore/vmlinux analysis and related kernel-debug tooling (crash commands, readelf, makedumpfile, KASAN/Kprobes, kmemleak, etc.). These commands necessarily read kernel memory and interact with debug sysfs; that is expected for the stated purpose. The docs also include dangerous operations (writing to kprobe_events, inserting modules, the 'wr' command) and correctly flag them as risky.
Install Mechanism
No install spec or packaged executable is present — this is an instruction-only skill that references running existing system tools. That minimizes supply-chain risk (nothing downloaded or executed by the skill itself).
Credentials
The skill requests no environment variables, no credentials, and no config paths. The tools it uses require elevated privileges on the host (root) to access vmcore and debug interfaces — this privilege is proportional to kernel debugging use cases, but it exposes sensitive memory and should only be used on systems you control.
Persistence & Privilege
The skill does not request always: true and contains no install hooks or self-modifying behavior. It is user-invocable and can be invoked autonomously per platform defaults, which is normal for skills; nothing else indicates elevated persistent privileges.
Assessment
This skill is coherent for kernel crash debugging, but consider the following before installing/using it:
- Trust and provenance: the registry entry lists 'Source: unknown' and no homepage, even though README points to a GitHub repo; verify the skill's origin and checksum before installing. Prefer a maintained upstream repository.
- Privileges and sensitivity: using the described commands requires root and will read kernel memory (vmcore, /proc/vmcore, etc.). vmcore can contain sensitive secrets (keys, passwords, process memory). Only run these steps on systems you control or in an isolated environment and do not upload vmcore files to untrusted services.
- Dangerous operations: the docs include actions that modify the running system (kprobe insertion, kernel modules, and the 'wr' crash utility command). The skill notes these are dangerous — avoid running them on production systems unless you understand the impact.
- Tool availability: SKILL.md lists required binaries (crash, gdb, readelf, objdump, makedumpfile) but registry metadata shows none; confirm these tools are installed on the host before use.
- Minimal install risk: there is no install script or remote download in the package, so the skill itself does not add code execution risk, but following its instructions will execute powerful host tools.
If you want to proceed: verify the source repo, run in a controlled/test environment, and ensure you have backups and appropriate permissions before performing any intrusive operations.Like a lobster shell, security has layers — review code before you run it.
latestvk9751x16m5q98hra2639bek2e583s2sw
License
MIT-0
Free to use, modify, and redistribute. No attribution required.
