skills.rest
Nightreaver
NightreaverCOMMUNITY
Explore all skills by this author →
GitHub

ssh_systemctl_disable

Disable a systemd unit on a remote host to prevent boot startup.

6|Updated Apr 17, 2026
Search Tags:#system administration#ssh#remote management#systemd#unit management
One-click install
npx skills add https://github.com/Nightreaver/python-ssh-mcp --skill ssh-systemctl-disable
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: ssh_systemctl_disable
Source: https://github.com/Nightreaver/python-ssh-mcp/tree/main/skills/ssh-systemctl-disable
Command: npx skills add https://github.com/Nightreaver/python-ssh-mcp --skill ssh-systemctl-disable

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill provides the ability to disable a systemd unit on a remote host, preventing it from starting on boot. It's useful for decommissioning services or preventing unauthorized services from running.

Core Features & Use Cases

  • Systemd Unit Disable: Disable a systemd unit so it does not start on boot.
  • Access Control: Hidden unless ALLOW_DANGEROUS_TOOLS=true is set.
  • Non-Disruptive: Does NOT stop the unit in the current boot, use ssh_systemctl_stop for that.
  • Use Case: Decommission a service by disabling and stopping it, or switch from a vendor-provided unit to a custom one before installation.

Quick Start

Use the ssh_systemctl_disable skill to disable the 'nginx.service' on 'web01'.

Frequently Asked Questions about ssh_systemctl_disable

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I disable a systemd unit remotely via SSH so it doesn't start on boot?▼

To disable a systemd unit remotely, you must access the host via SSH with root permissions and run the systemctl disable command. This permanently prevents the specified unit from starting on boot.

Does disabling a systemd service stop it immediately during the current boot?▼

Disabling a systemd service does not stop it during the current boot. It only prevents the unit from starting automatically on future boots, requiring a separate stop command to halt the currently running process.

What permissions are required to disable systemd units on remote hosts?▼

Disabling systemd units on remote hosts requires root access and appropriate SSH permissions. Additionally, the tool is hidden unless the environment variable ALLOW_DANGEROUS_TOOLS is explicitly set to true.

When should I disable a systemd unit instead of stopping it?▼

You should disable a systemd unit when decommissioning a service or replacing a vendor-provided unit with a custom one. Disabling ensures the service will not start on the next boot, whereas stopping only halts it temporarily.

Can I use SSH to permanently decommission a service by preventing it from starting on boot?▼

Yes, you can use SSH to permanently decommission a service by disabling the systemd unit. This action requires root access and prevents the service from starting on boot, effectively decommissioning it across remote hosts.

Why is the remote systemd unit disable tool not showing up in my environment?▼

The remote systemd unit disable tool is hidden by default for safety. You must set the environment variable ALLOW_DANGEROUS_TOOLS to true to access this system administration capability.

Related Skills

Explore More Software Engineering Skills→
NightreaverNightreaver
6

ssh_systemctl_show

Retrieve systemd unit properties from remote hosts via SSH.

Community
Intermediate
bdambrosiobdambrosio
10

mc-close

Close the active user interface in a Minecraft game instance.

Community
Basic
L3DigitalNetL3DigitalNet
6

systemd

Manages systemd services, timers, and sockets on Linux.

Official
Intermediate
NightreaverNightreaver
6

ssh-systemctl-restart

Restart systemd units on remote hosts via SSH with root access.

Community
Intermediate