EdgeOne Makers Deployment Skill

Deploy any project to EdgeOne Makers.

⛔ Critical Rules (never skip)

1. CLI version ≥ 1.6.0 — reinstall if lower. Versions below 1.6.0 lack the non-interactive fixes (whoami fail-fast, --json output) and will hang in Agent/CI environments. Never proceed with an outdated version.
2. Never truncate the deploy URL — EDGEONE_DEPLOY_URL includes query parameters required for access. Always output the complete URL. 3a. Prefer --json when running non-interactively — in Agent/CI/headless contexts, always pass --json to deploy so the result is a single machine-readable line; no need to scrape colored/\r-animated stdout. See Parse Deploy Output. 3b. Use edgeone whoami to check login status — on CLI ≥ 1.6.0, whoami fails fast (exit 1) when not logged in instead of hanging. If it exits 0, the user is already logged in and -t is not needed. Do NOT check cat .edgeone/.token — CLI stores credentials in ~/.edgeone/<hash> files, not a fixed .token path.
3. ⚠️ 部署地址必须醒目地放在回复最前面 — 部署完成后，完整的访问 URL 是用户最关心的核心交付物。必须做到：① 放在回复正文的第一行或第一个独立区块；② 使用醒目的格式（如大标题 + 代码块）；③ 绝不能把地址埋在长段落中间让用户去找。示例格式：

   🌐 线上地址：https://my-project-abc123.edgeone.cool?<auth_query_params>
   

   然后再附上其他说明（控制台地址、注意事项等）。
4. Ask the user to choose China or Global site before browser login. Never assume. (Token login via edgeone login --token auto-detects site, no need to ask.)
5. Auto-detect the login method — browser login in desktop environments, token login in headless/remote/CI environments. Follow the decision table below.
6. After token login, ask if the user wants to save the token locally for future use.
7. Before triggering any browser popup (login / registration), explain the reason and the benefits to the user first — never silently launch a browser window.