FC Agent Ops Kit
Production-grade health monitoring, alerting, and service management for OpenClaw agents. Monitor URLs, auto-restart services, get Telegram alerts, track uptime.
As a process C 53/100 · Has gaps — weak spots: result and completion, when it triggers, consistency
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.
The files contain someone else's key or token. If it is live, your agent will call third-party services under a stranger's identity; if it was revoked, the skill's scripts simply fail. Such a key often arrives with the author's whole workspace, personal data included.
The key is visible to everyone who downloaded the skill and has likely been copied by catalog-scanning bots already. Revoke it now, check bills and access logs, then reissue.
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.
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
- Remove the critical guard findings (secrets, dangerous commands, hidden instructions): while they stand the skill is blocked and cannot grade above F.
- Say in the description WHEN to use the skill ("use when…", example requests): that is the agent's main cue.
- The SKILL.md body is over 5,000 tokens: move reference detail into references/ and load it when needed.
- 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
-
critical Secrets in code
secret-telegram-botSKILL.md:428Telegram bot token (quoted — discussed, not commanded)3. Copy the bot token (looks like `1102…Hdq…`)
quoted -
high Dangerous commands
cmd-persistenceSKILL.md:110Persistence mechanism (cron / launchd / scheduled task / autorun registry)(crontab -l 2>/dev/null; echo "*/5 * * * * ~/.agent-ops/scripts/health-check.sh >> ~/.agent-ops/logs/cron.log 2>&1") | crontab -
-
high Dangerous commands
cmd-persistenceSKILL.md:1353Persistence mechanism (cron / launchd / scheduled task / autorun registry)launchctl load ~/Library/LaunchAgents/com.agent-ops.orchestrator.plist
Medium and low: 7
-
medium Dangerous commands
cmd-persistenceSKILL.md:1318Persistence mechanism (cron / launchd / scheduled task / autorun registry) (quoted — discussed, not commanded)Create `~/Library/LaunchAgents/com.agent-ops.orchestrator.plist`:
quoted -
low Exfiltration
exfil-webhook-urlscripts/health-check.sh:103Webhook / callback URL commonly used for exfiltration (verify the destination) (placeholder value)"https://api.telegram.org/bot${bot_token}/sendMessage" \placeholder -
low Dangerous commands
cmd-cron-mentionSKILL.md:110Mentions editing / listing crontab(crontab -l 2>/dev/null; echo "*/5 * * * * ~/.agent-ops/scripts/health-check.sh >> ~/.agent-ops/logs/cron.log 2>&1") | crontab -
-
low Exfiltration
exfil-webhook-urlSKILL.md:434Webhook / callback URL commonly used for exfiltration (verify the destination) (placeholder value)curl -s "https://api.telegram.org/botYOUR_BOT_TOKEN/getUpdates" | python3 -c "
placeholder -
low Exfiltration
exfil-webhook-urlSKILL.md:516Webhook / callback URL commonly used for exfiltration (verify the destination) (the skill's own vendor host; quoted — discussed, not commanded)url = f"https://api.telegram.org/bot{bot_token}/sendMessage"vendor-hostquoted -
low Dangerous commands
cmd-background-processSKILL.md:1390Starts a background / autostarted processsudo systemctl enable agent-ops.timer
-
low Exfiltration
exfil-webhook-urlSKILL.md:1586Webhook / callback URL commonly used for exfiltration (verify the destination) (placeholder value)1. Verify bot token: `curl https://api.telegram.org/botYOUR_TOKEN/getMe`
placeholder
Files scanned: 4. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
name-formatname should be kebab-case (lowercase letters, digits, hyphens) - warning
description-no-whendescription does not say WHEN to use the skill (no "use when") - warning
body-longSKILL.md body ≈ 11481 tokens (recommended < 5000); move details to references/ - note
frontmatter-keyunknown frontmatter key "price"
Process rating: all ten parameters 53/100
- 0Result and completion. Does not say what the result is
- 20When it triggers. No condition that starts the skill
- 40Consistency. Frontmatter name (Agent Ops Kit) differs from the folder (agent-ops-kit)
- 40Execution cost. Instruction body is 11481 tokens: crowds the task out of the window
- 50Failures and branches. 0 branches, has a failure section
- 60Tools and files. Uses tools (bash, web, python) that frontmatter does not declare
- 70Inputs and preconditions. Inputs and preconditions are listed
- 100Steps. 25 steps
- 100Running it twice. Mutating operations check current state
- 100Progress reporting. Reports progress
- low 12 top-level sections: this looks like several domains in one skill
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
- -4Absolute local paths (C:\Users, /home/…): not portable
- -2localhost URLs: will not work for another user
- +1No license
- +2Single-language instructions
- +3Description length 161: enough signal without eating the budget
- +4Structure: 52 headings
- +3Step-by-step instructions: 25 items
- +4Has examples (39 code blocks)
- +3All 1 scripts are documented
Quality base 70; lint remarks subtract, signals add up to 100. Result: 53.