SKILLEMALL.ai
GitHub ↗ RU Sign in

BB telegram

Integracao completa com Telegram Bot API. Setup com BotFather, mensagens, webhooks, inline keyboards, grupos, canais. Boilerplates Node.js e Python.

sickn33/agentic-awesome-skills Agent Skills author: sickn33 MIT 22 files body ≈ 318 tokens Open the sourcegithub.com↗ analyzed 2 d ago

Integracao completa com Telegram Bot API.

As a process B 76/100 · Nearly there — weak spots: result and completion, failures and branches, progress reporting

IntegrationTelegramCustomer supportSoftware developmenttype and topics are labelled automatically from the skill text
Runs in: Claude / Claude Code ChatGPT / Codex Gemini CLI Cursor GitHub Copilot / VS Code Qwen Code Kimi Code CLI Z.ai (GLM) DeepSeek (Deep Code) Mistral Vibe LangChain (deepagents) OpenClaw Goose OpenCode
JSON
Technical rating
B
75/100
safety, quality, tests
Safety 60%
73
Quality 40%
78
Run on models
none yet
Process rating
B
76/100
Nearly there
Failures and branches w 10
0
Progress reporting w 2
0
Result and completion w 14
40
the three weakest of ten parameters · all ten
This is a copy of a skill from another catalog; the rating counts the canonical one: telegram (sickn33/agentic-awesome-skills)

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

    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-webhook-url references/webhook-setup.md:215
      Webhook / callback URL commonly used for exfiltration (verify the destination) (quoted — discussed, not commanded)
      ngrok fornece URL tipo `https://abc1…app`. Use essa URL para registrar o webhook.
      quoted
    • low Secrets in code secret-high-entropy-token assets/boilerplate/nodejs/package-lock.json:79
      High-entropy token-like string (may be an id, hash or a credential) (detector / deny-list definition)
      "integrity": "sha5…xCA+ORZv…wO5/ywWF…Tag==",
      detector
    • low Secrets in code secret-high-entropy-token assets/boilerplate/nodejs/package-lock.json:225
      High-entropy token-like string (may be an id, hash or a credential) (detector / deny-list definition)
      "integrity": "sha5…Hra/JILC…zl8+mJRc…9PI+6Xbq…zjQ==",
      detector
    • low Secrets in code secret-high-entropy-token assets/boilerplate/nodejs/package-lock.json:232
      High-entropy token-like string (may be an id, hash or a credential) (detector / deny-list definition)
      "integrity": "sha5…ibj+tODHI5/+l06Au2Pcriv/Gmet…weg==",
      detector
    • low Secrets in code secret-high-entropy-token assets/boilerplate/nodejs/package-lock.json:283
      High-entropy token-like string (may be an id, hash or a credential) (detector / deny-list definition)
      "integrity": "sha5…B4t+D+OBkj…bcE+mWTyvVV7D/zsdE…1Rw==",
      detector
    • low Secrets in code secret-high-entropy-token assets/boilerplate/nodejs/package-lock.json:297
      High-entropy token-like string (may be an id, hash or a credential) (detector / deny-list definition)
      "integrity": "sha5…MfZ+71RA…HvA==",
      detector
    • low Exfiltration exfil-webhook-url assets/boilerplate/python/webhook_server.py:89
      Webhook / callback URL commonly used for exfiltration (verify the destination) (the skill's own vendor host; quoted — discussed, not commanded)
      url = f"https://api.telegram.org/bot{TOKEN}/setWebhook"
      vendor-hostquoted
    • low Exfiltration exfil-webhook-url references/advanced-features.md:332
      Webhook / callback URL commonly used for exfiltration (verify the destination) (the skill's own vendor host; quoted — discussed, not commanded)
      BASE = f"https://api.telegram.org/bot{TOKEN}"
      vendor-hostquoted
    • low Exfiltration exfil-webhook-url references/api-reference.md:19
      Webhook / callback URL commonly used for exfiltration (verify the destination) (placeholder value)
      **Base URL:** `https://api.telegram.org/bot<TOKEN>/<METHOD>`
      placeholder
    • low Exfiltration exfil-webhook-url references/detailed-guide.md:18
      Webhook / callback URL commonly used for exfiltration (verify the destination) (placeholder value)
      **Base URL:** `https://api.telegram.org/bot<TOKEN>/METHOD_NAME`
      placeholder
    • low Exfiltration exfil-webhook-url references/detailed-guide.md:160
      Webhook / callback URL commonly used for exfiltration (verify the destination) (the skill's own vendor host; quoted — discussed, not commanded)
      BASE = f"https://api.telegram.org/bot{TOKEN}"
      vendor-hostquoted
    • low Exfiltration exfil-webhook-url references/detailed-guide.md:364
      Webhook / callback URL commonly used for exfiltration (verify the destination) (the skill's own vendor host; quoted — discussed, not commanded)
      BASE = f"https://api.telegram.org/bot{TOKEN}"
      vendor-hostquoted
    • low Exfiltration exfil-webhook-url references/detailed-guide.md:407
      Webhook / callback URL commonly used for exfiltration (verify the destination) (the skill's own vendor host; quoted — discussed, not commanded)
      curl -X POST "https://api.telegram.org/bot$TOKEN/setMyCommands" \
      vendor-hostquoted
    • low Exfiltration net-credential-use references/detailed-guide.md:407
      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$TOKEN/setMyCommands" \
      vendor-host
    • low Exfiltration exfil-webhook-url references/webhook-setup.md:27
      Webhook / callback URL commonly used for exfiltration (verify the destination) (placeholder value)
      POST https://api.telegram.org/bot<TOKEN>/setWebhook
      placeholder
    • low Exfiltration exfil-webhook-url references/webhook-setup.md:38
      Webhook / callback URL commonly used for exfiltration (verify the destination) (placeholder value)
      GET https://api.telegram.org/bot<TOKEN>/getWebhookInfo
      placeholder
    • low Exfiltration exfil-webhook-url references/webhook-setup.md:43
      Webhook / callback URL commonly used for exfiltration (verify the destination) (placeholder value)
      POST https://api.telegram.org/bot<TOKEN>/deleteWebhook
      placeholder
    • low Exfiltration exfil-webhook-url references/webhook-setup.md:143
      Webhook / callback URL commonly used for exfiltration (verify the destination) (the skill's own vendor host; quoted — discussed, not commanded)
      f'https://api.telegram.org/bot{TOKEN}/setWebhook',
      vendor-hostquoted
    • low Exfiltration net-credential-use references/webhook-setup.md:218
      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$TOKEN/setWebhook" \
      vendor-host
    • low Exfiltration exfil-webhook-url scripts/send_message.py:42
      Webhook / callback URL commonly used for exfiltration (verify the destination) (the skill's own vendor host; quoted — discussed, not commanded)
      url = f"https://api.telegram.org/bot{token}/{method}"
      vendor-hostquoted
    • low Exfiltration read-dotenv scripts/setup_project.py:51
      Reads a .env file (quoted — discussed, not commanded)
      print("  3. Copy .env.example to .env and add your bot token")
      quoted
    • low Exfiltration read-dotenv scripts/setup_project.py:76
      Reads a .env file (quoted — discussed, not commanded)
      print("  3. Copy .env.example to .env and add your bot token")
      quoted
    • low Exfiltration exfil-webhook-url scripts/test_bot.py:27
      Webhook / callback URL commonly used for exfiltration (verify the destination) (test fixture / example file; the skill's own vendor host; quoted — discussed, not commanded)
      base_url = f"https://api.telegram.org/bot{token}"
      fixturevendor-hostquoted

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

    Against the Agent Skills spec

    • note frontmatter-key unknown frontmatter key "risk"
    • note frontmatter-key unknown frontmatter key "source"
    • note frontmatter-key unknown frontmatter key "date_added"
    • note frontmatter-key unknown frontmatter key "tools"

    Process rating: all ten parameters 76/100

    • 0Failures and branches. Linear process with no failure handling
    • 0Progress reporting. Says nothing while it works
    • 40Result and completion. Does not say what the result is
    • 70Inputs and preconditions. Inputs and preconditions are listed
    • 100Tools and files. Tools declared in frontmatter
    • 100Steps. 12 steps
    • 100When it triggers. States when to use and when not to
    • 100Consistency. Name and required fields are in place
    • 100Execution cost. Instruction body is 318 tokens
    • 100Running it twice. No mutating operations

    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
    • +4No input/output examples
    • -33 of 3 scripts are never mentioned in SKILL.md
    • +1No license
    • +2Single-language instructions
    • +3Description length 148: enough signal without eating the budget
    • +4Structure: 5 headings
    • +3Step-by-step instructions: 12 items
    • +4Reference files are cited in the instructions (1 of 5)

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