Install any skill in seconds. Free to start, no credit card required.
Get Started Free →doccker/api-proxy-safety
网关/代理/WAF/CDN 中间件的安全关键词匹配实现规范,防止纯子串匹配误判正常响应内容中的技术术语(如 Cloudflare、502、error)
Passed 21 of 22 test cases with the skill, and 10 of 22 without it.
and 12 more in the full report
11 fixed10 passed either way1 still failing0 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 11 test cases the skill fixed. Same model, same prompt, with and without the skill.
If an upstream service returns `{"error": {"code": 502, "message": "bad gateway"}}` with HTTP status 200, which inspection layer should catch this failure before body text scanning occurs?
| Checked | Without skill | With skill |
|---|---|---|
| Identifies response JSON schema inspection as Layer 3, preceding body keyword matching. | Missed | Passed |
The instructions your model reads when the skill loads.
网关/WAF/CDN 中间件实现关键词匹配时,避免纯子串匹配导致正常响应内容被误判。
// ❌ 误判:纯子串匹配,长正文中的正常用词也会命中
var pseudoSuccessPatterns = []string{
"cloudflare",
"502 bad gateway",
"bad gateway",
"reconnecting",
"upstream error",
}
当业务响应正文包含这些关键词的字面值(如文章主题就是 "Cloudflare"),纯子串匹配会触发误判,导致:
关键事实:关键词出现在长正文中 ≠ 响应存在问题。
将关键词按风险特征拆分为两组,并配合 HTTP 元数据做分层判定:
使用正文关键词匹配前,先通过 HTTP 元数据排除绝大多数正常响应:
| 判定层 | 检查项 | 优先级 |
|---|
test cases passed, vs 10 / 22 without
Published skills whose descriptions closely match this one, with their headline benchmark lift.
More skills from the same source and nearby in the registry, with their headline benchmark lift.