system-resource-diagnosis

Name: system-resource-diagnosis
Availability: InStock
Author: linfordwu

Collect Linux runtime data to diagnose system resource bottlenecks.

1|1|Updated Apr 25, 2026

Search Tags:#diagnostics #linux #ulimit #system-resources #ipc #core-dump #inotify

Ready to run

npx skills add https://github.com/linfordWu/owls --skill system-resource-diagnosis

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: system-resource-diagnosis
Source: https://github.com/linfordWu/owls/tree/main/skills/system-resource-diagnosis
Command: npx skills add https://github.com/linfordWu/owls --skill system-resource-diagnosis

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

专业的 Linux 系统资源故障在线诊断 skill。当用户描述涉及进程数超出 & ulimit 限制、进程栈溢出、IPC 资源耗尽、inotify 句柄耗尽、内核模块加载失败、fork 失败、无法创建新进程、SIGSEGV core dump、消息队列/共享内存/信号量无法使用、文件监控失效、insmod/modprobe 失败等问题时，必须使用此 skill。

Core Features & Use Cases

信息收集与初步诊断：聚合关键维度（ulimit、进程数、栈、IPC、inotify、内核模块等），快速定位资源瓶颈。
全量诊断报告：输出结构化诊断报告到临时目录，包含阶段性证据和核对清单，便于后续处置。
安全边界与无操作性修复建议：仅分析并给出修复建议，不执行任何修复命令，确保安全性。

Quick Start

运行 collect_resource_info.sh 脚本进行资源诊断，指定起始时间即可自动生成报告。

Frequently Asked Questions about system-resource-diagnosis

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I diagnose Linux system resource bottlenecks like IPC exhaustion and fork errors?▼

Diagnose Linux system resource bottlenecks by running a script to collect deep runtime data on ulimit, processes, IPC, and inotify, which then outputs a structured diagnostic report for remediation.

Why does my Linux server fail to create new processes or load kernel modules?▼

Linux server process creation or kernel module loading failures are identified by collecting runtime data on process limits and kernel modules, analyzing the findings without executing fixes, and logging structured evidence.

What is the best way to troubleshoot SIGSEGV core dumps and stack overflows on Linux?▼

Troubleshooting SIGSEGV core dumps and stack overflows involves collecting deep runtime data across affected servers, generating a full diagnostic report with phased evidence and checklists stored in a temporary directory.

Can I use this diagnostic approach to safely check inotify handle limits without executing fixes?▼

Yes, you can safely check inotify handle limits because the diagnostic process enforces a strict safe boundary by performing only data collection, analysis, and guidance without executing any remediation commands.

Does this Linux resource diagnosis require any external dependencies or components?▼

No external dependencies are required to run this Linux resource diagnosis; it operates using included shell scripts to aggregate critical dimensions like IPC, ulimit, and inotify metrics directly on the server.

What limitations exist when diagnosing excessive processes and message queue failures on Linux?▼

The primary limitation is that the diagnosis only collects and analyzes data for excessive processes and message queue failures, providing structured guidance without directly modifying system configurations or executing repairs.