os-scripting
Troubleshoot OS and Shell Scripts
This workflow bundle helps developers and system administrators debug shell scripts, create production-ready bash code, and automate system administration tasks across Linux, macOS, and Windows.
スキルZIPをダウンロード
Claudeでアップロード
設定 → 機能 → スキル → スキルをアップロードへ移動
オンにして利用開始
テストする
「os-scripting」を使用しています。 Help me debug a bash script that exits with error code 1
期待される結果:
I'll help you debug this systematically. First, let me check the script for common issues using ShellCheck, then we'll enable debug mode and trace the execution...
「os-scripting」を使用しています。 Create a monitoring script for disk space
期待される結果:
I'll create a production-ready monitoring script with proper error handling, logging, and notifications. This will check disk space and alert when usage exceeds thresholds...
「os-scripting」を使用しています。 My server has high CPU usage, help troubleshoot
期待される結果:
Let's diagnose this systematically. We'll check running processes, identify resource-heavy tasks, and analyze system logs to find the cause...
セキュリティ監査
安全This is a documentation/workflow bundle skill (SKILL.md) that provides educational guidance on OS and shell scripting. All 93 static findings are false positives. The detected 'external_commands', 'network', and 'filesystem' patterns are example commands in documentation, not executable code. The skill's own metadata correctly identifies it as 'risk: safe'.
品質スコア
作れるもの
Debug a failing bash script
Use systematic debugging techniques to trace and fix shell script errors with proper logging and error handling.
Create production-ready automation
Build robust shell scripts with proper error handling, input validation, and testing using Bats framework.
Troubleshoot system performance
Diagnose high CPU, memory issues, disk space problems, and network connectivity using standard system commands.
これらのプロンプトを試す
Use @os-scripting to help me check system performance and identify any issues
Use @os-scripting to analyze my shell script for issues and run ShellCheck on it
Use @os-scripting to systematically debug this shell script that is failing with error: [describe error]
Use @os-scripting to help me create a production-ready backup script with error handling and tests
ベストプラクティス
- Always use 'set -euo pipefail' at the script start for strict error handling
- Quote all variables to prevent word splitting and globbing issues
- Add comprehensive logging with timestamps for troubleshooting
- Write Bats tests for all critical script functionality
回避
- Using unquoted variables that may contain spaces or special characters
- Ignoring exit codes from commands with '|| true' without explicit handling
- Not validating user input before using it in commands
- Writing scripts without any error handling or logging