ClawHub

Lovefromio Telegram

v1.0.0

OpenClaw skill for designing Telegram Bot API workflows and command-driven conversations using direct HTTPS requests (no SDKs).

⭐ 0· 38·1 current·1 all-time
byAI@lovefromio

Install

OpenClaw Prompt Flow

Install with OpenClaw

Best for remote or guided setup. Copy the exact prompt, then paste it into OpenClaw for lovefromio/lovefromio-telegram.

Previewing Install & Setup.
Prompt PreviewInstall & Setup
Install the skill "Lovefromio Telegram" (lovefromio/lovefromio-telegram) from ClawHub.
Skill page: https://clawhub.ai/lovefromio/lovefromio-telegram
Keep the work scoped to this skill only.
After install, inspect the skill metadata and help me finish setup.
Use only the metadata you can verify from ClawHub; do not invent missing requirements.
Ask before making any broader environment changes.

Command Line

CLI Commands

Use the direct CLI path if you want to install manually and keep every step visible.

OpenClaw CLI

Bare skill slug

openclaw skills install lovefromio-telegram

ClawHub CLI

Package manager switcher

npx clawhub@latest install lovefromio-telegram
Security Scan
VirusTotalVirusTotal
Benign
View report →
OpenClawOpenClaw
Benign
high confidence
✓
Purpose & Capability
Name/description (designing Telegram Bot API workflows via direct HTTPS) matches the contents: references and SKILL.md provide request templates, routing, UX, and error handling. Required inputs (bot token, API URL, update strategy) are appropriate for the stated purpose.
✓
Instruction Scope
SKILL.md and reference files restrict themselves to HTTP call patterns, update routing, command UX, and operational/security guidance (e.g., do not log tokens, use webhook secret). There are no instructions to read unrelated files, access system state, or transmit data to unexpected endpoints.
✓
Install Mechanism
No install spec and no code files — the skill is instruction-only, which minimizes on-disk execution and risk.
✓
Credentials
The skill does not declare or require environment variables or other credentials in the registry metadata. It sensibly expects a Telegram bot token as an input for operation; that is proportional and expected for a Telegram integration.
✓
Persistence & Privilege
always is false and the skill does not request any system or platform-wide privileges. Autonomous invocation is allowed (platform default) but presents no additional incoherence given the skill's content.
Scan Findings in Context
[no-findings] expected: The regex-based scanner had nothing to analyze because this is an instruction-only skill; that is consistent with the provided artifacts.
Assessment
This skill is a documentation-style guide for building Telegram bots and appears coherent. Before using it, remember: do not hand over your real bot token to untrusted agents — the token enables full control of your bot. Prefer creating a test bot/token when experimenting. Use the recommended webhook secret, avoid logging tokens, and store credentials securely (environment variables or secret manager) outside chat history. If you plan to let the agent act autonomously with your token, review what operations it will perform (sendMessage, setWebhook, etc.) and restrict the token's scope by using a separate test bot if possible.

Like a lobster shell, security has layers — review code before you run it.

latestvk974aszt940vxfsf8janpcm18585mngz
38downloads
0stars
1versions
Updated 1d ago
v1.0.0
MIT-0
AI@lovefromio
latest
Download

Telegram Bot Skill (Advanced)

Purpose

Provide a clean, production-oriented guide for building Telegram bot workflows via the Bot API, focusing on command UX, update handling, and safe operations using plain HTTPS.

Best fit

  • You want a command-first bot that behaves professionally.
  • You need a reliable update flow (webhook or polling).
  • You prefer direct HTTP calls instead of libraries.

Not a fit

  • You require a full SDK or framework integration.
  • You need complex media uploads and streaming in-process.

Quick orientation

  • Read references/telegram-bot-api.md for endpoints, update types, and request patterns.
  • Read references/telegram-commands-playbook.md for command UX and messaging style.
  • Read references/telegram-update-routing.md for update normalization and routing rules.
  • Read references/telegram-request-templates.md for HTTP payload templates.
  • Keep this SKILL.md short and use references for details.

Required inputs

  • Bot token and base API URL.
  • Update strategy: webhook or long polling.
  • Command list and conversation tone.
  • Allowed update types and rate-limit posture.

Expected output

  • A clear command design, update flow plan, and operational checklist.

Operational notes

  • Prefer strict command routing: /start, /help, /settings, /status.
  • Always validate incoming update payloads and chat context.
  • Handle 429s with backoff and avoid message bursts.

Security notes

  • Never log tokens.
  • Use webhooks with a secret token header when possible.

Comments

Loading comments...