Ops Dashboard
v1.0.1Gather operational signals (disk usage, git status, recent commits, and resources) so you can answer "How is the Clawdy infrastructure doing?" without manually running multiple checks.
⭐ 1· 1.8k·9 current·10 all-time
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
OpenClaw
Suspicious
medium confidencePurpose & Capability
The code implements the claimed features (disk usage, git status/log, load averages, top directories). However the skill metadata declares no required binaries while the implementation invokes the 'git' CLI via subprocess.run. If 'git' is absent the script will raise FileNotFoundError (not caught), which is a mismatch between claimed requirements and actual runtime needs.
Instruction Scope
SKILL.md instructs running a CLI and limiting work to a workspace path, and the implementation follows that scope (it reads file sizes and runs git commands locally). Minor mismatches: SKILL.md references df output for '/', '/mnt/ramdisk' and other mounted tiers, but the script calls shutil.disk_usage on the provided workspace path (it does not enumerate system mounts or call 'df'). SKILL.md also uses a different path pattern (skills/ops-dashboard/...) than the manifest/files (scripts/ops_dashboard.py), which may confuse users or packaging.
Install Mechanism
No install spec (instruction-only plus included scripts). Nothing is downloaded or installed automatically by the skill bundle.
Credentials
The skill requests no environment variables or credentials and the implementation does not access external secrets. It runs local filesystem and git commands only.
Persistence & Privilege
The skill does not request persistent 'always' inclusion and does not modify other skills or global agent settings. Autonomous invocation remains the platform default and is not, by itself, a problem here.
What to consider before installing
This skill's code appears to match its stated purpose and does not contact external services, but there are a few things to check before installing or running it:
- Confirm git is available on any host where you run the script. The code calls the 'git' command but the skill metadata does not declare git as a required binary; if git is missing the script may crash. Consider adding a check for git or declaring it as a dependency.
- Note the small documentation/manifest mismatches (SKILL.md paths and some wording about 'df' and specific mount points) — make sure you run the script from the correct location (the packaged path is scripts/ops_dashboard.py) and that the behavior matches your expectations.
- The script walks the workspace and sums file sizes; on very large repositories this can be slow and I/O heavy. Run in a sandbox or with a representative workspace first.
- The script runs only local commands (git, filesystem calls, os.getloadavg) and does not transmit data. If you are concerned about sensitive filenames/sizes, inspect the code yourself or run it in a restricted environment.
- Because the metadata and docs are slightly inconsistent, prefer to review the source before granting broader trust; run the included unit tests in a safe environment to validate behavior.
If you want a stronger assurance, request the author/publisher to: (1) declare 'git' as a required binary, (2) correct the SKILL.md path and disk/mount wording to match the implementation, and (3) add a graceful check/catch for missing 'git' to avoid crashes.Like a lobster shell, security has layers — review code before you run it.
latestvk973q0c8z6r6817r051gmw1axh80jrh0
License
MIT-0
Free to use, modify, and redistribute. No attribution required.
