Skill flagged — suspicious patterns detected
ClawHub Security flagged this skill as suspicious. Review the scan results before using.
Server Audit
v1.0.0Reads server hardware, Proxmox/Linux OS info, temperatures, SMART status, ECC errors, RAID, disks, network stats, services, and logs without making changes.
⭐ 0· 100·0 current·0 all-time
bySergey@polumish
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
OpenClaw
Suspicious
medium confidencePurpose & Capability
Name/description (server hardware, SMART, ECC, RAID, logs, Proxmox) align with the commands and prompts in SKILL.md and the reference files — the commands shown are exactly what a read-only server audit would run.
Instruction Scope
Instructions are explicit about only reading state and provide many safe, read-only commands. They request sensitive data (journalctl, dmesg, last/lastb, smartctl output, dmidecode) which is expected for an audit but does mean the skill will collect potentially sensitive logs and user/login info. The skill also instructs the agent to save audit results into a local Obsidian-like path (/DATA/local_database/...), which goes beyond pure remote reading and introduces local persistence of potentially sensitive data.
Install Mechanism
No install spec or external downloads — instruction-only skill with no code files. Low install risk because nothing is fetched or written during installation.
Credentials
SKILL.md assumes the ability to ssh as root@HOST (and to run root-level commands like dmidecode, journalctl, ipmitool, storcli, smartctl) but the registry metadata declares no required credentials or auth mechanism. The skill does not declare how SSH credentials/keys are provided or whether private keys will be used. Hard-coded local save paths (/DATA/local_database/...) are also assumed without justification and may expose audit outputs to other systems if that path is synced/backed-up.
Persistence & Privilege
always:false (good). Skill does not install or claim persistent presence, but it explicitly instructs saving audit reports into a local vault path — this creates persistent local artifacts containing sensitive findings. The skill does not modify other skills or system-wide configuration.
What to consider before installing
This skill appears to genuinely perform a read-only server audit, but pay attention to three practical risks before installing/using it: (1) Credentials: the prompts expect root SSH access yet the skill declares no required credential fields — decide how you will supply SSH keys/passwords and avoid giving access to unknown agents. (2) Sensitive output persistence: the skill saves audit reports to a hard-coded local path (/DATA/local_database/…) which could be synced or accessible to others — ensure that path is secure or change it before use. (3) Scope & privacy: the commands collect logs and login history (journalctl, dmesg, lastb) which may contain secrets/PII; only run against hosts you control or have explicit permission to audit. Recommended actions: test on a non-production host first, require the human operator to supply the target and credentials at runtime, review and sanitize saved reports, and avoid enabling autonomous invocation for this skill unless you trust the environment and the skill owner (owner is unknown). If the platform supports it, ask the skill author to declare required credential inputs (SSH key or credential handle) and to make the save path configurable.Like a lobster shell, security has layers — review code before you run it.
latestvk97dg41aft1kevffc9ha75fxrn833kev
License
MIT-0
Free to use, modify, and redistribute. No attribution required.