tencentcloud-edgeone

What problem does it solve?

EdgeOne CDN cache needs fast, precise invalidation and warm-up after deployments, but doing it manually can be slow and error-prone while risking stale content for users.

Core Features & Use Cases

• Cache purge (URL/prefix/hostname/all): Remove stale objects for specific pages, asset paths, or whole hostnames, with an emergency option to purge everything in a zone.
• Prefetch (pre-warm edges): Warm the most important routes by scheduling prefetch tasks so users hit fresh cached content sooner.
• Operational visibility and configuration management: List zones and acceleration domains, track purge/prefetch task status, and manage EdgeOne DNS records plus inspect WAF/security settings for a zone.
• Use Case: After deploying a new web build, purge the affected routes (by URL, prefix, or host) and prefetch the top landing pages so traffic quickly serves the updated assets instead of stale cached responses.

Quick Start

Ask the skill to purge EdgeOne cache for the specific hostname after you deploy, for example: "Purge all cache for zone-xxxxxxxx" or "Purge cache for zone-xxxxxxxx by URL https://hub.example.com/index.html".