Watchdog Heartbeat
v1.0.0Monitor service health, heartbeat freshness, stuck workflows, and trigger recovery or degraded mode. Use on: high-frequency schedule, after system startup, w...
⭐ 0· 51·0 current·0 all-time
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
OpenClaw
Benign
high confidencePurpose & Capability
The name/description (monitor heartbeats, stuck workflows, recovery recommendations) match the SKILL.md inputs and outputs. All required inputs (service_list, health_endpoints, heartbeat_records, workflow_status_records, restart_records) are appropriate and expected for this purpose.
Instruction Scope
SKILL.md is a self-contained specification for evaluating health and producing recommendations. It does not instruct the agent to read unrelated system files, access extraneous environment variables, or call unexpected external endpoints. It only declares the inputs the skill expects.
Install Mechanism
No install spec or code files are present; this is instruction-only and therefore does not write code to disk or download artifacts.
Credentials
The skill requests no environment variables, credentials, or config paths. The declared inputs are reasonable for the stated purpose and there are no disproportionate secret/credential requests.
Persistence & Privilege
The skill is not always-enabled and has no install footprint. However, it returns actionable recommendations (restart, escalate, degraded_mode). Consider that if the agent invoking this skill has autonomous execution privileges (the platform default), downstream automation could act on those recommendations (e.g., trigger restarts) — that is an operational risk to manage outside the skill.
Assessment
This skill is a specification for monitoring and recovery recommendations and by itself does not access your system or secrets. Before installing: (1) Confirm where the declared inputs (heartbeat and workflow records, health endpoints, restart history) will come from and ensure they are accurate and read-only for the skill. (2) Decide whether automatic actions (restart, degraded_mode, escalate) should require human confirmation — the skill returns recommendations but an agent with execution rights could act on them. (3) Ensure the agent or environment that supplies inputs/acts on outputs follows least privilege (e.g., separate runbooks/credentials for restarts) to avoid accidental or automated disruptive changes. (4) If you plan to wire this into automated recovery, add safeguards (rate limits, approvals, escalation policies) so recommendations cannot cause cascading restarts.Like a lobster shell, security has layers — review code before you run it.
latestvk97591b35x47y95q8yw71cyv4d83q84n
License
MIT-0
Free to use, modify, and redistribute. No attribution required.