SKILLEMALL.ai

DC channel-reminders

(no description)

Not recommendedlow grade D
ClawHub Agent Skills author: alex3alex v1.3.0 3 files body ≈ 2 471 tokens Open the sourceclawhub.ai analyzed 3 d ago

As a process C 51/100 · Has gaps — weak spots: result and completion, when it triggers, inputs and preconditions

ReferenceTelegramInfrastructuretype and topics are labelled automatically from the skill text
JSON
Technical rating
D
59/100
safety, quality, tests
Safety 60%
99
Quality 40%
0
Run on models
none yet
Process rating
C
51/100
Has gaps
Result and completion w 14
0
When it triggers w 12
0
Inputs and preconditions w 11
0
the three weakest of ten parameters · all ten

How to improve

  1. Add a description to the frontmatter: without it the skill never triggers.
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 · 1

✓ No critical or high findings

Medium and low: 1
  • low Exfiltration exfil-webhook-url SKILL.md:151
    Webhook / callback URL commonly used for exfiltration (verify the destination) (placeholder value)
    curl "https://api.telegram.org/bot<BOT_TOKEN>/getUpdates" | jq '.result[].message.chat.id'
    placeholder

Files scanned: 3. Evidence is masked. Grey chips explain why severity was lowered.

Against the Agent Skills spec

  • error frontmatter SKILL.md: no YAML frontmatter block found
  • error name-missing SKILL.md: frontmatter has no `name`
  • error description-missing SKILL.md: no `description` — the skill can never trigger

Process rating: all ten parameters 51/100

  • 0Result and completion. Does not say what the result is
  • 0When it triggers. No condition that starts the skill
  • 0Inputs and preconditions. Does not say what the process needs to start
  • 0Failures and branches. Linear process with no failure handling
  • 0Progress reporting. Says nothing while it works
  • 100Tools and files. No external tools needed
  • 100Steps. 17 steps
  • 100Consistency. Name and required fields are in place
  • 100Execution cost. Instruction body is 2471 tokens
  • 100Running it twice. No mutating operations
  • low 11 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)
  • +3Description length 0: 120–800 characters recommended
  • +3Output format is not stated: the model decides each time
  • -214 emoji in the instructions: noise for the model
  • +1No license
  • +4Structure: 35 headings
  • +3Step-by-step instructions: 17 items
  • +4Has examples (22 code blocks)
  • +2Bilingual instructions (RU + EN)

Quality base 70; lint remarks subtract, signals add up to 100. Result: 0.

External checks

ClawHub: suspicious
This reminder skill has a legitimate purpose, but it gives persistent automation broad Telegram message-sending authority without enough recipient, account, or event-origin controls.
LLM: suspicious (high) · VirusTotal: suspicious · 28 May 2026