SKILLEMALL.ai
GitHub ↗ RU Sign in

CC claude-watchdog

Monitor the Claude API for outages and latency spikes with rich Telegram alerts. Status monitoring, latency probes, and automatic recovery notifications.

Not recommendedcritical or high security findings
modbender/skill-library-mcp Agent Skills author: modbender MIT 4 files · 1 script body ≈ 1 259 tokens Open the sourcegithub.com↗ analyzed 2 d ago

Monitor the Claude API for outages and latency spikes with rich Telegram alerts.

As a process C 53/100 · Has gaps — weak spots: result and completion, when it triggers, failures and branches

IntegrationTelegramAI and agentstype and topics are labelled automatically from the skill text
Runs in: OpenClaw Claude / Claude Code ChatGPT / Codex Gemini CLI Cursor GitHub Copilot / VS Code Qwen Code Kimi Code CLI Z.ai (GLM) DeepSeek (Deep Code) Mistral Vibe LangChain (deepagents) Goose OpenCode
JSON
Technical rating
C
71/100
safety, quality, tests
Safety 60%
69
Quality 40%
74
Run on models
none yet
Process rating
C
53/100
Has gaps
Result and completion w 14
0
Failures and branches w 10
0
When it triggers w 12
20
the three weakest of ten parameters · all ten

What is at stake

The skill contains fragments that, in the wrong hands, cost money or data. Below: what the installer risks and what the author should do.

Dangerous commands
If you install

The skill contains commands that delete files, rewrite disks or execute code fetched from the network. The agent may run them without asking if it believes the instructions require it.

For the author

Replace destructive commands with safe equivalents that ask for confirmation, scope them to one folder, and stop piping curl into a shell: pin a version and a checksum.

How to improve

  1. Address the high-severity findings: each costs 18 safety points. If one is a false positive, add the rule id to guard.allow in spec.yaml.
  2. Say in the description WHEN to use the skill ("use when…", example requests): that is the agent's main cue.
For the model run — optional
  • Your own cases (evals/evals.json, 4–6 real requests with expected answers): the full check would then run those instead of a model-drafted suite.
  • A spec.yaml with trigger phrases and assertions — a behaviour contract for CI; `skilltest init` writes a template.

Guard findings · 10

  • high Dangerous commands cmd-persistence scripts/setup.sh:200
    Persistence mechanism (cron / launchd / scheduled task / autorun registry)
    } | crontab -
Medium and low: 9
  • medium Dangerous commands cmd-persistence scripts/setup.sh:25
    Persistence mechanism (cron / launchd / scheduled task / autorun registry) (detector / deny-list definition)
    crontab -l 2>/dev/null | grep -v 'claude-watchdog' | crontab -
    detector
  • low Exfiltration exfil-webhook-url scripts/latency-probe.py:100
    Webhook / callback URL commonly used for exfiltration (verify the destination) (placeholder value)
    url = f"https://api.telegram.org/bot{BOT_TOKEN}/sendMessage"
    placeholder
  • low Dangerous commands cmd-cron-mention scripts/setup.sh:24
    Mentions editing / listing crontab
    if crontab -l 2>/dev/null | grep -q 'claude-watchdog'; then
  • low Dangerous commands cmd-cron-mention scripts/setup.sh:25
    Mentions editing / listing crontab
    crontab -l 2>/dev/null | grep -v 'claude-watchdog' | crontab -
  • low Exfiltration exfil-webhook-url scripts/setup.sh:77
    Webhook / callback URL commonly used for exfiltration (verify the destination) (placeholder value)
    echo "  2. Visit https://api.telegram.org/bot<TOKEN>/getUpdates"
    placeholder
  • low Exfiltration exfil-webhook-url scripts/setup.sh:177
    Webhook / callback URL commonly used for exfiltration (verify the destination) (placeholder value)
    -X POST "https://api.telegram.org/bot${bot_token}/sendMessage" \
    placeholder
  • low Dangerous commands cmd-cron-mention scripts/setup.sh:195
    Mentions editing / listing crontab
    crontab -l 2>/dev/null | grep -v 'claude-watchdog' | grep -v 'status-check\.py' | grep -v 'latency-probe\.py' > /tmp/crontab-clean || true
  • low Exfiltration exfil-webhook-url scripts/status-check.py:79
    Webhook / callback URL commonly used for exfiltration (verify the destination) (placeholder value)
    url = f"https://api.telegram.org/bot{BOT_TOKEN}/sendMessage"
    placeholder
  • low Exfiltration exfil-webhook-url SKILL.md:57
    Webhook / callback URL commonly used for exfiltration (verify the destination) (placeholder value)
    2. **Telegram Chat ID** — send a message to your bot, then check `https://api.telegram.org/bot<TOKEN>/getUpdates`
    placeholder

Files scanned: 4. Evidence is masked. Grey chips explain why severity was lowered.

Against the Agent Skills spec

  • warning description-no-when description does not say WHEN to use the skill (no "use when")
  • note frontmatter-key unknown frontmatter key "homepage"

Process rating: all ten parameters 53/100

  • 0Result and completion. Does not say what the result is
  • 0Failures and branches. Linear process with no failure handling
  • 20When it triggers. No condition that starts the skill
  • 30Running it twice. 7 mutating operations with no state check
  • 60Tools and files. Uses tools (bash, python) that frontmatter does not declare
  • 70Inputs and preconditions. Inputs and preconditions are listed
  • 100Steps. 18 steps
  • 100Consistency. Name and required fields are in place
  • 100Execution cost. Instruction body is 1259 tokens
  • 100Progress reporting. Reports progress
  • medium Safety rules and hard prohibitions inside a skill: they belong in the system prompt, here they protect nothing

Everything here is measured from the skill text rather than judged by a model, so the numbers are checkable. A parameter weighs more when it is a more common reason for the process to stall.

Quality signals

  • +5Description has no quoted example phrases that should trigger the skill
  • +4Description does not say when NOT to use the skill (false activations)
  • +3Output format is not stated: the model decides each time
  • +1No license
  • +2Single-language instructions
  • +3Description length 153: enough signal without eating the budget
  • +4Structure: 11 headings
  • +3Step-by-step instructions: 18 items
  • +4Has examples (8 code blocks)
  • +3All 3 scripts are documented

Quality base 70; lint remarks subtract, signals add up to 100. Result: 74.