alibabacloud-opc-deploy
Alibaba Cloud OPC Deploy
Mandatory first tool call
Immediately after this skill loads, make exactly one tool call: use Read on <skill-base>/references/execution-phases.md, where <skill-base> is the base directory printed by the skill launcher. Do not batch this read with TodoWrite or any other tool, do not call unnamed or placeholder tools, and do not omit the references/ directory. If this exact read fails, correct that path and retry it once; perform no other action until it succeeds.
At each phase transition, read the exact file named by that index before acting. In particular, before the first price command, Read <skill-base>/references/confirm-authorize.md; if that read is not present in this session, no price command and no payment prompt may be emitted. For lite_seed, also execute only the commands in the already-loaded YAML's price_inquiries block.
Create all cloud resources for an OPC package step-by-step via the Aliyun CLI. After receiving the SKU prescription from alibabacloud-opc-advisor, follow the Phase flow to create / tag / verify / tear down resources via the Aliyun CLI. The AI assistant explains as it goes, showing progress at every step — white-box, companion-style deployment built for non-technical OPC users.
All user-facing output MUST be in Chinese (zh-CN).
Progress narration — plain language only, never internal phase/step labels. When you tell the user what you are doing, describe the action in plain Chinese; NEVER surface the skill's internal Phase/Step numbering, Gate, probe/探针, RamRoleArn/AssumeRole/STS, or iron-rule labels — they are implementation scaffolding, not user language (Hard Gate #6). Say what is happening, not which phase it is:
- ✗
现在进行 Phase -1.5 CLI 可达性检查和 Step 0.2b 权限探测→ ✓正在确认这些云产品能自动开通、以及账号权限是否就绪 - ✗
进入 Phase 0.4 镜像解析→ ✓正在为你选定服务器的系统镜像 - ✗
进入 Phase 1：询价→ ✓正在查询各项的实时价格This is a preventive rule, not a post-hoc self-check: phrase it right the first time. If a label slips into something already sent, restate that part in plain Chinese immediately.