SLA Monitor
PassAudited by ClawScan on May 1, 2026.
Overview
This is a coherent instruction-only SLA monitoring guide, with only expected optional setup items like running a monitoring container and using a Slack webhook for alerts.
This skill appears safe as an instruction-only monitoring template. Before installing or using it, be careful with the optional Docker command, protect any Slack webhook or alerting credentials, and review public status page content so you do not disclose sensitive operational details.
Findings (2)
Artifact-based informational review of SKILL.md, metadata, install specs, static scan signals, and capability signals. ClawScan does not execute the skill or run runtime probes.
If you run this command, it will start a long-running monitoring service on the host using a third-party container image.
This optional self-hosted monitoring command would pull and run a Docker container, expose port 3001, create a volume, and keep the service restarting; this is aligned with the monitoring purpose but is executable and persistent if used.
docker run -d --restart=always -p 3001:3001 -v uptime-kuma:/app/data --name uptime-kuma louislam/uptime-kuma:1
Run it only on an intended host, verify the container image and version, review the exposed port and volume, and know how to stop or remove the container.
If a real Slack webhook is exposed or committed into a shared config, others may be able to send messages to that Slack channel.
The alert configuration template expects a Slack webhook secret for notifications; this is expected for Slack alerting, but a real webhook grants posting ability to the configured Slack destination.
webhook: "${SLACK_WEBHOOK}"Store the webhook securely, use a channel-specific or least-privilege integration, and avoid committing real webhook values into generated files.