server-management
Server Management Principles
Learn server management thinking and decision-making for production systems. This skill teaches process management, monitoring strategy, and scaling principles rather than memorized commands.
スキルZIPをダウンロード
Claudeでアップロード
設定 → 機能 → スキル → スキルをアップロードへ移動
オンにして利用開始
テストする
「server-management」を使用しています。 What process manager should I use for a Node.js application?
期待される結果:
- For Node.js in production, PM2 is recommended. It provides clustering, zero-downtime reload, and auto-restart on crash. Alternative: systemd for Linux-native integration.
「server-management」を使用しています。 When should I scale horizontally vs vertically?
期待される結果:
- Vertical scaling (more CPU/RAM) offers quick fixes for single-instance bottlenecks. Horizontal scaling (more instances) provides sustainability and distribution. Choose vertical for immediate needs, horizontal for long-term growth.
「server-management」を使用しています。 What are the key server security principles?
期待される結果:
- Key principles: SSH keys only (no passwords), firewall with minimal ports, regular security updates, environment variables for secrets, comprehensive audit logging.
セキュリティ監査
安全Static analysis flagged two instances of 'weak cryptographic algorithm' at SKILL.md lines 3 and 166. After manual review, these are FALSE POSITIVES. Line 3 contains only a description string in YAML frontmatter, and line 166 contains only instructional text. The file contains no cryptographic code, no network requests, no file system operations, no environment access, and no external command execution. This is purely educational content teaching server management concepts.
検出されたパターン
品質スコア
作れるもの
DevOps Learning
New developers learning server operations and production concepts
Architecture Decision Making
Engineers making decisions about monitoring and scaling strategies
System Troubleshooting
Teams establishing troubleshooting workflows and priorities
これらのプロンプトを試す
What process manager should I use for a Node.js application in production?
What key metrics should I monitor for a web application?
When should I scale horizontally versus vertically?
What should a proper health check include?
ベストプラクティス
- Start monitoring from day one rather than adding it later
- Use structured logging (JSON format) for easier parsing and analysis
- Implement auto-restart configurations to handle crashes automatically
- Choose health check depth based on load balancer requirements
回避
- Running services as root instead of non-root users
- Ignoring logs or skipping log rotation setup
- Manual restarts instead of configuring auto-restart
- Skipping backups or not having a regular backup schedule