shutdown

Safe shutdown/reboot workflow for local or remote machines. Use when the user asks to power off, restart, schedule shutdown, cancel shutdown, or perform pre-...

Security Scan

The skill's instructions, requirements, and scope are coherent for a shutdown/reboot helper: it gives platform-appropriate commands, requires explicit confirmations, and requests no unrelated credentials or installs.

Purpose & Capability

The name/description (shutdown/reboot workflows) matches the content: the SKILL.md lists platform-specific shutdown/reboot/schedule/cancel commands and pre-checks that are reasonable and expected for this purpose.

Instruction Scope

Instructions include privileged system commands (sudo shutdown, systemctl, Windows shutdown) and read-only pre-checks (who, uptime). The doc explicitly requires explicit user confirmation before any state-changing command, warns about session disconnects, and constrains scope to single targets — these safety controls are appropriate. Note: the skill assumes the agent can run shell/PowerShell commands; ensure the agent will not run commands autonomously without confirmation.

Install Mechanism

Instruction-only skill with no install spec and no code files — nothing will be downloaded or written during install, minimizing install-time risk.

Credentials

No environment variables, credentials, or config paths are requested. This is proportionate to a local/remote shutdown helper (no secret access requested).

Persistence & Privilege

always is false and the skill does not request persistent or cross-skill configuration changes. The skill can be invoked by the agent normally; that autonomous invocation is standard and not excessive by itself.

Assessment

This skill appears coherent for safely performing shutdown/reboot tasks. Before installing, confirm you are comfortable letting the agent present and run privileged commands (it uses sudo / Windows shutdown). Verify the agent will always require the explicit confirmation pattern the SKILL.md mandates — if you do not want any risk of accidental shutdowns, keep autonomous invocation off or require manual invocation only. If you plan to use it against remote hosts, ensure SSH/remote credentials and host targets are handled out-of-band (the skill does not request credentials) and test the flow in a safe environment first. If anything about confirmation or target selection is unclear, ask the skill author to clarify/strengthen the confirmation step.

Execute system shutdown and reboot actions safely, with explicit confirmation and connection-safety checks.

Core Rules

• Never run power actions without explicit user confirmation.
• Always confirm target machine and action: shutdown, reboot, schedule, or cancel.
• For remote hosts, warn about session disconnect before executing.
• Prefer delayed shutdown (+1 minute or equivalent) so cancellation remains possible.
• If user asks for immediate action, still echo the exact command and require final confirmation.
• 中文用户常见意图词（如“关机”“重启”“稍后关机”“取消关机”）按同一安全流程处理，不要省略确认步骤。

Workflow

1. Clarify intent and target

Collect and confirm:

• Target: local machine or remote host
• Action: shutdown or reboot
• Timing: now or scheduled time
• Scope: current machine only (never assume cluster/fleet-wide)

If ambiguous, ask one concise question before running commands.

2. Run pre-checks (read-only)

Use only relevant checks:

• Linux: who, uptime, systemctl is-system-running (if systemd exists)
• macOS: who, uptime
• Windows (PowerShell): query user, Get-Uptime

If long-running/critical work may be interrupted, report risk and ask whether to continue.

3. Choose platform command

Linux (systemd)

# shutdown now
sudo shutdown -h now

# reboot now
sudo shutdown -r now

# schedule shutdown in 1 minute
sudo shutdown -h +1

# cancel scheduled shutdown
sudo shutdown -c

Fallback where needed:

sudo systemctl poweroff
sudo systemctl reboot

macOS

# shutdown now
sudo shutdown -h now

# reboot now
sudo shutdown -r now

# schedule shutdown in 10 minutes
sudo shutdown -h +10

# cancel scheduled shutdown
sudo killall shutdown

Windows (PowerShell / cmd)

# shutdown now
shutdown /s /t 0

# reboot now
shutdown /r /t 0

# shutdown in 60 seconds
shutdown /s /t 60

# cancel scheduled shutdown
shutdown /a

4. Confirmation pattern (required)

Before executing state-changing commands, present:

• Exact command to run
• Expected impact (session disconnect, process termination)
• Cancellation path (if scheduled)

Require the user to reply with a clear confirmation (for example: yes, run it). 中文确认示例：确认执行、是，立即执行。

5. Post-action verification

For scheduled actions, verify and report pending state when possible:

• Linux/macOS: show relevant shutdown scheduling output
• Windows: confirm command exit output

After reboot requests, explain that reconnect checks should include:

• Host reachable
• OpenClaw services/processes healthy
• Required ports/listeners restored

Safety Boundaries

• Do not chain shutdown with destructive cleanup unless user explicitly asks.
• Do not apply shutdown commands to multiple hosts automatically.
• If insufficient privileges, report exact permission error and request elevation approval.
• If command support differs by distro/version, prefer the safest equivalent and state the substitution.

ClawHub Publish Notes

If this skill is published to clawhub.ai, keep updates semver and changelog-driven, and avoid embedding environment-specific hostnames, tokens, or private infrastructure details.