BF Telegram News Digest (Lite)
Monitors public Telegram channels via web scraping (t.me/s/*), extracts new messages, generates AI-powered summaries, and delivers structured digests to your configured OpenClaw notification channel. Zero authentication required — just provide channel names.
As a process F 33/100 · Will not run — References files that are not bundled: LICENSE
What is at stake
Medium-severity findings: the skill is probably honest, but read what alarmed the scanner.
Below is the worst case for this category. The finding here is medium: the guard saw a sign, not a proof.
The instructions or scripts send data out: environment variables, keys, file contents, chat history. You may never notice, because the agent performs the upload as "part of the task".
If the upload is not needed for the task, remove it: catalogs flag such skills and delist them. If it is needed, name the destination explicitly, say what leaves the machine, and give the user a switch.
How to improve
- Say in the description WHEN to use the skill ("use when…", example requests): that is the agent's main cue.
- For Hermes the description must be one sentence under 60 characters; move the conditions to a "When to Use" section.
- The text references files that are not there: add them or drop the references.
- 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 · 1
✓ No critical or high findings
Medium and low: 1
-
medium Exfiltration
net-credential-useSKILL.md:380Credential used in a network call (verify the destination is the intended service)curl -H "Authorization: Bearer $OPENCLAW_GATEWAY_TOKEN" \
Files scanned: 10. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
name-formatname should be kebab-case (lowercase letters, digits, hyphens) - warning
description-long-hermesdescription is 259 chars; the Hermes authoring standard requires ≤ 60 (one sentence, ending with a period) - warning
description-no-whenneither description nor a "## When to Use" section says when to use the skill - warning
missing-refreference to a missing file: LICENSE - note
frontmatter-keyunknown frontmatter key "id" - note
frontmatter-keyunknown frontmatter key "minOpenClawVersion" - note
frontmatter-keyunknown frontmatter key "runtime" - note
frontmatter-keyunknown frontmatter key "permissions"
Process rating: all ten parameters 33/100
- 0Tools and files. 1 referenced file(s) missing: LICENSE
- 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. 3 mutating operations with no state check
- 40Consistency. Frontmatter name (Telegram News Digest (Lite)) differs from the folder (tg-news-digest-lite)
- 50Failures and branches. 0 branches, has a failure section
- 100Steps. 25 steps
- 100Execution cost. Instruction body is 3620 tokens
- low 12 top-level sections: this looks like several domains in one skill
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
- -230 emoji in the instructions: noise for the model
- +2Single-language instructions
- +3Description length 258: enough signal without eating the budget
- +4Structure: 39 headings
- +3Step-by-step instructions: 25 items
- +4Has examples (20 code blocks)
- +1License stated
Quality base 70; lint remarks subtract, signals add up to 100. Result: 51.