BB alibabacloud-migration-mas-cloud-migration-survey
当用户提供迁云调研材料（Excel/Word/文本/CSV文件）并要求生成结构化调研报告时，自动分析汇总并输出 .docx 文档。涵盖客户画像、架构现状、云产品映射、版本兼容性风险、迁移风险、待确认事项。支持 AWS/Azure/GCP/华为云/腾讯云/百度云/IDC 到阿里云的迁移评估。适用于阿里云迁云项目售前或交付调研阶段。本 skill 仅做信息梳理和报告生成，不执行实际迁移操作，不生成报价方案。
当用户提供迁云调研材料（Excel/Word/文本/CSV文件）并要求生成结构化调研报告时，自动分析汇总并输出 .docx 文档。涵盖客户画像、架构现状、云产品映射、版本兼容性风险、迁移风险、待确认事项。支持 AWS/Azure/GCP/华为云/腾讯云/百度云/IDC…
As a process B 66/100 · Nearly there — weak spots: inputs and preconditions
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 · 0
✓ No critical or high findings
Files scanned: 8. 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 ≈ 6365 tokens (recommended < 5000); move details to references/
Process rating: all ten parameters 66/100
- 30Inputs and preconditions. Does not say what the process needs to start
- 50When it triggers. No condition that starts the skill
- 60Tools and files. Uses tools (bash, write, python) that frontmatter does not declare
- 60Steps. 116 steps, 12 vague phrases
- 60Result and completion. Output format stated, no completion criterion
- 70Execution cost. Instruction body is 6365 tokens
- 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 10 top-level sections: this looks like several domains in one skill
- low The response is described with custom markup (11 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)
- +1No license
- +2Single-language instructions
- +3Description length 203: enough signal without eating the budget
- +4Structure: 26 headings
- +3Step-by-step instructions: 116 items
- +3Output format is stated explicitly
- +4Has examples (5 code blocks)
- +4Reference files are cited in the instructions (2 of 2)
- +3All 3 scripts are documented
Quality base 70; lint remarks subtract, signals add up to 100. Result: 72.