BC telegram-bot-manager
Manage and configure Telegram bots for OpenClaw. Use when setting up Telegram integrations, troubleshooting bot connectivity, configuring bot tokens, or managing Telegram channel/webhook settings. Handles bot registration, token validation, and network connectivity checks for api.telegram.org.
Manage and configure Telegram bots for OpenClaw.
As a process C 53/100 · Has gaps — weak spots: result and completion, when it triggers, inputs and preconditions
How to improve
- 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 · 12
✓ No critical or high findings
Medium and low: 12
-
low Exfiltration
exfil-webhook-urlreferences/OPENCLAW_CONFIG.md:106Webhook / callback URL commonly used for exfiltration (verify the destination) (placeholder value)curl -s "https://api.telegram.org/botYOUR_TOKEN/getMe"
placeholder -
low Exfiltration
exfil-webhook-urlreferences/OPENCLAW_CONFIG.md:245Webhook / callback URL commonly used for exfiltration (verify the destination) (placeholder value)"https://api.telegram.org/botYOUR_TOKEN/setWebhook"
placeholder -
low Exfiltration
exfil-webhook-urlreferences/OPENCLAW_CONFIG.md:251Webhook / callback URL commonly used for exfiltration (verify the destination) (placeholder value)curl "https://api.telegram.org/botYOUR_TOKEN/deleteWebhook"
placeholder -
low Exfiltration
exfil-webhook-urlreferences/WEBHOOK_SETUP.md:96Webhook / callback URL commonly used for exfiltration (verify the destination) (placeholder value)"https://api.telegram.org/botYOUR_BOT_TOKEN/setWebhook"
placeholder -
low Exfiltration
exfil-webhook-urlreferences/WEBHOOK_SETUP.md:99Webhook / callback URL commonly used for exfiltration (verify the destination) (placeholder value)curl "https://api.telegram.org/botYOUR_BOT_TOKEN/getWebhookInfo"
placeholder -
low Exfiltration
exfil-webhook-urlreferences/WEBHOOK_SETUP.md:243Webhook / callback URL commonly used for exfiltration (verify the destination) (placeholder value)curl "https://api.telegram.org/botYOUR_BOT_TOKEN/getWebhookInfo"
placeholder -
low Exfiltration
exfil-webhook-urlreferences/WEBHOOK_SETUP.md:365Webhook / callback URL commonly used for exfiltration (verify the destination) (placeholder value)STATUS=$(curl -s "https://api.telegram.org/bot$BOT_TOKEN/getWebhookInfo" | jq -r '.result.url')
placeholder -
low Exfiltration
net-credential-usereferences/WEBHOOK_SETUP.md:365Credential used in a network call (verify the destination is the intended service) (the skill's own vendor host)STATUS=$(curl -s "https://api.telegram.org/bot$BOT_TOKEN/getWebhookInfo" | jq -r '.result.url')
vendor-host -
low Exfiltration
exfil-webhook-urlreferences/WEBHOOK_SETUP.md:382Webhook / callback URL commonly used for exfiltration (verify the destination) (placeholder value)curl "https://api.telegram.org/botYOUR_BOT_TOKEN/deleteWebhook"
placeholder -
low Exfiltration
exfil-webhook-urlscripts/setup_bot.py:136Webhook / 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{bot_token}/getMe",vendor-hostquoted -
low Exfiltration
exfil-webhook-urlscripts/test_bot.py:17Webhook / callback URL commonly used for exfiltration (verify the destination) (test fixture / example file; the skill's own vendor host; quoted — discussed, not commanded)self.base_url = f"https://api.telegram.org/bot{bot_token}"fixturevendor-hostquoted -
low Exfiltration
exfil-webhook-urlSKILL.md:30Webhook / callback URL commonly used for exfiltration (verify the destination) (placeholder value)curl -s "https://api.telegram.org/bot<YOUR_TOKEN>/getMe"
placeholder
Files scanned: 10. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
✓ No remarks against the Agent Skills spec
Process rating: all ten parameters 53/100
- 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. 2 mutating operations with no state check
- 50Failures and branches. 0 branches, has a failure section
- 85Steps. 46 steps, 1 vague phrases
- 100Tools and files. No external tools needed
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 781 tokens
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
- -32 of 3 scripts are never mentioned in SKILL.md
- +1No license
- +2Single-language instructions
- +3Description length 294: enough signal without eating the budget
- +4Structure: 18 headings
- +3Step-by-step instructions: 46 items
- +4Has examples (4 code blocks)
- +4Reference files are cited in the instructions (2 of 2)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 85.