remote-system-maintenance

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.

25 stars

Best use case

remote-system-maintenance is best used when you need a repeatable AI agent workflow instead of a one-off prompt.

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.

Teams using remote-system-maintenance should expect a more consistent output, faster repeated execution, less prompt rewriting.

When to use this skill

  • You want a reusable workflow that can be run more than once with consistent structure.

When not to use this skill

  • You only need a quick one-off answer and do not need a reusable workflow.
  • You cannot install or maintain the underlying files, dependencies, or repository context.

Installation

Claude Code / Cursor / Codex

$curl -o ~/.claude/skills/remote-system-maintenance/SKILL.md --create-dirs "https://raw.githubusercontent.com/ComeOnOliver/skillshub/main/skills/aiskillstore/marketplace/2389-research/remote-system-maintenance/SKILL.md"

Manual Installation

  1. Download SKILL.md from GitHub
  2. Place it in .claude/skills/remote-system-maintenance/SKILL.md inside your project
  3. Restart your AI agent — it will auto-discover the skill

How remote-system-maintenance Compares

Feature / Agentremote-system-maintenanceStandard Approach
Platform SupportNot specifiedLimited / Varies
Context Awareness High Baseline
Installation ComplexityUnknownN/A

Frequently Asked Questions

What does this skill do?

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.

Where can I find the source code?

You can find the source code on GitHub using the link provided at the top of the page.

SKILL.md Source

# 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:

1. **Package Cache Refresh** - `apt update` to sync package lists
2. **System Upgrades** - `apt upgrade` for security and bug fixes
3. **Orphan Removal** - `apt autoremove` to clean unused dependencies
4. **Cache Purging** - `apt clean` to reclaim package cache space
5. **Journal Pruning** - `journalctl --vacuum-time=7d` to limit log retention
6. **Snap Revision Cleanup** - Remove disabled snap revisions (see below)
7. **Temporary Directory Assessment** - Review `/tmp` and `/var/tmp` for cleanup opportunities

## Snap Revision Cleanup Technique

Snap keeps old revisions by default. To identify and remove:

```bash
# 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:

1. **System Identification**
   - Hostname
   - OS version
   - Kernel information
   - Operator identity

2. **Resource States**
   - Initial disk/memory/CPU usage
   - Final disk/memory/CPU usage
   - Quantified improvements

3. **Actions Taken**
   - Specific commands executed
   - MB/GB freed per category
   - Packages upgraded/removed

4. **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.

Related Skills

analyzing-system-throughput

25
from ComeOnOliver/skillshub

This skill enables Claude to analyze and optimize system throughput. It is triggered when the user requests throughput analysis, performance improvements, or bottleneck identification. The skill uses the `throughput-analyzer` plugin to assess request throughput, data throughput, concurrency limits, queue processing, and resource saturation. Use this skill when the user mentions "analyze throughput", "optimize performance", "identify bottlenecks", or asks about system capacity. It helps determine limiting factors and evaluate scaling strategies.

reminder-system-creator

25
from ComeOnOliver/skillshub

Reminder System Creator - Auto-activating skill for Business Automation. Triggers on: reminder system creator, reminder system creator Part of the Business Automation skill category.

building-recommendation-systems

25
from ComeOnOliver/skillshub

This skill empowers Claude to construct recommendation systems using collaborative filtering, content-based filtering, or hybrid approaches. It analyzes user preferences, item features, and interaction data to generate personalized recommendations. Use this skill when the user requests to build a recommendation engine, needs help with collaborative filtering, wants to implement content-based filtering, or seeks to rank items based on relevance for a specific user or group of users. It is triggered by requests involving "recommendations", "collaborative filtering", "content-based filtering", "ranking items", or "building a recommender".

orchestrating-multi-agent-systems

25
from ComeOnOliver/skillshub

Execute orchestrate multi-agent systems with handoffs, routing, and workflows across AI providers. Use when building complex AI systems requiring agent collaboration, task delegation, or workflow coordination. Trigger with phrases like "create multi-agent system", "orchestrate agents", or "coordinate agent workflows".

box-cloud-filesystem

25
from ComeOnOliver/skillshub

Cloud filesystem operations via Box CLI. Use when the user mentions Box, cloud files, cloud storage, uploading to the cloud, sharing files, document management, or syncing project files offsite. Trigger with "upload to box", "save to cloud", "pull from box", "search my box files", "share this file", "box sync", "cloud backup", or "box filesystem".

create-design-system-rules

25
from ComeOnOliver/skillshub

Generates custom design system rules for the user's codebase. Use when user says "create design system rules", "generate rules for my project", "set up design rules", "customize design system guidelines", or wants to establish project-specific conventions for Figma-to-code workflows. Requires Figma MCP server connection.

filesystem-context

25
from ComeOnOliver/skillshub

This skill should be used when the user asks to "offload context to files", "implement dynamic context discovery", "use filesystem for agent memory", "reduce context window bloat", or mentions file-based context management, tool output persistence, agent scratch pads, or just-in-time context loading.

gtm-developer-ecosystem

25
from ComeOnOliver/skillshub

Build and scale developer-led adoption through ecosystem programs. Use when deciding open vs curated ecosystems, building developer programs, scaling platform adoption, or designing student program pipelines.

Filesystem Navigation

25
from ComeOnOliver/skillshub

Guidelines for systematically exploring and understanding directory structures.

windows-remote-desktop-connection-doctor

25
from ComeOnOliver/skillshub

Diagnose Windows App (Microsoft Remote Desktop / Azure Virtual Desktop / W365) connection quality issues on macOS. Analyze transport protocol selection (UDP Shortpath vs WebSocket), detect VPN/proxy interference with STUN/TURN negotiation, and parse Windows App logs for Shortpath failures. This skill should be used when VDI connections are slow, when transport shows WebSocket instead of UDP, when RDP Shortpath fails to establish, or when RTT is unexpectedly high.

../../../engineering/interview-system-designer/SKILL.md

25
from ComeOnOliver/skillshub

No description provided.

C-Level Advisory Ecosystem

25
from ComeOnOliver/skillshub

A complete virtual board of directors for founders and executives.