About this skill

Problem Solved

Publishing a local static index.html to Tencent EdgeOne Pages often gets interrupted by account setup, edgeone CLI, API token, project naming, and preview or production targets. This skill breaks the workflow into checkable steps: verify the environment, generate a deployable demo, then run deployment and report the result.

How It Works

The skill focuses on publishing a directory containing index.html:
- Account and service check: confirm whether Tencent Cloud and EdgeOne Pages are available; otherwise point to the console entry.
- CLI and token: detect edgeone CLI and ask whether an API token exists; if not, guide creation and copying.
- Demo generation: produce an index.html with dynamic background, gradient text, and a live clock to validate the deployment path.
- Deploy and update: publish using the folder path, project name -n, token -t, and optional -e preview; redeploying the same project name overwrites the update.

Boundaries and Notes

Treat the API token as sensitive; do not write it to logs or files.
Project names may use letters, numbers, and hyphens only, no Chinese characters.
Plain static HTML does not need a build step; upload the directory directly.
Default region is global; domestic users may choose the china region.

Screenshots

Use Cases

A frontend engineer finishes a static site homepage and needs to publish a local HTML directory to a previewable URL.
An indie developer generates a dynamic demo page locally and wants to verify the EdgeOne Pages deployment path.
A product operations person exports a campaign landing page as static HTML and needs to publish it without build tooling.
A tester repeatedly updates the same project's static page and expects redeployment to overwrite the project, not create a new one.

Best For

Frontend engineers: publish local static pages or demos to EdgeOne Pages and verify the deployment result.
Indie developers: validate that the edgeone CLI, API token, and preview environment work for static site deployment.
Product operations staff: publish campaign pages or documentation pages as HTML and get a preview link for iteration.
Test engineers: repeatedly redeploy the same project name and check whether the static update overwrites correctly.