SKILLEMALL.ai

BD Telegram Bot Builder

This skill should be used when the user asks to "create a Telegram bot", "build a Telegram chatbot", "set up a Telegram webhook", "add inline keyboards to a bot", "handle Telegram callback queries", "implement Telegram payments", "send media via Telegram bot", "configure Telegram bot commands", "deploy a Telegram bot", or mentions the Telegram Bot API, telegram bot tokens, getUpdates, setWebhook, or bot frameworks like node-telegram-bot-api, grammy, python-telegram-bot, or aiogram. Provides comprehensive guidance for building production-ready Telegram bots with Node.js and Python.

davila7/claude-code-templates Agent Skills author: davila7 MIT 4 files body ≈ 2 054 tokens Open the sourcegithub.com↗ analyzed 6 d ago

This skill should be used when the user asks to "create a Telegram bot", "build a Telegram chatbot", "set up a Telegram webhook", "add inline keyboards to a…

As a process D 37/100 · Unfinished process — References files that are not bundled: url

IntegrationTelegramDockerSoftware developmentInfrastructuretype and topics are labelled automatically from the skill text
JSON
Technical rating
B
91/100
safety, quality, tests
Safety 60%
97
Quality 40%
82
Run on models
none yet
Process rating
D
37/100
Unfinished process
References files that are not bundled: url
Tools and files w 18
0
Result and completion w 14
0
Inputs and preconditions w 11
0
the three weakest of ten parameters · all ten

The same skill appears in 1 more place: RA-Skills

How to improve

  1. The text references files that are not there: add them or drop the references.
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 · 3

✓ No critical or high findings

Medium and low: 3
  • low Exfiltration exfil-webhook-url reference/api_methods.md:3
    Webhook / callback URL commonly used for exfiltration (verify the destination) (placeholder value)
    > Based on Bot API 9.4 (February 2026). Base URL: `https://api.telegram.org/bot<token>/METHOD_NAME`
    placeholder
  • low Secrets in code secret-high-entropy-token reference/api_methods.md:191
    High-entropy token-like string (may be an id, hash or a credential) (quoted — discussed, not commanded)
    **Result types:** `InlineQueryResultArticle`, `InlineQueryResultPhoto`, `InlineQueryResultGif`, `Inli…Gif`, `InlineQueryResultVideo`, `InlineQueryResultAudio`, `InlineQueryResultVoice
    quoted
  • low Exfiltration exfil-webhook-url SKILL.md:29
    Webhook / callback URL commonly used for exfiltration (verify the destination) (placeholder value)
    All API calls go to: `https://api.telegram.org/bot<TOKEN>/METHOD_NAME`
    placeholder

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

Against the Agent Skills spec

  • warning name-format name should be kebab-case (lowercase letters, digits, hyphens)
  • warning missing-ref reference to a missing file: url

Process rating: all ten parameters 37/100

Will not run. References files that are not bundled: url
  • 0Tools and files. 1 referenced file(s) missing: url
  • 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
  • 30Running it twice. 20 mutating operations with no state check
  • 40Consistency. Frontmatter name (Telegram Bot Builder) differs from the folder (telegram-bot-builder)
  • 50Failures and branches. 0 branches, has a failure section
  • 70When it triggers. States when to use, but not when not to
  • 85Steps. 31 steps, 1 vague phrases
  • 100Execution cost. Instruction body is 2054 tokens
  • medium Safety rules and hard prohibitions inside a skill: they belong in the system prompt, here they protect nothing
  • low The response is described with custom markup (3 tags): a typed call is more reliable

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

  • +4Description does not say when NOT to use the skill (false activations)
  • +3Output format is not stated: the model decides each time
  • +1No license
  • +2Single-language instructions
  • +5Description quotes 9 example trigger phrases
  • +3Description length 587: enough signal without eating the budget
  • +4Structure: 19 headings
  • +3Step-by-step instructions: 31 items
  • +4Has examples (11 code blocks)
  • +4Reference files are cited in the instructions (3 of 3)

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