EdgeOne Pages Deployment

Problem

When publishing a front-end project to EdgeOne Pages, the blocking issues are often operational rather than code-related: the edgeone CLI may be too old, China and Global console sessions can be confused, desktop browser login does not fit headless or CI environments, tokens can be mishandled, and the deploy URL can be truncated. This skill provides an agent with a deployment checklist that forces version, site, login mode, and output parsing decisions before running commands.

How It Works

• Environment checks: requires edgeone CLI >= 1.2.30 and sets an AI-skill context variable so deployments are distinguishable from manual runs.
• Site selection: asks the user to choose China or Global before login, mapping to console.cloud.tencent.com or console.intl.cloud.tencent.com instead of assuming a region.
• Auth modes: uses browser login for local desktop IDEs, token login for SSH, containers, CI, or explicit requests; saved tokens can be stored in .edgeone/.token and excluded from version control.
• Deploy parsing: extracts EDGEONE_DEPLOY_URL, EDGEONE_PROJECT_ID, and the console link, preserving the full query string because a truncated URL may not load.
• Failure paths: covers missing CLI, browser not opening, expired tokens, project name conflicts, build failures, and browser session reuse that binds the wrong account.

Boundaries

This skill is useful for quick preview or production deployment of an existing buildable project in local and CI workflows. It does not solve ICP filing, custom domain DNS, or resource permissioning. Preview URLs accessed from mainland China may be restricted by filing or CDN policy, so long-term public access still needs a properly filed custom domain.