CC alibabacloud-rds-postgresql-inspection
Batch health inspection for Alibaba Cloud RDS PostgreSQL instances. Supports single, multiple, or all-instance global scan with configurable time window (default 7 days, max 30). Outputs one HTML report per instance plus a summary HTML. Dimensions include instance basics, resource utilization (CPU/memory/disk/IOPS/connections), CloudMonitor alert history, slow log TOP 20, long transactions, table bloat, QPS/TPS, replication delay. Cluster instances auto-detected with per-node metrics. Triggers on RDS inspection, RDS health check, RDS PostgreSQL inspection, Alibaba Cloud RDS inspection, batch or global multi-instance inspection, slow log analysis, space analysis, PostgreSQL inspection, long transaction, table bloat, replication delay. Chinese triggers: "巡检 RDS PostgreSQL"、"RDS PostgreSQL 巡检"、"RDS 健康巡检"、"RDS 健康检查"、"阿里云 RDS 巡检"、"批量巡检"、"全局巡检"、"所有实例巡检"、"实例巡检"、"慢日志分析"、"长事务"、"表膨胀"、"复制延迟"、"健康评分"、"汇总报告"。
Batch health inspection for Alibaba Cloud RDS PostgreSQL instances.
As a process C 60/100 · Has gaps — weak spots: result and completion, running it twice
What is at stake
Medium-severity findings: the skill is probably honest, but read what alarmed the scanner.
Below is the worst case for this category. The finding here is medium: the guard saw a sign, not a proof.
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
- 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 · 6
✓ No critical or high findings
Medium and low: 6
-
medium Dangerous commands
cmd-privilegeassets/cli-installation-guide.md:30Privilege escalation / world-writable permissionssudo mv aliyun /usr/local/bin/
-
medium Dangerous commands
cmd-privilegeassets/cli-installation-guide.md:45Privilege escalation / world-writable permissionssudo mv aliyun /usr/local/bin/
-
medium Dangerous commands
cmd-privilegeassets/cli-installation-guide.md:58Privilege escalation / world-writable permissionssudo mv aliyun /usr/local/bin/
-
medium Dangerous commands
cmd-privilegeassets/cli-installation-guide.md:71Privilege escalation / world-writable permissionssudo mv aliyun /usr/local/bin/
-
medium Dangerous commands
cmd-autorun-instructionSKILL.md:56Instructs the agent to auto-run a script on every session## [MUST] Execution Mode — Always Run the Script, Never Hand-craft CLI
-
medium Dangerous commands
cmd-pipe-to-shellSKILL.md:145Downloads and executes remote code from an unrecognised host (pipe to shell) (quoted — discussed, not commanded)> run `curl -fsSL https://aliyuncli.alicdn.com/setup.sh | bash` to install or upgrade,
quoted
Files scanned: 7. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
frontmatter-yamlSKILL.md: the frontmatter is not valid YAML (YAML parse error: Nested mappings are not allowed in compact mappings at line 2, column 14: description: Batch health inspection for Alibaba Cloud RDS PostgreSQL instances… ^ ); fields were read line by line. The usual cause is a colon inside an unquoted value - warning
description-no-whendescription does not say WHEN to use the skill (no "use when") - warning
body-longSKILL.md body ≈ 6455 tokens (recommended < 5000); move details to references/
Process rating: all ten parameters 60/100
- 0Result and completion. Does not say what the result is
- 30Running it twice. 2 mutating operations with no state check
- 50Failures and branches. 0 branches, has a failure section
- 60Tools and files. Uses tools (bash, web, python, node) that frontmatter does not declare
- 60Steps. 62 steps, 4 vague phrases
- 70When it triggers. States when to use, but not when not to
- 70Execution cost. Instruction body is 6455 tokens
- 100Inputs and preconditions. Inputs and preconditions are listed
- 100Consistency. Name and required fields are in place
- 100Progress reporting. Reports progress
- medium Safety rules and hard prohibitions inside a skill: they belong in the system prompt, here they protect nothing
- low 15 top-level sections: this looks like several domains in one skill
- low The response is described with custom markup (7 tags): a typed call is more reliable
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)
- +3Description length 908: 120–800 characters recommended
- +3Output format is not stated: the model decides each time
- -31 of 2 scripts are never mentioned in SKILL.md
- +1No license
- +2Single-language instructions
- +5Description quotes 6 example trigger phrases
- +4Structure: 37 headings
- +3Step-by-step instructions: 62 items
- +4Has examples (16 code blocks)
- +4Reference files are cited in the instructions (1 of 2)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 55.