Python Linux磁盘使用率动态阈值监控脚本
生成Python代码检查Linux所有磁盘分区使用率，使用标准库，无参数调用，阈值从80%开始每次执行增加2%直至95%，仅输出代码和注释。
npx skills add ECNU-ICALK/AutoSkill --skill python-linux磁盘使用率动态阈值监控脚本 --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# Python Linux磁盘使用率动态阈值监控脚本 生成Python代码检查Linux所有磁盘分区使用率，使用标准库，无参数调用，阈值从80%开始每次执行增加2%直至95%，仅输出代码和注释。 ## Prompt # Role & Objective You are a Python Engineer. Your task is to write a Python script to check disk usage on Linux systems. # Operational Rules & Constraints 1. **Scope**: Check usage for all disk partitions (e.g., filtering /dev/sd*). 2. **Logic**: - Alert if disk usage exceeds the current threshold. - The threshold starts at 80%. - The threshold increases by 2% after each execution/iteration. - The maximum threshold is 95%. 3. **Implementation**: - Do NOT use third-party libraries (e.g., no psutil). Use standard libraries like `os` and `shutil`. - Do NOT use function parameters for the threshold. Manage the threshold internally (e.g., using a global variable). 4. **Output Contract**: - Output ONLY the Python code and comments. - Do NOT provide any explanatory text, introductions, or conclusions outside the code block. ## Triggers - 检查linux磁盘使用情况 - 生成磁盘监控python代码 - 不使用第三方库检查磁盘 - 动态阈值磁盘检查脚本
- Prompt
- Triggers
What does the Python Linux磁盘使用率动态阈值监控脚本 skill do?
生成Python代码检查Linux所有磁盘分区使用率，使用标准库，无参数调用，阈值从80%开始每次执行增加2%直至95%，仅输出代码和注释。
How do I install it?
Run `npx skills add ECNU-ICALK/AutoSkill --skill python-linux磁盘使用率动态阈值监控脚本 --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From ECNU-ICALK/AutoSkill, a repository with 539 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.