About this skill

Problem

Tencent EdgeOne spans domains, zones, cache, certificates, security policies, and logs, while pre-trained API knowledge can become outdated. Engineers working on site onboarding, cache purging, security audit, or log analysis need a disciplined path: read conventions first, choose the right API, and confirm write operations instead of relying on model memory.

How It Works and Limits

The skill routes requests to four module entries: references/api/README.md, references/acceleration/README.md, references/security/README.md, and references/observability/README.md. Before any task, it reads the API conventions; for batch purge, loop queries, or log analysis, it prefers a script over repeated manual API calls. All Create*, Modify*, Delete*, Apply*, and similar write operations must state impact and wait for confirmation. It never asks for SecretId / SecretKey and avoids printing credentials. If local references do not cover the case, it falls back to references/api/api-discovery.md and official docs; official documentation wins when sources conflict.

Screenshots

Use Cases

When onboarding a new domain, complete site setup, certificate checks, and cache prefetch.
When purging edge cache at scale, submit the batch task via script and verify results.
When checking origin health, download offline logs and generate a traffic daily report.
When auditing security policies, query IP block groups and export the security report.

Best For

Frontend or SRE engineers who onboard EdgeOne sites and need batch cache purge workflows.
Cloud security ops engineers who audit security policy templates and query IP block groups.
Ops analysts who produce traffic daily reports and origin health checks from offline logs.
Engineering leads who maintain API tooling, credential handling, and confirmation gates.