Status Page Gen
v1.0.0Generate a dark-themed static HTML status page summarizing health checks, ping, SSL certs, and uptime for self-hosted services from a JSON config.
⭐ 0· 66·0 current·0 all-time
byNew Age Investments@newageinvestments25-byte
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
OpenClaw
Benign
high confidencePurpose & Capability
The skill's name/description match the included scripts: check_services.py (HTTP + ping), check_certs.py (TLS), history.py (local history), and generate_page.py (HTML). Only minor mismatch: the README describes publishing via the GitHub CLI (`gh`) but the skill does not declare or install `gh` (this is optional in docs, not required to run core functionality).
Instruction Scope
SKILL.md confines the agent to reading a local services.json, running the provided Python scripts, writing local JSON and an HTML file, and optionally scheduling via cron/LaunchAgent. The scripts only reference the service config, local files, and standard system/network calls; they do not read unrelated system files or environment variables.
Install Mechanism
There is no install spec and all code is bundled as plain Python scripts. No downloads, external installers, or archive extraction are used.
Credentials
The skill requires no environment variables or credentials. The docs mention using `gh` to publish a Gist (which would require GitHub authentication) — publishing is optional but could expose internal URLs if used. There are no other unexplained credential requests.
Persistence & Privilege
always is false and the skill does not request persistent platform privileges. The docs suggest scheduling (cron/LaunchAgent) which is normal for monitoring tasks and requires user action/consent; the skill does not modify other skills or system-wide agent settings.
Assessment
This skill appears to be what it claims: it runs local network checks (HTTP, ICMP via the system ping command, and TLS connects), writes a local history JSON and a self-contained HTML file, and can be scheduled with cron/LaunchAgent. Before installing or scheduling: 1) Review assets/services.json to ensure only the hosts you intend are included (these scripts will actively probe every configured host). 2) Be aware that publishing the generated HTML to a public GitHub Gist (documented but not automatic) will expose the page and any service names/URLs it contains — don't publish sensitive internal hostnames/URLs. 3) The scripts invoke the system ping binary and perform outbound network connections; ensure your environment permits that and that you are comfortable with periodic probes. 4) If you plan to serve the HTML from a system webroot (e.g., /var/www/html), check file permissions and that writing to that path is intentional. Overall this skill is internally consistent and does not request credentials or hidden external endpoints.Like a lobster shell, security has layers — review code before you run it.
latestvk97bqt5md57rv08cq86qqr8ng983mnep
License
MIT-0
Free to use, modify, and redistribute. No attribution required.