Ping services and alert when your VPS endpoints go down
Monitors HTTP, TCP and ICMP targets on a schedule and alerts when they become unavailable. Useful for keeping an eye on mission-critical services from a lightweight VPS.
Low blast radius on the evidence available, but it is still third-party code — a quick look at the SKILL.md costs nothing.
It contacts external services. Outbound calls are how data leaves your machine, so it is worth knowing where it connects.
This skill's own description refers to "http"
These permissions are inferred from this listing — the credentials it declares, any maintainer warning, and the operations its own description mentions. ClawVault has not audited this skill's source code. Treat it as a starting point for your own review, not a substitute for one.
PicoClaw does not have a skill-install command. Capabilities come from two places: skill packages, which are SKILL.md directories under workspace/skills/, and built-in tool groups configured in config.json under the tools field, which covers web, mcp, exec, cron and skills. MCP servers are managed through the mcp CLI command group.
mkdir -p workspace/skills/uptime-monitorPicoClaw discovers skills as directories under workspace/skills/. Each one contains a SKILL.md describing the procedure, which the agent loads on demand.
$EDITOR workspace/skills/uptime-monitor/SKILL.mdKeep it short. Sipeed's own skill-creator guidance is explicit that the context window is a shared resource: include only what the model does not already know, and make each paragraph justify its token cost.
$EDITOR config.jsonThe tools field in config.json controls the web, mcp, exec, cron and skills groups. A skill that shells out needs exec enabled; a scheduled one needs cron. Leave filter_sensitive_data on so API keys and tokens are stripped from tool output before it reaches the model.
picoclaw mcpFor capabilities that already exist as an MCP server, the mcp command group manages those entries in your config rather than writing a skill by hand.
Commands follow the official PicoClaw documentation. Placeholders such as <owner> are filled in by the search step, because registry references are publisher-scoped.
PicoClaw filters sensitive values such as API keys and tokens out of tool results before they are sent to the model, controlled by filter_sensitive_data (on by default) and filter_min_length. Because exec grants shell access, enable it only when a skill genuinely needs it.
Deploy OpenClaw, Hermes, or PicoClaw on Bluehost with the right template for the job.
Gives your PicoClaw agent control over system processes. Monitor CPU and memory usage per process, restart crashed services, kill runaway processes and get alerts when resource thresholds are exceeded.
Monitors disk usage across all mounted volumes on your VPS. Sends alerts when usage crosses configurable thresholds, identifies the largest directories consuming space and can trigger cleanup scripts automatically.
Lets your PicoClaw agent manage nginx configuration files, create and enable virtual hosts, test config validity and reload the server — all programmatically. Ideal for automated deployment pipelines.