remote-system-maintenance
Use when performing system maintenance or diagnostics on remote Linux systems via tmux - provides structured checklists for Ubuntu/Debian cleanup (apt, journal, snap revisions), diagnostic procedures, and log file templates with quantification patterns
When & Why to Use This Skill
This Claude skill streamlines remote Linux system maintenance and diagnostics, specifically optimized for Ubuntu and Debian environments. It provides a structured three-phase approach—covering initial diagnostics, log reviews, and package assessments—alongside automated cleanup sequences for apt, journal logs, and snap revisions to reclaim disk space and ensure peak system performance.
Use Cases
- Routine server maintenance: Reclaiming significant disk space (often 2GB+) by purging package caches, vacuuming journals, and removing obsolete snap revisions.
- Remote diagnostics: Performing structured health checks and resource utilization analysis on remote servers via SSH or tmux sessions.
- Standardized IT runbooks: Implementing a consistent, seven-stage cleanup sequence across multiple Linux environments to reduce human error.
- System optimization: Identifying and removing orphaned configurations, unused dependencies, and zombie processes to improve system stability.
- Compliance and reporting: Generating detailed maintenance logs that quantify resource improvements and document all actions taken for auditing purposes.
| name | remote-system-maintenance |
|---|---|
| description | This skill should be used when performing maintenance or diagnostics on remote Linux systems. Triggers on "remote server", "Linux maintenance", "Ubuntu cleanup", "Debian", "disk space", "apt cleanup", "journal vacuum", "snap cleanup", "system diagnostics". Provides structured three-phase checklists with quantification. |
Remote System Maintenance
Purpose
Structured guidance for diagnosing and maintaining remote Linux systems through SSH/tmux sessions, with emphasis on Ubuntu/Debian platforms.
Applicable Scenarios
- System maintenance tasks
- Disk space recovery
- Package updates
- Health diagnostics
- Cleanup operations on remote servers
Three-Phase Approach
Phase 1: Initial Diagnostics
Capture baseline system state:
- Hostname and system identification
- Resource utilization (disk, memory, CPU)
- Process status and load
- Zombie process detection
Phase 2: System Log Review
Examine system health indicators:
- Recent error messages in system logs
- Journal disk consumption analysis
- Critical service status
- Authentication and security events
Phase 3: Package Assessment
Identify maintenance opportunities:
- Upgradable packages
- Orphaned configurations
- Unused dependencies
- Package cache size
Ubuntu/Debian Cleanup Sequence
Execute these seven stages in order:
- Package Cache Refresh -
apt updateto sync package lists - System Upgrades -
apt upgradefor security and bug fixes - Orphan Removal -
apt autoremoveto clean unused dependencies - Cache Purging -
apt cleanto reclaim package cache space - Journal Pruning -
journalctl --vacuum-time=7dto limit log retention - Snap Revision Cleanup - Remove disabled snap revisions (see below)
- Temporary Directory Assessment - Review
/tmpand/var/tmpfor cleanup opportunities
Snap Revision Cleanup Technique
Snap keeps old revisions by default. To identify and remove:
# List all disabled snap revisions
snap list --all | awk '/disabled/{print $1, $3}'
# Remove specific revision
snap remove <package-name> --revision=<revision-number>
Important: Requires explicit removal by revision number, not simple package uninstallation.
Documentation Requirements
All maintenance sessions must generate structured logs recording:
System Identification
- Hostname
- OS version
- Kernel information
- Operator identity
Resource States
- Initial disk/memory/CPU usage
- Final disk/memory/CPU usage
- Quantified improvements
Actions Taken
- Specific commands executed
- MB/GB freed per category
- Packages upgraded/removed
Follow-up Recommendations
- Remaining issues
- Future maintenance needs
- Monitoring suggestions
Expected Results
Real-world recovery examples:
- Journal vacuuming: 300-600 MB
- Snap revision cleanup: 500 MB to 2 GB
- Package cache purging: 100-500 MB
- Total potential: 2+ GB in comprehensive sessions
Time Commitment
Typical maintenance session: 15-30 minutes including diagnostics, cleanup, and documentation.