How do I install the Linux Services skill?

Run npx skillmds@latest add majiayu000/linux-services in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

What does the Linux Services skill do?

Systemd service management and log access It is listed under Coding & Dev Tools on SkillMD.

Is Linux Services safe to use?

This skill has not completed SkillMD's automated safety review yet. Independent scanners report: SkillSpector: PASS, Skill Scanner: PASS. Capability flags: docs only. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Linux Services?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Linux Services free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Linux Services?

majiayu000 (@majiayu000) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Linux Services by majiayu000 — Agent Skill

Name: Linux Services
Rating: 4.666666666666667 (3 reviews)
Author: majiayu000

File contents

Linux Services Skill

Manage systemd services and access logs safely.

See also: Shared Conventions | Safety Guidelines

Purpose

Check service status, view logs, and restart services when needed.

Commands

Service Status

systemctl status <service>
systemctl is-active <service>
systemctl is-enabled <service>
systemctl list-units --type=service --state=running

Service Control

systemctl start <service>
systemctl stop <service>
systemctl restart <service>
systemctl reload <service>

Log Access

journalctl -u <service> --no-pager -n 200
journalctl -u <service> --since "1 hour ago" --no-pager
journalctl -u <service> -f  # follow

Service Restart Protocol

Before restarting any service:

Capture current status
```
systemctl status myapp
```
Capture recent logs
```
journalctl -u myapp --no-pager -n 50
```
Present findings to user
Restart (only after acknowledgment)
```
systemctl restart myapp
```
Verify service started
```
systemctl status myapp
```

Workflow: Diagnose Service Issues

# 1. Check if service is running
systemctl is-active myapp

# 2. Get detailed status
systemctl status myapp

# 3. Check recent logs for errors
journalctl -u myapp --no-pager -n 100 | grep -i error

# 4. Check when it last started
systemctl show myapp --property=ActiveEnterTimestamp

Workflow: Safe Restart

# 1. Pre-restart state
systemctl status myapp
journalctl -u myapp --no-pager -n 20

# 2. Restart
systemctl restart myapp

# 3. Verify
sleep 2
systemctl status myapp
journalctl -u myapp --since "1 minute ago" --no-pager

Policies

Capture state before restart - always log pre-restart status
Verify after restart - confirm service is healthy
No blind restarts - understand why restart is needed
Critical services - extra caution with database, auth, networking services
Report any failed restarts with full log output

---name: linux-servicesdescription: Systemd service management and log access--- # Linux Services Skill Manage systemd services and access logs safely. > **See also**: [Shared Conventions](../shared/CONVENTIONS.md) | [Safety Guidelines](../shared/SAFETY.md) ## Purpose Check service status, view logs, and restart services when needed. ## Commands ### Service Status ```bash systemctl status <service> systemctl is-active <service> systemctl is-enabled <service> systemctl list-units --type=service --state=running ``` ### Service Control ```bash systemctl start <service> systemctl stop <service> systemctl restart <service> systemctl reload <service> ``` ### Log Access ```bash journalctl -u <service> --no-pager -n 200 journalctl -u <service> --since "1 hour ago" --no-pager journalctl -u <service> -f # follow ``` ## Service Restart Protocol **Before restarting any service:** 1. **Capture current status** ```bash systemctl status myapp ``` 2. **Capture recent logs** ```bash journalctl -u myapp --no-pager -n 50 ``` 3. **Present findings** to user 4. **Restart** (only after acknowledgment) ```bash systemctl restart myapp ``` 5. **Verify service started** ```bash systemctl status myapp ``` ## Workflow: Diagnose Service Issues ```bash # 1. Check if service is running systemctl is-active myapp # 2. Get detailed status systemctl status myapp # 3. Check recent logs for errors journalctl -u myapp --no-pager -n 100 | grep -i error # 4. Check when it last started systemctl show myapp --property=ActiveEnterTimestamp ``` ## Workflow: Safe Restart ```bash # 1. Pre-restart state systemctl status myapp journalctl -u myapp --no-pager -n 20 # 2. Restart systemctl restart myapp # 3. Verify sleep 2 systemctl status myapp journalctl -u myapp --since "1 minute ago" --no-pager ``` ## Policies - **Capture state before restart** - always log pre-restart status - **Verify after restart** - confirm service is healthy - **No blind restarts** - understand why restart is needed - **Critical services** - extra caution with database, auth, networking services - Report any failed restarts with full log output

Frequently asked questions

Linux Services