BC webhook-notify
通用 Webhook 通知工具,支持钉钉、企业微信、飞书、Slack、Discord、Telegram。自动识别平台,统一接口,内置模板系统和重试机制。
As a process C 56/100 · Has gaps — weak spots: result and completion, when it triggers, inputs and preconditions
IntegrationSlackDiscordTelegramInfrastructuretype and topics are labelled automatically from the skill text
How to improve
- Say in the description WHEN to use the skill ("use when…", example requests): that is the agent's main cue.
For the model run — optional
- 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 · 4
✓ No critical or high findings
Medium and low: 4
-
low Exfiltration
exfil-webhook-urlexamples.ps1:21Webhook / callback URL commonly used for exfiltration (verify the destination) (test fixture / example file; the skill's own vendor host; quoted — discussed, not commanded)$env:SLACK_WEBHOOK = "https://hooks.slack.com/services/YOUR/WEBHOOK/URL"
fixturevendor-hostquoted -
low Exfiltration
exfil-webhook-urlSKILL.md:43Webhook / callback URL commonly used for exfiltration (verify the destination) (documentation table row; the skill's own vendor host)| **Slack** | ✅ | ❌ | `https://hooks.slack.com/services/***` |
tablevendor-host -
low Exfiltration
exfil-webhook-urlSKILL.md:44Webhook / callback URL commonly used for exfiltration (verify the destination) (documentation table row; the skill's own vendor host)| **Discord** | ✅ | ❌ | `https://discord.com/api/webhooks/***` |
tablevendor-host -
low Exfiltration
exfil-webhook-urlSKILL.md:45Webhook / callback URL commonly used for exfiltration (verify the destination) (documentation table row; the skill's own vendor host)| **Telegram** | ✅ | ❌ | `https://api.telegram.org/bot***/sendMessage` |
tablevendor-host
Files scanned: 11. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
description-no-whendescription does not say WHEN to use the skill (no "use when")
Process rating: all ten parameters 56/100
- 0Result and completion. Does not say what the result is
- 0Inputs and preconditions. Does not say what the process needs to start
- 0Progress reporting. Says nothing while it works
- 20When it triggers. No condition that starts the skill
- 30Running it twice. 11 mutating operations with no state check
- 50Failures and branches. 0 branches, has a failure section
- 100Tools and files. No external tools needed
- 100Steps. 38 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 1553 tokens
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)
- +3Description length 76: 120–800 characters recommended
- +3Output format is not stated: the model decides each time
- -221 emoji in the instructions: noise for the model
- +1No license
- +2Single-language instructions
- +4Structure: 28 headings
- +3Step-by-step instructions: 38 items
- +4Has examples (16 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 67.
External checks
ClawHub: suspicious
Review before installing: the skill is mostly a disclosed webhook notifier, but it ships under-scoped generic HTTP helpers and gives weak guidance around webhook secrets.
LLM: suspicious (high) · VirusTotal: · 4 Jun 2026