FC platform-monitor
全平台状态监控助手。监控AI平台可达性、关键词变化、响应时间、竞品动态,支持飞书/微信/钉钉通知、定时巡检、健康度评分。触发词:"监控XX平台"、"检查XX状态"、"XX是不是挂了"、"每天9点帮我检查"、"有没有新公告"、"竞品有什么变化"。
全平台状态监控助手。监控AI平台可达性、关键词变化、响应时间、竞品动态,支持飞书/微信/钉钉通知、定时巡检、健康度评分。触发词:"监控XX平台"、"检查XX状态"、"XX是不是挂了"、"每天9点帮我检查"、"有没有新公告"、"竞品有什么变化"。
As a process C 53/100 · Has gaps — weak spots: result and completion, when it triggers, inputs and preconditions
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 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
- 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.
- Say in the description WHEN to use the skill ("use when…", example requests): that is the agent's main cue.
- 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 · 16
-
high Dangerous commands
cmd-persistencescripts/install.ps1:67Persistence mechanism (cron / launchd / scheduled task / autorun registry)Register-ScheduledTask -TaskName "PlatformMonitor-Morning" -Action `$action -Trigger `$trigger1 -Description "平台监控-早班" -Force
-
high Dangerous commands
cmd-persistencescripts/install.ps1:68Persistence mechanism (cron / launchd / scheduled task / autorun registry)Register-ScheduledTask -TaskName "PlatformMonitor-Evening" -Action `$action -Trigger `$trigger2 -Description "平台监控-晚班" -Force
-
high Dangerous commands
cmd-persistencescripts/install.sh:63Persistence mechanism (cron / launchd / scheduled task / autorun registry)(crontab -l 2>/dev/null; echo "$CRON_CMD") | crontab -
-
high Dangerous commands
cmd-persistencescripts/README.md:90Persistence mechanism (cron / launchd / scheduled task / autorun registry)Register-ScheduledTask -TaskName "PlatformMonitor-Morning" -Action $action -Trigger $trigger1 -Force
-
high Dangerous commands
cmd-persistencescripts/README.md:91Persistence mechanism (cron / launchd / scheduled task / autorun registry)Register-ScheduledTask -TaskName "PlatformMonitor-Evening" -Action $action -Trigger $trigger2 -Force
Medium and low: 11
-
medium Dangerous commands
cmd-execpolicy-bypassscripts/README.md:31Runs PowerShell with execution policy bypassedpowershell -ExecutionPolicy Bypass -File install.ps1
-
low Dangerous commands
cmd-execpolicy-bypassscripts/install.ps1:2Runs PowerShell with execution policy bypassed (code comment)# 用法: powershell -ExecutionPolicy Bypass -File install.ps1
comment -
low Dangerous commands
cmd-execpolicy-bypassscripts/install.ps1:79Runs PowerShell with execution policy bypassed (quoted — discussed, not commanded)Write-Host " powershell -ExecutionPolicy Bypass -File $taskScriptPath" -ForegroundColor Cyan
quoted -
low Dangerous commands
cmd-cron-mentionscripts/install.sh:59Mentions editing / listing crontabif crontab -l 2>/dev/null | grep -q "monitor.js"; then
-
low Dangerous commands
cmd-cron-mentionscripts/install.sh:63Mentions editing / listing crontab(crontab -l 2>/dev/null; echo "$CRON_CMD") | crontab -
-
low Secrets in code
secret-high-entropy-tokenscripts/package-lock.json:28High-entropy token-like string (may be an id, hash or a credential) (detector / deny-list definition)"integrity": "sha5…9dM/mwVgvbZJaSNaRk+bshk…Kbz+IoId…W0Q==",
detector -
low Secrets in code
secret-high-entropy-tokenscripts/package-lock.json:90High-entropy token-like string (may be an id, hash or a credential) (detector / deny-list definition)"integrity": "sha5…NxY+fzEC…TMw+Dfs3…h4g==",
detector -
low Secrets in code
secret-high-entropy-tokenscripts/package-lock.json:107High-entropy token-like string (may be an id, hash or a credential) (detector / deny-list definition)"integrity": "sha5…SDq+2kAA…MOe/+5cdoEdg==",
detector -
low Secrets in code
secret-high-entropy-tokenscripts/package-lock.json:147High-entropy token-like string (may be an id, hash or a credential) (detector / deny-list definition)"integrity": "sha5…GLw+xYSd…cqA==",
detector -
low Secrets in code
secret-high-entropy-tokenscripts/package-lock.json:187High-entropy token-like string (may be an id, hash or a credential) (detector / deny-list definition)"integrity": "sha5…9co+7Zrb…CSH/zJvXw56gmHw==",
detector -
low Dangerous commands
cmd-cron-mentionscripts/README.md:100Mentions editing / listing crontabcrontab -e
Files scanned: 11. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
description-no-whendescription does not say WHEN to use the skill (no "use when") - note
frontmatter-keyunknown frontmatter key "emoji"
Process rating: all ten parameters 53/100
- 0Result and completion. Does not say what the result is
- 0Inputs and preconditions. Does not say what the process needs to start
- 0Failures and branches. Linear process with no failure handling
- 0Progress reporting. Says nothing while it works
- 20When it triggers. No condition that starts the skill
- 100Tools and files. No external tools needed
- 100Steps. 24 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 997 tokens
- 100Running it twice. No mutating operations
- low 14 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
- +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
- +5Description quotes 6 example trigger phrases
- +3Description length 122: enough signal without eating the budget
- +4Structure: 27 headings
- +3Step-by-step instructions: 24 items
- +4Has examples (11 code blocks)
- +3All 5 scripts are documented
Quality base 70; lint remarks subtract, signals add up to 100. Result: 79.