Agent Skills › nixopus/nixopus › machine-ops

machine-ops

GitHub

提供机器实例生命周期管理、指标监控及自动化诊断功能，用于排查服务器健康问题和执行备份操作。

api/skills/machine-ops/SKILL.md nixopus/nixopus

Trigger Scenarios

调查服务器健康状况管理机器状态（重启/暂停）分析性能指标异常执行机器备份

Install

npx skills add nixopus/nixopus --skill machine-ops -g -y

More Options

Non-standard path

npx skills add https://github.com/nixopus/nixopus/tree/master/api/skills/machine-ops -g -y

Use without installing

npx skills use nixopus/nixopus@machine-ops

指定 Agent (Claude Code)

npx skills add nixopus/nixopus --skill machine-ops -a claude-code -g -y

安装 repo 全部 skill

npx skills add nixopus/nixopus --all -g -y

预览 repo 内 skill

npx skills add nixopus/nixopus --list

SKILL.md

Frontmatter

{
    "name": "machine-ops",
    "metadata": {
        "version": "1.0"
    },
    "description": "Machine-level diagnostic layers, lifecycle management (restart\/pause\/resume), metrics analysis, and backup operations. Load when investigating server health or managing machine state."
}

Machine Operations

Lifecycle Management

You can check and control the machine instance state:

get_machine_lifecycle_status → current state (Running, Paused, Stopped), PID, uptime
restart_machine → restart the instance (requires user approval)
pause_machine → pause the instance (requires user approval)
resume_machine → resume a paused instance (requires user approval)

Always check get_machine_lifecycle_status before performing restart/pause/resume.

Metrics & Events

get_machine_metrics → historical time-series metrics (CPU, memory, disk, network)
get_machine_metrics_summary → summarized averages, peaks, and trends
get_machine_events → lifecycle events (restarts, failures, state changes)

Use metrics for trend analysis and incident correlation. Use get_machine_stats for a point-in-time snapshot.

Backups

get_backup_schedule → current backup schedule configuration
update_backup_schedule → modify backup frequency, retention, timing
list_machine_backups → list available backups with timestamps and status
trigger_machine_backup → create an immediate backup (requires approval)

Diagnostic Layers (IN ORDER, stop on root cause)

get_servers_ssh_status → reachable?
get_machine_stats → CPU, RAM, disk, load, uptime
Anomalies: mem>90% → host_exec "ps aux --sort=-%mem | head -20". disk>85% → "du -sh /var/lib/docker/* 2>/dev/null | sort -rh | head -10". cpu>80% → "ps aux --sort=-%cpu | head -20". load>2x cores → overloaded.
Docker → host_exec "systemctl status docker --no-pager", "docker info 2>&1 | head -30"
System logs → host_exec "dmesg | tail -30", "journalctl -u docker --since '30 min ago' --no-pager | tail -50"
Proxy/domain: follow domain-tls-routing skill. Caddy status/logs/validate via host_exec. For domain CRUD or reachability checks, defer to Infrastructure Agent.
Network → host_exec "ss -tlnp"
Cleanup → host_exec "docker system df"

Root cause: bold summary, evidence in code block, fix in 1-2 sentences. No anomalies: report healthy with key metrics.