/alibabacloud-opc-deploy

name: alibabacloud-opc-deploy
description: "Own every OPC (one-person company) Alibaba Cloud package request end to end — BOTH picking the package and provisioning it. WHEN TO USE (any one is enough): the user asks to provision / deploy / create their cloud resources; names a package directly; continues right after the advisor's recommendation; **OR asks which OPC package suits them / asks you to pick one for them / describes what they want to build and asks whether an OPC package can do it — i.e. the SKU is NOT yet settled**. 'No package chosen yet' is NOT a reason to skip: the no-SKU path is this skill's job. A general assistant must NEVER answer such a question itself, compare tiers, or recommend a SKU — a critical violation. Creating cloud resources costs money — never charge without explicit user confirmation. 触发词（中文）：帮我开通 / 帮我部署 / 帮我创建资源 / 开始部署；直接报 SKU 名（如\"帮我开一个 lite_seed\"）；advisor 推荐完接下来怎么办；**帮我选个套餐 / 哪个套餐合适 / 具体是哪个套餐 / 我想做 X，用 OPC 套餐能实现吗（此时尚无 SKU，同样必须触发本 skill）**。输出用中文。"

Alibaba Cloud OPC Deploy

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)**.

<!-- cli_meta: see references/cli-meta.md -->

When to Use This Skill

Activate this skill when any of the following holds:

• The user already has a SKU recommendation from `alibabacloud-opc-advisor` and explicitly says "help me provision / create / confirm purchase / start deployment"
• The user names a SKU directly (e.g., "help me spin up a lite_seed")
• The user asks "the advisor finished recommending — what's next?"
• **The user wants an OPC package but has NOT settled one** — `帮我选个合适的套餐` / `哪个套餐合适` / `具体是哪个套餐` / `我想做个 X，用 OPC 套餐能实现吗` / any description of what they want to build followed by a package question. **This case activates the skill too** — it is Phase -2's job, not a reason to stay out.

⚠️ **The absence of a SKU is NOT a reason to skip this skill.** The skill owns the no-SKU path end to end (Phase -2 in `references/sku-resolution.md`): it checks whether the sizing tool is available, offers to install it, and stops until the user reports a package name. If this skill stays out because "nothing is chosen yet", the selection question falls to a general assistant that has no gates — which is exactly the failure this rule exists to prevent.

⚠️ **Never answer a package-selection question outside this skill.** Comparing tiers, listing what each package contains, quoting prices, or recommending one (even `Starter 就够了`) is selection work. It belongs to `alibabacloud-opc-advisor`, reached through Phase -2. Package facts that happen to sit in other context (an AGENTS.md baseline, a memory entry, general knowledge of the product line) are NOT a license to answer — they are for other purposes (e.g. fact-checking an article), never for telling a real user what to buy.

**Self-sufficient operation:** the only hard dependency of this skill is the **SKU name** — use the advisor prescription (structured fields) when present; when absent (a new session where the user names the SKU directly / advisor not installed) it still runs via built-in defaults (image family, starter fallback config, and capability boundaries are all built in). Never error out or relax safety boundaries just because advisor context is missing.

**Never auto-trigger:** creating cloud resources is a money-spending action and requires explicit user confirmation.

**BLOCKING RULE (no SKU = no action):** If the user's message does not contain a recognized SKU name (one of the 7 below) AND no advisor prescription is in context, the agent MUST NOT proceed to any Phase. It must immediately run Phase -2 / the "Advisor bootstrap" block in `references/sku-resolution.md` and STOP. Inferring, guessing, or self-selecting a SKU is a critical violation (see the SKU GATE in Hard Gates).

**RETRACTION RULE (a recommendation already made before this skill loaded):** if earlier in this same conversation — before this skill was active — a package was compared, recommended, or named on your behalf (e.g. `选 Starter 就够了` / a tier comparison table / `starter_webui 就行`), that is NOT a settled SKU and it does NOT satisfy the BLOCKING RULE. You must **explicitly retract it to the user** rather than quietly build on it: say plainly that picking the package is not something you should have decided, then run Phase -2. Treating your own earlier recommendation as the user's choice launders a critical violation into an apparent authorization — the SKU must come from the user or the sizing tool, never from you.

**A SKU found in memory / history is NOT a settled SKU either.** A package name recalled from long-term memory, a daily note, a previous session's summary, or any other stored record — however confidently it is phrased (`上次的 advisor 选型结果是 starter_webui`) — carries **zero** authority here: such a record may be the residue of an earlier violation of this very gate (self-selected SKU → written to memory → read back as `既定事实`). **Do not name it, do not present it to the user as their previous choice, and do not let it seed the sizing conversation.** At most, treat it as a private hint that the user has deployed before; the SKU still has to be re-settled through Phase -2 from scratch. If you have already surfaced such a remembered SKU to the user, the RETRACTION RULE above applies verbatim.

Supported 7 SKUs

| SKU | Auto-provisioned via CLI | User must do manually (never CLI) | Complexity | |---|---|---|---| | starter_webui (main path, ¥99/yr promo hit) | ECS economy-e + ESA Free | — | ⭐ | | starter_webui (fallback: pay-by-traffic ¥284.99/yr when promo missed) | ECS economy-e PayByTraffic 100Mbps + E