Telegram
bubbuild/bub
Telegram Bot skill for sending and editing Telegram messages via Bot API.
Adds a new field to the Update type and wires it through ProcessedUpdate, UpdateType, ProcessUpdate, KSP (TypeConstants, TypeMapper), and FunctionalDSLUtils.
Install Add Telegram Update Field
$ npx skills add vendelieu/telegram-bot --skill add-telegram-update-field -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install vendelieu/telegram-bot add-telegram-update-field --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/vendelieu/telegram-bot.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.cursor/skills/add-telegram-update-field .claude/skills/add-telegram-update-field && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "add-telegram-update-field" agent skill from https://github.com/vendelieu/telegram-bot/tree/master/.cursor/skills/add-telegram-update-field into .claude/skills/add-telegram-update-field/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "add-telegram-update-field", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/vendelieu/telegram-bot/tree/master/.cursor/skills/add-telegram-update-fieldType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add vendelieu/telegram-bot --skill add-telegram-update-field -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install vendelieu/telegram-bot add-telegram-update-field --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/vendelieu/telegram-bot.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.cursor/skills/add-telegram-update-field .agents/skills/add-telegram-update-field && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "add-telegram-update-field" agent skill from https://github.com/vendelieu/telegram-bot/tree/master/.cursor/skills/add-telegram-update-field into .agents/skills/add-telegram-update-field/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "add-telegram-update-field", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add vendelieu/telegram-bot --skill add-telegram-update-field -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install vendelieu/telegram-bot add-telegram-update-field --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/vendelieu/telegram-bot.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.cursor/skills/add-telegram-update-field .cursor/skills/add-telegram-update-field && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "add-telegram-update-field" agent skill from https://github.com/vendelieu/telegram-bot/tree/master/.cursor/skills/add-telegram-update-field into .cursor/skills/add-telegram-update-field/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "add-telegram-update-field", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/vendelieu/telegram-bot.git --path .cursor/skills/add-telegram-update-field--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add vendelieu/telegram-bot --skill add-telegram-update-field -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install vendelieu/telegram-bot add-telegram-update-field --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/vendelieu/telegram-bot.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.cursor/skills/add-telegram-update-field .gemini/skills/add-telegram-update-field && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "add-telegram-update-field" agent skill from https://github.com/vendelieu/telegram-bot/tree/master/.cursor/skills/add-telegram-update-field into .gemini/skills/add-telegram-update-field/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "add-telegram-update-field", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install vendelieu/telegram-bot add-telegram-update-fieldInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add vendelieu/telegram-bot --skill add-telegram-update-field -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/vendelieu/telegram-bot.git skills-src && mkdir -p .github/skills && cp -r skills-src/.cursor/skills/add-telegram-update-field .github/skills/add-telegram-update-field && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "add-telegram-update-field" agent skill from https://github.com/vendelieu/telegram-bot/tree/master/.cursor/skills/add-telegram-update-field into .github/skills/add-telegram-update-field/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "add-telegram-update-field", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add vendelieu/telegram-bot --skill add-telegram-update-field -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install vendelieu/telegram-bot add-telegram-update-field --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/vendelieu/telegram-bot.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.cursor/skills/add-telegram-update-field .opencode/skills/add-telegram-update-field && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "add-telegram-update-field" agent skill from https://github.com/vendelieu/telegram-bot/tree/master/.cursor/skills/add-telegram-update-field into .opencode/skills/add-telegram-update-field/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "add-telegram-update-field", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
add-telegram-update-field- GitHub stars
- 249
- Token cost
- ~841 tokens
- SKILL.md length
- 204 words
- Files
- 1
- Skills in repo
- 14
- Repo updated
- First seen
- Licence
- Apache-2.0
At a glance
Adds a new field to the Update type and wires it through ProcessedUpdate, UpdateType, ProcessUpdate, KSP (TypeConstants, TypeMapper), and FunctionalDSLUtils.
- Works in 6 steps: Add Field to Update → Add UpdateType Entry → Add ProcessedUpdate Subclass → …
- Implementing support for a new Telegram update type (e.g
- SKILL.md covers Workflow, Naming Conventions, Reference Examples and Validation
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Add Telegram Update Field is an agent skill from vendelieu/telegram-bot. Adds a new field to the Update type and wires it through ProcessedUpdate, UpdateType, ProcessUpdate, KSP (TypeConstants, TypeMapper), and FunctionalDSLUtils. Use when implementing support for a new Telegram update type (e.g. messagereaction, chatboost), adding a new update handler, or extending the bot to handle additional update kinds.
Its SKILL.md is about 840 tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in Productivity & Automation, covering Chatbots and conversational support and Android development. It works with Telegram and Kotlin. The repository describes itself as: Telegram Bot API wrapper with handy Kotlin DSL. The licence is Apache-2.0.
When your agent uses it
- Implementing support for a new Telegram update type (e.g
- Tasks that involve Chatbots and conversational support
- Tasks that involve Android development
Example prompts
- “/add-telegram-update-field”
Workflow steps
6 steps, taken from the step headings in SKILL.md.
What it can do on your machine
Read from SKILL.md and the folder at commit 1dbfd00. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md (its code samples are bash).
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Add Telegram Update Field loads about 841 tokens when it runs. Until then it costs about 92 tokens; SKILL.md has 204 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from vendelieu/telegram-bot at commit 1dbfd00, republished under its Apache-2.0 licence (© vendelieu). 204 words, ~841 tokens.
Download SKILL.mdSave it as
.claude/skills/add-telegram-update-field/SKILL.md (or your agent's skills folder).- name
- add-telegram-update-field
- description
- Adds a new field to the Update type and wires it through ProcessedUpdate, UpdateType, ProcessUpdate, KSP (TypeConstants, TypeMapper), and FunctionalDSLUtils. Use when implementing support for a new Telegram update type (e.g. message_reaction, chat_boost), adding a new update handler, or extending the bot to handle additional update kinds.
Add Telegram Update Field
Workflow
1. Add Field to Update
- In Update.kt: add
val myField: MyType? = null(camelCase, nullable) - Add import for the payload type if needed
2. Add UpdateType Entry
- In UpdateType.kt: add enum entry with
@SerialName("snake_case")matching Telegram API (e.g.MY_FIELD)
3. Add ProcessedUpdate Subclass
- In ProcessedUpdate.kt: add
data class MyFieldUpdate(...) : ProcessedUpdate(...) - Use
@Serializable(MyFieldUpdate.Companion::class)andinternal companion object : UpdateSerializer<MyFieldUpdate>() - Implement
UserReferencewhen the update has a user;ChatReferencewhen it has a chat;TextReferencewhen it has text
4. Add processUpdate Clause
- In ProcessUpdate.kt: add
myField != null -> MyFieldUpdate(updateId, this, myField) - Add import for the new ProcessedUpdate subclass
- Place clause in a logical order (group with similar update types)
5. Update KSP Module
- In TypeConstants.kt: add
val myFieldUpdateClass: TypeName = MyFieldUpdate::class.asTypeName() - In TypeMapper.kt: add
TypeConstants.myFieldUpdateClass to MyFieldUpdate::classtoupdateTypeMap
6. Regenerate FunctionalDSLUtils
- Run
./gradlew prepareRelease(or full build) - api-sentinel KSP regenerates FunctionalDSLUtils.kt from
UpdateType.entries; no manual edits needed
Handling: The new onXxx DSL function enables bot.setFunctionality { onXxx { ... } }. Both functional DSL and annotation approach (@UpdateHandler) use the same ActivityRegistry and ProcessingPipeline; see telegram-bot-handling.mdc.
Naming Conventions
- Update field: camelCase (e.g.
callbackQuery,messageReaction) - UpdateType: SCREAMING_SNAKE_CASE,
@SerialName("snake_case")matching Telegram API - ProcessedUpdate subclass:
XxxUpdate(e.g.CallbackQueryUpdate)
Reference Examples
- MessageUpdate - UserReference + ChatReference
- PollUpdate - minimal, no User/Chat
- CallbackQueryUpdate - UserReference + ChatReference
Validation
./gradlew formatKotlin
./gradlew prepareRelease© vendelieu, Apache-2.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
Just SKILL.md in .cursor/skills/add-telegram-update-field of vendelieu/telegram-bot.
Open the folder on GitHubat commit 1dbfd00
Compare with similar skills
Add Telegram Update Field next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Add Telegram Update Field this skillvendelieu/telegram-bot | 249 | — | ~841 | Automated safety check: Pass | Apache-2.0 | |
| Telegrambubbuild/bub | 1.7k | — | ~2.2k | Automated safety check: Pass | Apache-2.0 | |
| Pytdbotpytdbot/client | 137 | — | ~4.3k | Automated safety check: Pass | MIT | |
| Setupterranc/claude-telegram-bot-bridge | 134 | — | ~1.5k | Automated safety check: Notes | None | |
| MuseKevPH2026/muse-catch | 128 | — | ~1.6k | Automated safety check: Notes | AGPL-3.0 | |
| Actionizeinfranodus/skills | 119 | — | ~3.8k | Automated safety check: Notes | None |
Similar skills
Pytdbot
pytdbot/client
Write Telegram bots and userbots with Pytdbot (async TDLib wrapper with high-level helpers; not the Telegram Bot API).
Setup
terranc/claude-telegram-bot-bridge
Install and configure the Telegram Skill Bot. An agent skill from terranc/claude-telegram-bot-bridge.
Muse
KevPH2026/muse-catch
Muse · Catch — AI 灵感捕手。浏览器插件 + 任意 Agent（Telegram/WhatsApp/Discord…）一键捕获灵感，AI自动提炼，Web Dashboard浏览。分级LLM路由：Agent内置LLM隐私分析 + TokenRouter云端分布式调用。当用户说「灵感」「捕获」「Muse」「Catch」「记下来」「收藏」「稍后读」时自动触发。
Actionize
infranodus/skills
Turn insights, findings, or research into an actionable plan with deadlines and scheduled Telegram reminders.
Muse
KevPH2026/muse-catch
Muse · Catch — AI灵感捕手。浏览器插件+Telegram Bot一键捕获，AI自动提炼，Dashboard浏览+DNA雷达+OPC Market。当用户说「灵感」「捕获」「Muse」「Catch」「记下来」「收藏」时触发。
More from vendelieu/telegram-bot
All 14 skills in this repoAdd Ktnip Ksp Tests
vendelieu/telegram-bot
Adds tests for the ktnip KSP processor. An agent skill from vendelieu/telegram-bot.
Add Ktnip Parameter Strategy
vendelieu/telegram-bot
Adds a new parameter resolution strategy to the ktnip KSP processor.
Add Telegram API Action
vendelieu/telegram-bot
Adds a new Telegram Bot API method (action class and top-level functions).
Add Telegram API Tests
vendelieu/telegram-bot
Writes tests for Telegram Bot API actions. An agent skill from vendelieu/telegram-bot.
Add Wizard Handler
vendelieu/telegram-bot
Configures @WizardHandler annotation for wizard flows. An agent skill from vendelieu/telegram-bot.
Add Wizard Step
vendelieu/telegram-bot
Implements WizardStep for wizard flows. An agent skill from vendelieu/telegram-bot.
Related
Categories
Questions about Add Telegram Update Field
What does Add Telegram Update Field do?
Adds a new field to the Update type and wires it through ProcessedUpdate, UpdateType, ProcessUpdate, KSP (TypeConstants, TypeMapper), and FunctionalDSLUtils. Add Telegram Update Field is an agent skill from vendelieu/telegram-bot. Adds a new field to the Update type and wires it through ProcessedUpdate, UpdateType, ProcessUpdate, KSP (TypeConstants, TypeMapper), and FunctionalDSLUtils.
When should I use Add Telegram Update Field?
Add Telegram Update Field fits situations like: implementing support for a new Telegram update type (e.g; tasks that involve Chatbots and conversational support; tasks that involve Android development.
How do I install Add Telegram Update Field in Claude Code?
Run `npx skills add vendelieu/telegram-bot --skill add-telegram-update-field -a claude-code`. Or copy the skill folder (.cursor/skills/add-telegram-update-field in vendelieu/telegram-bot) into .claude/skills/add-telegram-update-field in your project. Claude Code loads it when a task matches its description.
How do I install Add Telegram Update Field in Codex?
Run `npx skills add vendelieu/telegram-bot --skill add-telegram-update-field -a codex`. Or copy the skill folder (.cursor/skills/add-telegram-update-field in vendelieu/telegram-bot) into .agents/skills/add-telegram-update-field in your project. Codex loads it when a task matches its description.
Can I use Add Telegram Update Field in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add vendelieu/telegram-bot --skill add-telegram-update-field -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/add-telegram-update-field, .gemini/skills/add-telegram-update-field, .github/skills/add-telegram-update-field and .opencode/skills/add-telegram-update-field in your project.
What does Add Telegram Update Field need to run?
SKILL.md names no scripts, command-line tools or credentials: Add Telegram Update Field is instructions for the agent only.
Does Add Telegram Update Field access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Add Telegram Update Field safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Add Telegram Update Field use?
Add Telegram Update Field is published under the Apache-2.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Add Telegram Update Field use?
About 841 tokens (SKILL.md is roughly 3.4k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Add Telegram Update Field?
Skills that share tags, products or a category with Add Telegram Update Field: Telegram (bubbuild/bub, 1.7k stars), Pytdbot (pytdbot/client, 137 stars), Setup (terranc/claude-telegram-bot-bridge, 134 stars) and Muse (KevPH2026/muse-catch, 128 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Add Telegram Update Field?
vendelieu (a GitHub user) maintains it in vendelieu/telegram-bot, which has 249 GitHub stars. The repository holds 14 skills in this directory. The repository was last updated on October 4, 2026.
Source: vendelieu/telegram-bot on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.