Telegram Inline Buttons

v0.1.0

Use inline buttons when communicating with Rahul on Telegram (message tool) to reduce typing and force crisp decisions. Trigger when drafting Telegram messag...

0· 360·2 current·2 all-time
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
VirusTotalVirusTotal
Benign
View report →
OpenClawOpenClaw
Benign
high confidence
Purpose & Capability
The name/description (Telegram inline buttons for Rahul) match the SKILL.md content. There are no unrelated environment variables, binaries, or installs declared; all instructions focus on composing and handling inline-button flows in Telegram.
Instruction Scope
The runtime instructions are limited to message composition, button layout, callback handling, and message-edit behavior. They do not ask the agent to read files, access unrelated environment variables, or transmit data to external endpoints beyond the implied Telegram message tool. The directive to use 'NO_REPLY' when using functions.message is an internal UI/tooling convention, not an exfiltration instruction.
Install Mechanism
No install spec and no code files — instruction-only. Nothing will be written to disk or downloaded during install.
Credentials
The skill declares no required environment variables, credentials, or config paths. That is proportionate for a messaging/UI guideline skill.
Persistence & Privilege
always is false and the skill is user-invocable; the skill can be invoked autonomously by the agent (platform default) but that is not combined with broad privileges or credential access.
Assessment
This skill is low-risk and simply prescribes how to use inline buttons in Telegram conversations. Before installing, confirm you want the agent to automatically edit messages and silently ignore stale callbacks (that behavior can hide confirmations). Also ensure your agent already has legitimate Telegram credentials/permissions configured elsewhere (this skill does not request them). Test flows in a safe chat to verify callbacks, callback_data uniqueness, and that 'NO_REPLY' behavior doesn't suppress information you expect to see.

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

latestvk97fqcd6mb90z4p5r9f9bsaxz981yx1q

License

MIT-0
Free to use, modify, and redistribute. No attribution required.

Comments