Pi Admin
ReviewAudited by ClawScan on May 10, 2026.
Overview
This looks like a real Raspberry Pi admin tool, but it can reboot and change the host system, and some high-impact actions do not ask for confirmation as clearly as the documentation claims.
Use this only on the intended Raspberry Pi and prefer the information commands or `--dry-run` first. Do not let an agent run maintenance commands autonomously unless you are comfortable with reboots, package changes, service disabling, and gateway restarts. Review the hardcoded paths/ports/IPs and add explicit confirmations before using it for unattended administration.
Findings (6)
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.
A user or agent may run a maintenance command expecting a final confirmation prompt, but the host could reboot or services could be changed before the user has meaningfully approved it.
This safety claim is not consistently matched by the scripts: reboot uses only a Ctrl+C countdown, restart-gateway has no affirmative confirmation, and optimize applies persistent changes after invocation/sudo. Users may overestimate the amount of built-in approval gating.
**Note:** All maintenance commands require sudo and ask for confirmation before making changes.
Make the documentation and behavior match: require explicit y/N confirmation for every non-dry-run maintenance command, or clearly document which commands act immediately.
The Raspberry Pi or other host could reboot unexpectedly, interrupting running services or active work.
The reboot command proceeds after a countdown without an affirmative confirmation prompt, which is risky if invoked by an agent or in a session where the user cannot interrupt it.
echo "To cancel, press Ctrl+C" ... for i in {10..1}; do ... done ... $SUDO rebootRequire an explicit confirmation such as typing 'reboot' or 'yes', and prefer dry-run behavior unless the user directly requests a reboot.
The gateway service could be interrupted or replaced, and a background process may continue running after the immediate task is done.
The script kills all matching gateway processes and starts a new long-running background process without an explicit confirmation or clear lifecycle management.
pkill -f "clawdis gateway" 2>/dev/null ... pnpm clawdis gateway --port 18789 > /dev/null 2>&1 &
Gate gateway restarts behind explicit user approval, use a service manager where possible, record the PID/log location, and avoid hardcoded paths or ports.
Bluetooth, modem management, local service discovery, or swap behavior could change until manually undone.
These persistent system optimizations are disclosed and include dry-run/undo support, but they still disable services and write system configuration.
$SUDO systemctl disable bluetooth.service ... $SUDO systemctl disable ModemManager.service ... echo "vm.swappiness=10" | $SUDO tee /etc/sysctl.d/99-swappiness.conf
Run `./skill.sh optimize --dry-run` first, confirm each service is safe to disable on your Pi, and keep the undo command available.
If approved, the skill can make system-wide package changes as root.
Privileged package maintenance is expected for a system administration skill, but it gives the command broad authority over the host.
echo "⚠️ This script requires sudo privileges" ... $SUDO apt upgrade -y
Only run privileged maintenance commands on the intended Raspberry Pi, review package changes first, and avoid granting sudo to autonomous invocations.
The skill may be installed or invoked in an unsupported environment, where commands could fail or affect a non-Pi Linux host.
The registry metadata does not declare the Linux/Raspberry Pi command dependencies or OS scope that the scripts clearly rely on.
Required binaries (all must exist): none ... OS restriction: none
Declare required tools and restrict the skill to the intended operating system or hardware environment.