FC alibabacloud-kvstore-health-inspection
Health inspection for Alibaba Cloud Redis (ApsaraDB for Redis / Tair) instances. Generates HTML reports across 7 dimensions: instance basic info, current sessions, resource usage trends (CPU/memory/connection/bandwidth, last 7 days), big key / hot key analysis, slow log statistics, alert history, and risk-prioritized recommendations. Supports standard / cluster / SplitRW architectures, Tair PENA (persistent memory) and Tair ESSD (disk) types. Single-instance, multi-instance and full-account batch modes are supported. Trigger keywords: Redis inspection, Redis health check, KVStore inspection, Tair inspection, CPU usage, memory usage, connection usage, bandwidth usage, proxy usage, persistent memory, disk usage, slow log, big key, hot key, alert history, instance health report.
Health inspection for Alibaba Cloud Redis (ApsaraDB for Redis / Tair) instances.
As a process C 61/100 · Has gaps — weak spots: failures and branches, running it twice
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.
- 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 · 9
-
high Dangerous commands
cmd-pipe-to-shellreferences/cli-installation-guide.md:27Downloads and executes remote code from an unrecognised host (pipe to shell)curl -fsSL https://aliyuncli.alicdn.com/setup.sh | sudo bash
-
high Dangerous commands
cmd-pipe-to-shellreferences/cli-installation-guide.md:32Downloads and executes remote code from an unrecognised host (pipe to shell)curl -fsSL https://aliyuncli.alicdn.com/setup.sh | sudo bash
-
high Dangerous commands
cmd-pipe-to-shellreferences/cli-installation-guide.md:253Downloads and executes remote code from an unrecognised host (pipe to shell)curl -fsSL https://aliyuncli.alicdn.com/setup.sh | sudo bash
Medium and low: 6
-
medium Dangerous commands
cmd-privilegereferences/cli-installation-guide.md:20Privilege escalation / world-writable permissionssudo mv aliyun /usr/local/bin/
-
medium Dangerous commands
cmd-privilegereferences/cli-installation-guide.md:27Privilege escalation / world-writable permissionscurl -fsSL https://aliyuncli.alicdn.com/setup.sh | sudo bash
-
medium Dangerous commands
cmd-privilegereferences/cli-installation-guide.md:32Privilege escalation / world-writable permissionscurl -fsSL https://aliyuncli.alicdn.com/setup.sh | sudo bash
-
medium Dangerous commands
cmd-privilegereferences/cli-installation-guide.md:48Privilege escalation / world-writable permissionssudo mv aliyun /usr/local/bin/
-
medium Dangerous commands
cmd-privilegereferences/cli-installation-guide.md:250Privilege escalation / world-writable permissionssudo mv aliyun /usr/local/bin/
-
medium Dangerous commands
cmd-pipe-to-shellSKILL.md:176Downloads and executes remote code from an unrecognised host (pipe to shell) (quoted — discussed, not commanded)> or run `curl -fsSL https://aliyuncli.alicdn.com/setup.sh | bash` to install/update.
quoted
Files scanned: 9. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- note
edit-residuethe text marks something as outdated (lines 175, 179): check that old rules are not kept next to new ones — the full check reads the text for contradictions
Process rating: all ten parameters 61/100
- 0Failures and branches. Linear process with no failure handling
- 30Running it twice. 4 mutating operations with no state check
- 50When it triggers. No condition that starts the skill
- 60Tools and files. Uses tools (bash, web, python, node) that frontmatter does not declare
- 60Result and completion. Output format stated, no completion criterion
- 70Inputs and preconditions. Inputs and preconditions are listed
- 70Execution cost. Instruction body is 4337 tokens
- 85Steps. 61 steps, 2 vague phrases
- 100Consistency. Name and required fields are in place
- 100Progress reporting. Reports progress
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)
- +1No license
- +2Single-language instructions
- +3Description length 786: enough signal without eating the budget
- +4Structure: 18 headings
- +3Step-by-step instructions: 61 items
- +3Output format is stated explicitly
- +4Has examples (19 code blocks)
- +4Reference files are cited in the instructions (4 of 4)
- +3All 3 scripts are documented
Quality base 70; lint remarks subtract, signals add up to 100. Result: 94.