Linux & service basics
PassAudited by ClawScan on May 1, 2026.
Overview
This instruction-only skill is coherent and safety-scoped, but users should review any suggested service, permission, or persistence changes before running them.
This skill appears safe to install as an instruction-only Linux troubleshooting guide. Treat any generated shell commands as administrative changes: review them, confirm they match your service and paths, and ask for rollback steps before running restarts, permission changes, Nginx reloads, or systemd service creation.
Findings (2)
Artifact-based informational review of SKILL.md, metadata, install specs, static scan signals, and capability signals. ClawScan does not execute the skill or run runtime probes.
Running the suggested commands could change server configuration or service state, so the user should understand and approve them first.
The skill may provide shell commands that restart services, adjust permissions, or reload Nginx. This is purpose-aligned for service triage and is explicitly gated on user request and safety.
If explicitly requested and safe: exact shell commands to apply the fix.
Keep the read-only default, review proposed commands before execution, and require explicit approval for restarts, permission changes, reloads, or configuration edits.
A persistent service can keep running after reboot and affect the server until removed or disabled.
Creating a systemd service introduces persistence across reboots. Here it is disclosed as a user-invoked troubleshooting/setup use case, not hidden background behavior.
Create a systemd service for this script and make it survive reboots.
Only create persistent services when explicitly needed, include rollback commands such as disable/remove service files, and verify the service runs under the least-privileged appropriate user.