Uptime Checker
v1.0.0Lightweight URL uptime checker and response time monitor. Check if websites and APIs are up, measure response times, track history, and detect SSL issues. Us...
⭐ 0· 162·0 current·0 all-time
byJohn Wang@johnnywang2001
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
OpenClaw
Benign
high confidencePurpose & Capability
Name/description align with included Python script: it performs HTTP(S) checks, measures response time, follows redirects, validates SSL, and tracks history. No unrelated credentials, binaries, or services are requested.
Instruction Scope
SKILL.md instructs running the bundled script with CLI flags; the script only reads URLs from arguments or a provided file and reads/writes a local history file. It does not attempt to scan other parts of the filesystem, exfiltrate data to third parties, or access unspecified environment variables.
Install Mechanism
No install spec is provided and the skill is instruction-only aside from the included Python script. The script uses only the Python standard library (urllib, ssl, json, pathlib), so no external packages or downloads are required.
Credentials
The skill requests no environment variables or credentials, which is appropriate. Caution: the CLI supports custom headers (e.g., Authorization) and these will be sent to target endpoints if supplied; the tool also writes a local history file (default uptime_history.json) which could contain result metadata. Ensure you don't pass secrets via --header unless intended and protect the history file if it will contain sensitive target metadata.
Persistence & Privilege
The skill is not always-enabled and does not modify other skills or global agent settings. It does persist check results to a local history file when --save is used, which is expected behavior for a monitor tool.
Assessment
This skill appears coherent and implements a simple uptime checker in pure Python. Before installing/using: (1) review and run the included script locally to confirm behavior; (2) be careful when supplying Authorization or other sensitive headers via --header (those are sent to the checked URLs); (3) note the default history file (uptime_history.json) is written to the current directory—restrict filesystem permissions if that matters; (4) avoid --no-verify-ssl unless you trust the endpoint (it disables SSL checks). If you need the agent to run this skill autonomously, consider where it will run and what URLs/headers it will be given.Like a lobster shell, security has layers — review code before you run it.
latestvk97f32h8y3yjn8afxs3e5s8d2182wa4m
License
MIT-0
Free to use, modify, and redistribute. No attribution required.