BB tencent-edgeone-skill
A comprehensive skill for Tencent EdgeOne (Edge Security & Acceleration Platform), covering edge acceleration (DNS, certificates, caching, rule engine, L4 proxy, load balancing), edge security (DDoS protection, Web protection, Bot management), edge media (real-time video / image processing), edge development (Edge Functions, EdgeOne Pages), and more. Use this skill whenever a user mentions any EdgeOne / EO-related configuration, operations, querying, or troubleshooting needs.
As a process B 69/100 · Nearly there — weak spots: result and completion, inputs and preconditions, running it twice
How to improve
- Your own cases (evals/evals.json, 4–6 real requests with expected answers): the full check would then run those instead of a model-drafted suite.
- A spec.yaml with trigger phrases and assertions — a behaviour contract for CI; `skilltest init` writes a template.
Guard findings · 11
✓ No critical or high findings
Medium and low: 11
-
low Secrets in code
secret-high-entropy-tokenreferences/observability/eo-log-downloader.md:65High-entropy token-like string (may be an id, hash or a credential) (quoted — discussed, not commanded)3. **No traffic** — The domain may have no actual traffic in the queried time range. Use `Desc…ata` or check the console to confirm
quoted -
low Secrets in code
secret-high-entropy-tokenreferences/observability/eo-origin-health-check.md:9High-entropy token-like string (may be an id, hash or a credential)| Desc…ata | Query L7 time-series data (response status code analysis at edge nodes) |
-
low Secrets in code
secret-high-entropy-tokenreferences/observability/eo-origin-health-check.md:10High-entropy token-like string (may be an id, hash or a credential)| Desc…ata | Query L7 origin-pull time-series data (origin status code distribution, origin traffic/bandwidth) |
-
low Secrets in code
secret-high-entropy-tokenreferences/observability/eo-origin-health-check.md:28High-entropy token-like string (may be an id, hash or a credential) (quoted — discussed, not commanded)- **Shortcut**: Both `Desc…ata` and `Desc…ata` support `ZoneIds=["*"]` to query account-level aggregated data across all zones. Use this when the user does no
quoted -
low Secrets in code
secret-high-entropy-tokenreferences/observability/eo-origin-health-check.md:32High-entropy token-like string (may be an id, hash or a credential)### Interval (applies to both Desc…ata and Desc…ata)
-
low Secrets in code
secret-high-entropy-tokenreferences/observability/eo-origin-health-check.md:46High-entropy token-like string (may be an id, hash or a credential)### Desc…ata
-
low Secrets in code
secret-high-entropy-tokenreferences/observability/eo-traffic-daily-report.md:9High-entropy token-like string (may be an id, hash or a credential)| Desc…ata | Query L7 time-series traffic/bandwidth/request data |
-
low Secrets in code
secret-high-entropy-tokenreferences/observability/eo-traffic-daily-report.md:67High-entropy token-like string (may be an id, hash or a credential) (quoted — discussed, not commanded)L7 access data query APIs (`Desc…ata`, `Desc…ata`) **return post-mitigation clean traffic/request counts by default** (i.e., excluding requests blocked/challenged
quoted -
low Secrets in code
secret-high-entropy-tokenreferences/observability/eo-traffic-daily-report.md:82High-entropy token-like string (may be an id, hash or a credential) (detector / deny-list definition)In `Desc…ata` and `Desc…ata`, use the `domain` key in `Filters` to filter data for a specific domain:
detector -
low Secrets in code
secret-high-entropy-tokenreferences/observability/eo-traffic-daily-report.md:214High-entropy token-like string (may be an id, hash or a credential) (quoted — discussed, not commanded)- `Desc…ata` has approximately 10-minute data delay; avoid querying the most recent 10 minutes
quoted -
low Secrets in code
secret-high-entropy-tokenreferences/observability/eo-traffic-daily-report.md:218High-entropy token-like string (may be an id, hash or a credential) (quoted — discussed, not commanded)Call `Desc…ata` to query the following metrics:
quoted
Files scanned: 22. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
✓ No remarks against the Agent Skills spec
Process rating: all ten parameters 69/100
- 0Result and completion. Does not say what the result is
- 0Inputs and preconditions. Does not say what the process needs to start
- 30Running it twice. 2 mutating operations with no state check
- 70When it triggers. States when to use, but not when not to
- 100Tools and files. No external tools needed
- 100Steps. 7 steps
- 100Failures and branches. 3 branches, has a failure section
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 771 tokens
- 100Progress reporting. Reports progress
- medium Safety rules and hard prohibitions inside a skill: they belong in the system prompt, here they protect nothing
Everything here is measured from the skill text rather than judged by a model, so the numbers are checkable. A parameter weighs more when it is a more common reason for the process to stall.
Quality signals
- +5Description has no quoted example phrases that should trigger the skill
- +4Description does not say when NOT to use the skill (false activations)
- +3Output format is not stated: the model decides each time
- +4No input/output examples
- +1No license
- +2Single-language instructions
- +3Description length 480: enough signal without eating the budget
- +4Structure: 5 headings
- +3Step-by-step instructions: 7 items
Quality base 70; lint remarks subtract, signals add up to 100. Result: 80.