BB alibabacloud-ecs-code-deploy
基于 aliyun appmanager 一键把项目代码部署到阿里云 ECS 云服务器,覆盖环境预检、询价、部署、日志验证、失败诊断重试全流程。支持 App / AI Agent(LangChain / AutoGen / AgentScope / MCP / FastAPI / Flask / Spring Boot 等),新建或已有 ECS 实例,自动处理分组冲突、zip 解压、余额不足、地域参数透传、重复部署免初始化。触发词:部署到ECS、部署项目到ECS、部署到云服务器、把这个项目部署上去、上线到ECS、把仓库部署到ECS、当前目录部署、阿里云ECS部署、appmanager部署、aliyun appmanager、一键部署App、部署AI Agent、deploy to ECS、code deploy、deploy app、deploy agent、appmanager deploy、ECS code deploy、跑一下这个项目、把代码跑到ECS上、ECS上线。
基于 aliyun appmanager 一键把项目代码部署到阿里云 ECS 云服务器,覆盖环境预检、询价、部署、日志验证、失败诊断重试全流程。支持 App / AI Agent(LangChain / AutoGen / AgentScope / MCP / FastAPI / Flask / Spring…
As a process B 72/100 · Nearly there — weak spots: execution cost
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 · 8
✓ No critical or high findings
Medium and low: 8
-
medium Dangerous commands
cmd-pipe-to-shellreferences/script-templates.md:90Downloads and executes remote code from an unrecognised host (pipe to shell) (quoted — discussed, not commanded)> **⚠️ Supply chain security**: Some rows below use `curl ... | bash` or `curl ... | php` patterns to install runtimes. These are convenience patterns from upstream vendors (NodeSource, Composer, Go)
quoted -
medium Dangerous commands
cmd-pipe-to-shellreferences/script-templates.md:99Downloads and executes remote code from an unrecognised host (pipe to shell) (documentation table row)| **Node.js** | `command -v node` | `curl --connect-timeout 30 --max-time 120 -fsSL https://rpm.nodesource.com/setup_22.x \| bash - && $PKG_MGR install -y nodejs` (HTTPS official NodeSource; prefer di
table -
low Dangerous commands
cmd-shell-rcreferences/init-and-credentials.md:91Writes to a shell startup file (detector / deny-list definition)grep -q 'HOME/bin' ~/.zshrc 2>/dev/null || echo 'export PATH="$HOME/bin:$PATH"' >> ~/.zshrc
detector -
low Dangerous commands
cmd-background-processreferences/lessons-learned.md:60Starts a background / autostarted processnohup java -Xmx384m -jar /root/<app>.jar --server.port=8090 >> /root/app.log 2>&1 &
-
low Dangerous commands
cmd-background-processreferences/script-templates.md:81Starts a background / autostarted processnohup {START_CMD} >> "$LOG_FILE" 2>&1 & -
low Dangerous commands
cmd-pipe-to-shell-known-hostreferences/script-templates.md:99Pipe-to-shell installer from a well-known host (still executes remote code) (detector / deny-list definition; documentation table row)| **Node.js** | `command -v node` | `curl --connect-timeout 30 --max-time 120 -fsSL https://rpm.nodesource.com/setup_22.x \| bash - && $PKG_MGR install -y nodejs` (HTTPS official NodeSource; prefer di
detectortable -
low Dangerous commands
cmd-background-processreferences/tutorial-flask-app.md:80Starts a background / autostarted processnohup python3 app.py >> /root/app.log 2>&1 &
-
low Dangerous commands
cmd-shell-rcscripts/deploy_toolkit.py:292Writes to a shell startup file (string literal in code, not executed)print(f" echo 'export PATH=\"$HOME/bin:$PATH\"' >> ~/.zshrc # bash users edit ~/.bashrc")
code literal
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") - warning
body-longSKILL.md body ≈ 8124 tokens (recommended < 5000); move details to references/ - note
edit-residuethe text marks something as outdated (lines 95): check that old rules are not kept next to new ones — the full check reads the text for contradictions
Process rating: all ten parameters 72/100
- 40Execution cost. Instruction body is 8124 tokens: crowds the task out of the window
- 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
- 85Steps. 31 steps, 2 vague phrases
- 100Failures and branches. 4 branches, has a failure section
- 100Consistency. Name and required fields are in place
- 100Running it twice. Mutating operations check current state
- 100Progress reporting. Reports progress
- medium Safety rules and hard prohibitions inside a skill: they belong in the system prompt, here they protect nothing
- low 13 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
- +5Description has no quoted example phrases that should trigger the skill
- +4Description does not say when NOT to use the skill (false activations)
- -5TODO / placeholder text left in the skill
- -220 emoji in the instructions: noise for the model
- +1No license
- +2Single-language instructions
- +3Description length 443: enough signal without eating the budget
- +4Structure: 27 headings
- +3Step-by-step instructions: 31 items
- +3Output format is stated explicitly
- +4Has examples (6 code blocks)
- +4Reference files are cited in the instructions (6 of 7)
- +3All 1 scripts are documented
Quality base 70; lint remarks subtract, signals add up to 100. Result: 65.