SKILLEMALL.ai

DD telegram-voice-message-skill

(no description)

Not recommendedlow grade D
ClawHub Agent Skills author: shynloc v1.0.0 MIT-0 21 files · 6 scripts body ≈ 770 tokens Open the sourceclawhub.ai analyzed 3 d ago

As a process D 44/100 · Unfinished process — weak spots: result and completion, when it triggers, inputs and preconditions

ProcedureTelegramInfrastructuretype and topics are labelled automatically from the skill text
JSON
Technical rating
D
41/100
safety, quality, tests
Safety 60%
69
Quality 40%
0
Run on models
none yet
Process rating
D
44/100
Unfinished process
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

What is at stake

Medium-severity findings: the skill is probably honest, but read what alarmed the scanner.

Exfiltration medium severity

Below is the worst case for this category. The finding here is medium: the guard saw a sign, not a proof.

If you install

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".

For the author

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

  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 · 23

✓ No critical or high findings

Medium and low: 23
  • medium Exfiltration exfil-secret-in-url docs/api-integration.md:514
    Credential passed in a URL query string (normal for some APIs — verify the host is the intended service) (quoted — discussed, not commanded)
    curl -X POST "https://qyapi.weixin.qq.com/cgi-bin/webhook/send?key=…" \
    quoted
  • medium Exfiltration net-credential-use docs/api-integration.md:514
    Credential used in a network call (verify the destination is the intended service)
    curl -X POST "https://qyapi.weixin.qq.com/cgi-bin/webhook/send?key=…" \
  • low Exfiltration exfil-webhook-url docs/api-integration.md:324
    Webhook / callback URL commonly used for exfiltration (verify the destination) (placeholder value)
    -X POST "https://api.telegram.org/bot$TELEGRAM_BOT_TOKEN/sendVoice" \
    placeholder
  • low Exfiltration exfil-webhook-url docs/api-integration.md:451
    Webhook / callback URL commonly used for exfiltration (verify the destination) (placeholder value)
    export SLACK_WEBHOOK_URL="https://hooks.slack.com/services/..."
    placeholder
  • low Exfiltration exfil-webhook-url docs/api-integration.md:486
    Webhook / callback URL commonly used for exfiltration (verify the destination) (placeholder value)
    export DISCORD_WEBHOOK_URL="https://discord.com/api/webhooks/..."
    placeholder
  • low Exfiltration exfil-webhook-url docs/api-integration.md:741
    Webhook / callback URL commonly used for exfiltration (verify the destination) (placeholder value)
    if curl -s "https://api.telegram.org/bot$TELEGRAM_BOT_TOKEN/getMe" | grep -q '"ok":true'; then
    placeholder
  • low Exfiltration net-credential-use docs/api-integration.md:741
    Credential used in a network call (verify the destination is the intended service) (the skill's own vendor host)
    if curl -s "https://api.telegram.org/bot$TELEGRAM_BOT_TOKEN/getMe" | grep -q '"ok":true'; then
    vendor-host
  • low Exfiltration exfil-webhook-url docs/best-practices.md:50
    Webhook / callback URL commonly used for exfiltration (verify the destination) (placeholder value)
    curl -X POST "https://api.telegram.org/bot$TELEGRAM_BOT_TOKEN/sendVoice" \
    placeholder
  • low Exfiltration net-credential-use docs/best-practices.md:50
    Credential used in a network call (verify the destination is the intended service) (the skill's own vendor host)
    curl -X POST "https://api.telegram.org/bot$TELEGRAM_BOT_TOKEN/sendVoice" \
    vendor-host
  • low Exfiltration exfil-webhook-url docs/best-practices.md:57
    Webhook / callback URL commonly used for exfiltration (verify the destination) (placeholder value)
    curl -X POST "https://api.telegram.org/bot$TELEGRAM_BOT_TOKEN/sendAudio" \
    placeholder
  • low Exfiltration net-credential-use docs/best-practices.md:57
    Credential used in a network call (verify the destination is the intended service) (the skill's own vendor host)
    curl -X POST "https://api.telegram.org/bot$TELEGRAM_BOT_TOKEN/sendAudio" \
    vendor-host
  • low Exfiltration exfil-webhook-url examples/error-examples.md:17
    Webhook / callback URL commonly used for exfiltration (verify the destination) (placeholder value)
    curl -X POST "https://api.telegram.org/bot${TELEGRAM_BOT_TOKEN}/sendAudio" \
    placeholder
  • low Exfiltration net-credential-use examples/error-examples.md:17
    Credential used in a network call (verify the destination is the intended service) (test fixture / example file; the skill's own vendor host)
    curl -X POST "https://api.telegram.org/bot${TELEGRAM_BOT_TOKEN}/sendAudio" \
    fixturevendor-host
  • low Exfiltration exfil-webhook-url examples/error-examples.md:35
    Webhook / callback URL commonly used for exfiltration (verify the destination) (placeholder value)
    curl -X POST "https://api.telegram.org/bot${TELEGRAM_BOT_TOKEN}/sendVoice" \
    placeholder
  • low Exfiltration net-credential-use examples/error-examples.md:35
    Credential used in a network call (verify the destination is the intended service) (test fixture / example file; the skill's own vendor host)
    curl -X POST "https://api.telegram.org/bot${TELEGRAM_BOT_TOKEN}/sendVoice" \
    fixturevendor-host
  • low Exfiltration exfil-webhook-url examples/error-examples.md:50
    Webhook / callback URL commonly used for exfiltration (verify the destination) (placeholder value)
    curl -X POST "https://api.telegram.org/bot${TELEGRAM_BOT_TOKEN}/sendAudio" \
    placeholder
  • low Exfiltration net-credential-use examples/error-examples.md:50
    Credential used in a network call (verify the destination is the intended service) (test fixture / example file; the skill's own vendor host)
    curl -X POST "https://api.telegram.org/bot${TELEGRAM_BOT_TOKEN}/sendAudio" \
    fixturevendor-host
  • low Exfiltration exfil-webhook-url examples/error-examples.md:63
    Webhook / callback URL commonly used for exfiltration (verify the destination) (placeholder value)
    curl -X POST "https://api.telegram.org/bot${TELEGRAM_BOT_TOKEN}/sendVoice" \
    placeholder
  • low Exfiltration net-credential-use examples/error-examples.md:63
    Credential used in a network call (verify the destination is the intended service) (test fixture / example file; the skill's own vendor host)
    curl -X POST "https://api.telegram.org/bot${TELEGRAM_BOT_TOKEN}/sendVoice" \
    fixturevendor-host
  • low Exfiltration exfil-webhook-url examples/error-examples.md:78
    Webhook / callback URL commonly used for exfiltration (verify the destination) (placeholder value)
    curl -X POST "https://api.telegram.org/bot${TELEGRAM_BOT_TOKEN}/sendVoice" \
    placeholder
  • low Exfiltration net-credential-use examples/error-examples.md:78
    Credential used in a network call (verify the destination is the intended service) (test fixture / example file; the skill's own vendor host)
    curl -X POST "https://api.telegram.org/bot${TELEGRAM_BOT_TOKEN}/sendVoice" \
    fixturevendor-host
  • low Exfiltration read-dotenv README.md:25
    Reads a .env file
    cp templates/.env.example .env
  • low Exfiltration exfil-webhook-url scripts/telegram_sender.sh:170
    Webhook / callback URL commonly used for exfiltration (verify the destination) (placeholder value)
    local api_url="https://api.telegram.org/bot${TELEGRAM_BOT_TOKEN}/sendVoice"
    placeholder

Files scanned: 21. 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 44/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
  • 60Tools and files. Uses tools (bash) that frontmatter does not declare
  • 100Steps. 60 steps
  • 100Consistency. Name and required fields are in place
  • 100Execution cost. Instruction body is 770 tokens
  • 100Running it twice. No mutating operations
  • 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)
  • +3Description length 0: 120–800 characters recommended
  • +3Output format is not stated: the model decides each time
  • -213 emoji in the instructions: noise for the model
  • -33 of 6 scripts are never mentioned in SKILL.md
  • +1No license
  • +2Single-language instructions
  • +4Structure: 30 headings
  • +3Step-by-step instructions: 60 items
  • +4Has examples (2 code blocks)
  • +4Reference files are cited in the instructions (4 of 4)

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

External checks

ClawHub: suspicious
This Telegram voice-message skill is mostly purpose-aligned, but it includes runnable examples and scripts with command-execution and unsafe automation patterns that deserve manual review before use.
LLM: suspicious (high) · VirusTotal: · 29 May 2026