.NET Crash Dump Collection
dotnet/skills
Configures automatic crash dumps or captures dumps from running processes for modern .NET apps on Linux, macOS and Windows, including Docker and Kubernetes.
Agent skill
Debugs a single Linux host or container runtime at the kernel level with the standalone ig binary and eBPF gadgets, read-only and without Kubernetes.
$ npx skills add inspektor-gadget/inspektor-gadget --skill linux-troubleshooting -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install inspektor-gadget/inspektor-gadget linux-troubleshooting --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/inspektor-gadget/inspektor-gadget.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/linux-troubleshooting .claude/skills/linux-troubleshooting && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "linux-troubleshooting" agent skill from https://github.com/inspektor-gadget/inspektor-gadget/tree/main/skills/linux-troubleshooting into .claude/skills/linux-troubleshooting/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "linux-troubleshooting", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/inspektor-gadget/inspektor-gadget/tree/main/skills/linux-troubleshootingType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add inspektor-gadget/inspektor-gadget --skill linux-troubleshooting -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install inspektor-gadget/inspektor-gadget linux-troubleshooting --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/inspektor-gadget/inspektor-gadget.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/linux-troubleshooting .agents/skills/linux-troubleshooting && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "linux-troubleshooting" agent skill from https://github.com/inspektor-gadget/inspektor-gadget/tree/main/skills/linux-troubleshooting into .agents/skills/linux-troubleshooting/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "linux-troubleshooting", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add inspektor-gadget/inspektor-gadget --skill linux-troubleshooting -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install inspektor-gadget/inspektor-gadget linux-troubleshooting --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/inspektor-gadget/inspektor-gadget.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/linux-troubleshooting .cursor/skills/linux-troubleshooting && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "linux-troubleshooting" agent skill from https://github.com/inspektor-gadget/inspektor-gadget/tree/main/skills/linux-troubleshooting into .cursor/skills/linux-troubleshooting/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "linux-troubleshooting", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/inspektor-gadget/inspektor-gadget.git --path skills/linux-troubleshooting--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add inspektor-gadget/inspektor-gadget --skill linux-troubleshooting -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install inspektor-gadget/inspektor-gadget linux-troubleshooting --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/inspektor-gadget/inspektor-gadget.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/linux-troubleshooting .gemini/skills/linux-troubleshooting && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "linux-troubleshooting" agent skill from https://github.com/inspektor-gadget/inspektor-gadget/tree/main/skills/linux-troubleshooting into .gemini/skills/linux-troubleshooting/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "linux-troubleshooting", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install inspektor-gadget/inspektor-gadget linux-troubleshootingInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add inspektor-gadget/inspektor-gadget --skill linux-troubleshooting -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/inspektor-gadget/inspektor-gadget.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/linux-troubleshooting .github/skills/linux-troubleshooting && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "linux-troubleshooting" agent skill from https://github.com/inspektor-gadget/inspektor-gadget/tree/main/skills/linux-troubleshooting into .github/skills/linux-troubleshooting/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "linux-troubleshooting", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add inspektor-gadget/inspektor-gadget --skill linux-troubleshooting -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install inspektor-gadget/inspektor-gadget linux-troubleshooting --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/inspektor-gadget/inspektor-gadget.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/linux-troubleshooting .opencode/skills/linux-troubleshooting && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "linux-troubleshooting" agent skill from https://github.com/inspektor-gadget/inspektor-gadget/tree/main/skills/linux-troubleshooting into .opencode/skills/linux-troubleshooting/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "linux-troubleshooting", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
linux-troubleshootingDebugs a single Linux host or container runtime at the kernel level with the standalone ig binary and eBPF gadgets, read-only and without Kubernetes.
The ig binary runs the same eBPF gadgets as Inspektor Gadget's Kubernetes integration, but against one machine and its local container runtime (Docker, containerd, CRI-O or podman). It suits VMs, edge nodes and CI runners where logs fall short: DNS or TCP failures, resets and retransmits, processes exiting or being killed, failed file opens, permission, capability, seccomp or LSM denials, slow disk I/O, and questions like which process made a syscall or connection. Events carry the container name and runtime, and --host adds non-container processes.
The central rule is to discover rather than guess: each gadget is an OCI image pulled on demand, so the agent reads its --help and field list instead of recalling flags. The loop is to route the symptom to a domain (networking, security, process lifecycle, storage or performance), discover the gadget's options, run it bounded with a timeout and filters by container, command or pid, and repeat until the root cause shows. It needs ig on PATH, root and a BTF-enabled kernel, and asks the operator before installing on a host that is not yours. Kubernetes clusters go to kubernetes-troubleshooting.
4 steps, taken from the first numbered list in SKILL.md.
Read from SKILL.md and the folder at commit 1f292a7. It shows what the files ask for, not the result of running them.
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Shell commands in SKILL.md call:
kubectljqFrom the folder's file list and the shell code blocks in SKILL.md.
No URLs in SKILL.md. Its commands use kubectl, which can reach the network depending on how they are called.
From URLs in SKILL.md, links to its own repository left out.
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Requires the standalone `ig` binary on PATH, run as root (CAP_BPF + CAP_SYS_ADMIN), on a BTF-enabled kernel (`/sys/kernel/btf/vmlinux`) for CO-RE. An optional container runtime (containerd/Docker/CRI-O/podman) enriches events; `--host` traces bare-host processes. Read-only. If `ig` is missing, see references/install.md — ask the operator before installing.
From compatibility in the SKILL.md frontmatter.
Linux Troubleshooting with Inspektor Gadget loads about 2.4k tokens when it runs, and up to ~6.8k if it reads all its reference files. Until then it costs about 200 tokens; SKILL.md has 889 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
The automated check noted patterns worth knowing about, such as sudo or a known installer.
I runners, or any box where you can run `sudo ig`. Events aresudo ig run <gadget>:latest --help # flags + a "--fields" block listing every data source & fieldsudo ig run <gadget>:latest --timeout 5 -o json \`sudo ig run <gadget>:latest --runtimes containerd -c <name> --timeout <sec> -o json`e-host skill, swap `kubectl gadget run`→`sudo ig run` and `-n`/`-p`→Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
The full file from inspektor-gadget/inspektor-gadget at commit 1f292a7, republished under its Apache-2.0 licence (© inspektor-gadget). 889 words, ~2,359 tokens.
.claude/skills/linux-troubleshooting/SKILL.md (or your agent's skills folder). This skill also uses 5 other files; get the full folder from GitHub.The standalone ig binary runs the same eBPF gadgets as the Kubernetes
integration, but against a single Linux host and its local container runtime
(Docker / containerd / CRI-O / podman) — no cluster, no kubectl. Use it on
VMs, edge nodes, CI runners, or any box where you can run sudo ig. Events are
enriched with container name + runtime (not pod/namespace) when a runtime is
present; with --host you also see host (non-container) processes.
Reach for ig when host logs/metrics can't answer "what is the kernel doing
right now?" — a syscall failing silently, a connection reset before the app
notices, a file open returning ENOENT.
This skill drives the standalone ig binary. Confirm it's usable before the loop:
command -v ig >/dev/null 2>&1 && ig version || echo "ig MISSING -> references/install.md"If ig is missing, open references/install.md and follow it — don't guess
an install command. ig needs root (CAP_BPF / CAP_SYS_ADMIN) and a BTF-enabled
kernel; ask the operator before installing on a host you don't own.
Never hardcode a gadget's flags or field names from memory. Enumerate the real interface at run time:
sudo ig run <gadget>:latest --help # flags + a "--fields" block listing every data source & field
sudo ig run <gadget>:latest --timeout 5 -o json \
| jq -s '(.[0] // {}) | if type == "array" then (.[0] // {}) else . end | keys'Each gadget is an OCI image pulled on demand; there is no list-gadgets
command and no fixed list to memorize. The gadget's own --help/--fields is
the source of truth. See references/discovering-params-and-fields.md.
references/gadget-catalog.md.<gadget>:latest --help to read the real flags and fields.sudo ig run <gadget>:latest --runtimes containerd -c <name> --timeout <sec> -o json
(-c filters by container, --comm/--pid by process; add --host for host
processes; always set --timeout; --max-entries for top/snapshot).
See references/common-flags.md.runtime.*, proc.*, error codes)
to confirm or refute, then narrow and repeat.--help)| Symptom | Domain | Start with | Then / disambiguate |
|---|---|---|---|
| DNS fails / slow / NXDOMAIN | networking | trace_dns | latency in latency_ns |
| Connection reset / refused / hangs | networking | trace_tcp | trace_tcpretrans, trace_tcpdrop |
| Packet loss / high latency | networking | trace_tcpdrop | profile_tcprtt, top_tcp, tcpdump |
| TLS/cert/SNI issue | networking | trace_sni | trace_ssl |
| Port bind fails / "address already in use" | networking | snapshot_socket | trace_bind (bind + errno) |
| Process exits / restarts unexpectedly | process-lifecycle | trace_exec | trace_signal (filter --signal 9/15 — Go SIGURG / glibc SIGRTMIN async-preempt noise), trace_oomkill |
| Process killed / OOM | process-lifecycle | trace_oomkill | top_process, profile_cpu |
| Container died too fast to trace live (post-mortem) | process-lifecycle | traceloop | replays recent syscalls from the ring buffer; empty if it wasn't already recording |
| Watch an interactive shell / tty / pts / keystrokes | process-lifecycle | ttysnoop | no --tty/--pts selector — scope by --pid/--comm/container |
| "no such file" / missing path | storage-fs | trace_open --failed | snapshot_file, top_file |
| Slow disk / file I/O | storage-fs | trace_fsslower | profile_blockio, top_blockio |
| Unexpected mount/umount, or suspicious hardlink/symlink (escape) | storage-fs | trace_mount | trace_link (type = HARDLINK/SYMLINK cuts the noise) |
| fd leak / "too many open files" / inotify watch storm | storage-fs | fdpass | fsnotify; snapshot_file (unclosed fds in one proc) |
| Permission denied despite correct FS perms | security | trace_capabilities | audit_seccomp; host audit logs for AppArmor/SELinux |
| Seccomp denial | security | audit_seccomp | the code + syscall identify the seccomp action; advise_seccomp to author a profile |
| AppArmor/SELinux denial | security | host audit logs | trace_lsm can correlate hook activity, but does not expose another LSM's verdict |
| Kernel module loaded / rootkit / unexpected insmod | security | trace_init_module | trace_capabilities (CAP_SYS_MODULE) |
| Harden / author a seccomp or NetworkPolicy profile | security | advise_seccomp | advise_networkpolicy |
| High CPU, or slow despite low CPU% (CFS throttling / cgroup CPU limit) | performance | profile_cpu | top_cpu_throttle (capped?), top_process |
| Memory growth / leak (userspace) | performance | trace_malloc (libc malloc only — statically-linked Go runtime allocator invisible) | trace_malloc --collect-ustack (the leak site) |
| App hung / mutex deadlock | performance | deadlock (pthread only — Go sync.Mutex invisible) | profile_cpu |
| GPU / CUDA out-of-memory | performance | top_cuda_memory | device vs pinned; profile_cuda = libcuda Driver-API |
| Quantify eBPF/gadget CPU or memory overhead (self-profiling) | meta | bpfstats | needs an active window — longer --timeout |
This is a deliberately thin shortlist, not the catalog — it names the few
gadgets that fit the most common symptoms so you don't scan the full bundled set,
keeping this always-loaded router small. Symptom not listed, or
unsure which row fits? Read references/gadget-catalog.md — it groups all
bundled gadgets by domain with the disambiguation reasoning (which of the
TCP/file/TLS/CPU gadgets to pick). The authoritative live list is whatever sudo ig run <name>:latest --help resolves; confirm a gadget's flags/fields there
before relying on them.
references/gadget-catalog.md — all upstream gadgets grouped by domain, with per-domain disambiguation.references/discovering-params-and-fields.md — discover-don't-guess mechanics (ig variant).references/common-flags.md — host/container scope, output, timeouts, gotchas.references/install.md — detect whether ig is usable; install it + requirements (root, BTF) if missing.references/kubernetes-companion.md — when to switch to kubectl gadget (clusters).The five per-domain playbooks (networking, security, process-lifecycle,
storage-fs, performance) live in the kubernetes-troubleshooting skill's
references/ tree and apply verbatim here — the gadgets, flags, and fields are
identical; only the launcher and scope flags differ. To use one from this
single-host skill, swap kubectl gadget run→sudo ig run and -n/-p→
-c/--host (full mapping in references/kubernetes-companion.md):
../kubernetes-troubleshooting/references/domain-networking.md — DNS / TCP / drops / retransmits / TLS-SNI / pcap / NetworkPolicy.../kubernetes-troubleshooting/references/domain-security.md — capabilities / LSM / seccomp / kernel-module loading.../kubernetes-troubleshooting/references/domain-process-lifecycle.md — exec / signals / OOM / snapshots / traceloop / tty.../kubernetes-troubleshooting/references/domain-storage-fs.md — open / slow FS / block I/O / mounts / links / fd / fsnotify.../kubernetes-troubleshooting/references/domain-performance.md — CPU / throttle / RTT / deadlock / malloc / GPU.Observation is read-only — gadgets never modify the host or containers. ig
needs elevated privileges (typically sudo, CAP_BPF/CAP_SYS_ADMIN) to load eBPF.
Always bound streaming gadgets with --timeout and cap top/snapshot with
--max-entries.
© inspektor-gadget, Apache-2.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
SKILL.md and 5 other files (references) in skills/linux-troubleshooting of inspektor-gadget/inspektor-gadget.
Open the folder on GitHubat commit 1f292a7
Linux Troubleshooting with Inspektor Gadget next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Linux Troubleshooting with Inspektor Gadget this skillinspektor-gadget/inspektor-gadget | 2.9k | — | ~2.4k | Automated safety check: Notes | Apache-2.0 | |
| .NET Crash Dump Collectiondotnet/skills | 5.6k | 2 repos | ~1.1k | Automated safety check: Pass | MIT | |
| Minimegasandia-minimega/minimega | 160 | — | ~3.2k | Automated safety check: Pass | GPL-3.0-only | |
| Setup Cpu Proxy Serverdrawthingsai/draw-things-community | 582 | — | ~3.8k | Automated safety check: Pass | GPL-3.0 | |
| Podmansickn33/agentic-awesome-skills | 47k | 1 repos | ~2.2k | Automated safety check: Notes | MIT | |
| Sshepherdsickn33/agentic-awesome-skills | 47k | 1 repos | ~1.6k | Automated safety check: Warn | MIT |
dotnet/skills
Configures automatic crash dumps or captures dumps from running processes for modern .NET apps on Linux, macOS and Windows, including Docker and Kubernetes.
sandia-minimega/minimega
This skill should be used when the user asks how to configure, run, automate, integrate, or troubleshoot minimega (VMs, namespaces, VLANs, clusters, miniccc, miniweb, command socket or Python API…
drawthingsai/draw-things-community
Set up and verify a new Draw Things CPU proxy and Envoy server using the scripts in Scripts/ServerManagement/CPUScript.
sickn33/agentic-awesome-skills
Manage containers using Podman, the daemonless container engine.
sickn33/agentic-awesome-skills
Zero-knowledge SSH ops CLI — server health checks, docker/systemd control, log tailing, Postgres introspection, and declarative deploys, without ever exposing credentials to the agent.
BagelHole/DevOps-Security-Agent-Skills
Manage containers using Podman, the daemonless container engine.
inspektor-gadget/inspektor-gadget
Traces what the kernel is doing for a misbehaving pod using Inspektor Gadget's eBPF tools, tagged with namespace, pod, container and node, without changing workloads.
Categories
Debugs a single Linux host or container runtime at the kernel level with the standalone ig binary and eBPF gadgets, read-only and without Kubernetes. The ig binary runs the same eBPF gadgets as Inspektor Gadget's Kubernetes integration, but against one machine and its local container runtime (Docker, containerd, CRI-O or podman). It suits VMs, edge nodes and CI runners where logs fall short: DNS or TCP failures, resets and retransmits, processes exiting or being killed, failed file opens, permission, capability, seccomp or LSM denials, slow disk I/O, and questions like which process made a syscall or connection.
Linux Troubleshooting with Inspektor Gadget fits situations like: tracing DNS or TCP failures on a host where application logs show nothing; finding which process opened a missing file or was killed by the kernel; diagnosing permission, capability or seccomp denials in a container; investigating slow disk or file I/O on a CI runner or edge node.
Run `npx skills add inspektor-gadget/inspektor-gadget --skill linux-troubleshooting -a claude-code`. Or copy the skill folder (skills/linux-troubleshooting in inspektor-gadget/inspektor-gadget) into .claude/skills/linux-troubleshooting in your project. Claude Code loads it when a task matches its description.
Run `npx skills add inspektor-gadget/inspektor-gadget --skill linux-troubleshooting -a codex`. Or copy the skill folder (skills/linux-troubleshooting in inspektor-gadget/inspektor-gadget) into .agents/skills/linux-troubleshooting in your project. Codex loads it when a task matches its description.
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add inspektor-gadget/inspektor-gadget --skill linux-troubleshooting -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/linux-troubleshooting, .gemini/skills/linux-troubleshooting, .github/skills/linux-troubleshooting and .opencode/skills/linux-troubleshooting in your project.
Going by SKILL.md and its folder, Linux Troubleshooting with Inspektor Gadget needs the command-line tools its instructions call (kubectl and jq). Our summary lists: The standalone ig binary on PATH; Root access (CAP_BPF and CAP_SYS_ADMIN); A BTF-enabled Linux kernel. Compatibility (from SKILL.md): Requires the standalone `ig` binary on PATH, run as root (CAP_BPF + CAP_SYS_ADMIN), on a BTF-enabled kernel (`/sys/kernel/btf/vmlinux`) for CO-RE. An optional container runtime (containerd/Docker/CRI-O/podman) enriches events; `--host` traces bare-host processes. Read-only. If `ig` is missing, see references/install.md — ask the operator before installing..
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Our automated static check of SKILL.md found notes only (runs commands with sudo), nothing it rates as a warning. It is not a guarantee. Review the folder before installing.
Linux Troubleshooting with Inspektor Gadget is published under the Apache-2.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
About 2.4k tokens (SKILL.md is roughly 9.4k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 4.5k tokens, read only when the agent opens those files.
Skills that share tags, products or a category with Linux Troubleshooting with Inspektor Gadget: .NET Crash Dump Collection (dotnet/skills, 5.6k stars), Minimega (sandia-minimega/minimega, 160 stars), Setup Cpu Proxy Server (drawthingsai/draw-things-community, 582 stars) and Podman (sickn33/agentic-awesome-skills, 47k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
inspektor-gadget (a GitHub organization) maintains it in inspektor-gadget/inspektor-gadget, which has 2,936 GitHub stars. The repository holds 2 skills in this directory. The repository was last updated on October 9, 2026.
Source: inspektor-gadget/inspektor-gadget on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.