Browser4 Dev
platonai/Browser4
Develop features inside the Browser4 repository itself: add CLI commands, agent tool domains, REST endpoints, tests, and skills; analyze impact, plan dev tasks, check CDP pitfalls, and verify builds.
Adds a new Telegram Bot API method (action class and top-level functions).
$ npx skills add vendelieu/telegram-bot --skill add-telegram-api-action -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install vendelieu/telegram-bot add-telegram-api-action --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-api-action .claude/skills/add-telegram-api-action && 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-api-action" agent skill from https://github.com/vendelieu/telegram-bot/tree/master/.cursor/skills/add-telegram-api-action into .claude/skills/add-telegram-api-action/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "add-telegram-api-action", 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-api-actionType 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-api-action -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install vendelieu/telegram-bot add-telegram-api-action --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-api-action .agents/skills/add-telegram-api-action && 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-api-action" agent skill from https://github.com/vendelieu/telegram-bot/tree/master/.cursor/skills/add-telegram-api-action into .agents/skills/add-telegram-api-action/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "add-telegram-api-action", 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-api-action -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install vendelieu/telegram-bot add-telegram-api-action --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-api-action .cursor/skills/add-telegram-api-action && 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-api-action" agent skill from https://github.com/vendelieu/telegram-bot/tree/master/.cursor/skills/add-telegram-api-action into .cursor/skills/add-telegram-api-action/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "add-telegram-api-action", 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-api-action--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-api-action -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install vendelieu/telegram-bot add-telegram-api-action --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-api-action .gemini/skills/add-telegram-api-action && 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-api-action" agent skill from https://github.com/vendelieu/telegram-bot/tree/master/.cursor/skills/add-telegram-api-action into .gemini/skills/add-telegram-api-action/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "add-telegram-api-action", 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-api-actionInstalls 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-api-action -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-api-action .github/skills/add-telegram-api-action && 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-api-action" agent skill from https://github.com/vendelieu/telegram-bot/tree/master/.cursor/skills/add-telegram-api-action into .github/skills/add-telegram-api-action/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "add-telegram-api-action", 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-api-action -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-api-action --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-api-action .opencode/skills/add-telegram-api-action && 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-api-action" agent skill from https://github.com/vendelieu/telegram-bot/tree/master/.cursor/skills/add-telegram-api-action into .opencode/skills/add-telegram-api-action/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "add-telegram-api-action", 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.
add-telegram-api-actionAdds a new Telegram Bot API method (action class and top-level functions).
Add Telegram API Action is an agent skill from vendelieu/telegram-bot. Adds a new Telegram Bot API method (action class and top-level functions). Use when implementing a new Telegram API endpoint, adding support for a specific method (e.g. sendVideoNote, getChatMemberCount), or creating a new action for the telegram-bot library.
Its SKILL.md is about 970 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, REST APIs 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.
6 steps, taken from the step headings in SKILL.md.
Read from SKILL.md and the folder at commit 1dbfd00. It shows what the files ask for, not the result of running them.
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.
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.
Links to these hosts (documentation or services it may open):
core.telegram.orgFrom URLs in SKILL.md, links to its own repository left out.
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Add Telegram API Action loads about 974 tokens when it runs. Until then it costs about 71 tokens; SKILL.md has 307 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.
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.
The full file from vendelieu/telegram-bot at commit 1dbfd00, republished under its Apache-2.0 licence (© vendelieu). 307 words, ~974 tokens.
.claude/skills/add-telegram-api-action/SKILL.md (or your agent's skills folder).Action (or MediaAction for media)SimpleAction (e.g. getMe, getUpdates, setWebhook)Consult core.telegram.org/bots/api for:
telegram-bot/src/commonMain/kotlin/eu/vendeli/tgbot/types/options/data class implementing Options + mixins (OptionsCommon, OptionsParseMode, MediaSpoiler, ForumProps, etc.)var prop: Type? = null@Serializableinterface MyProp : Options { var myParam: Type? }) only when the param is shared; single-use params stay in the data class.Place in appropriate package under telegram-bot/src/commonMain/kotlin/eu/vendeli/tgbot/api/:
media/ - photo, video, document, etc.message/ - sendMessage, editMessage, etc.answer/ - answerCallbackQuery, answerInlineQuerybotactions/ - getMe, setWebhook, etc.chat/ - getChat, banChatMember, etc.Required:
@TgAPI on class@TgAPI.Name("methodName") on method when Kotlin name differs from APIoverride val method, returnType, options (if OptionsFeature)Features (add as needed):
OptionsFeature - optional params via options { }MarkupFeature - reply_markupCaptionFeature - caption, caption_entities (media)EntitiesFeature - entities (text)BusinessActionExt - chat-based actionsInlineActionExt - inline message actionsParameter handling:
parameters["key"] = value.toJsonElement()value.encodeWith(MyType.serializer())list.encodeWith(ListSerializer(ItemType.serializer()))value.encodeWith(DynamicLookupSerializer)value.encodeWith(EnumType.serializer())handleImplicitFile(file, "paramName") in inithandleImplicitFile(options::thumbnail) in override val beforeReqbeforeReq, then encodeWith(Serializer)Use encodeWith for any @Serializable class, list, or polymorphic type; use toJsonElement() only for primitives.
@TgAPI on eachinline fun actionName(...) = ActionClass(...)ImplicitFile, InputFile, ByteArray, () -> String as in existing media actionssendActionName alias./gradlew formatKotlin
./gradlew prepareReleasebeforeReq for handleImplicitFile(options::thumbnail)© 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
Just SKILL.md in .cursor/skills/add-telegram-api-action of vendelieu/telegram-bot.
Open the folder on GitHubat commit 1dbfd00
Add Telegram API Action 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 API Action this skillvendelieu/telegram-bot | 249 | — | ~974 | Automated safety check: Pass | Apache-2.0 | |
| Browser4 Devplatonai/Browser4 | 1.2k | — | ~2.2k | Automated safety check: Pass | Apache-2.0 | |
| Connekt Script WriterAmplicode/spring-skills | 126 | — | ~4.7k | Automated safety check: Pass | None | |
| 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 |
platonai/Browser4
Develop features inside the Browser4 repository itself: add CLI commands, agent tool domains, REST endpoints, tests, and skills; analyze impact, plan dev tasks, check CDP pitfalls, and verify builds.
Amplicode/spring-skills
Write .connekt.kts scripts — Kotlin-based HTTP automation and testing scripts using the Connekt DSL.
bubbuild/bub
Telegram Bot skill for sending and editing Telegram messages via Bot API.
pytdbot/client
Write Telegram bots and userbots with Pytdbot (async TDLib wrapper with high-level helpers; not the Telegram Bot API).
terranc/claude-telegram-bot-bridge
Install and configure the Telegram Skill Bot. An agent skill from terranc/claude-telegram-bot-bridge.
KevPH2026/muse-catch
Muse · Catch — AI 灵感捕手。浏览器插件 + 任意 Agent(Telegram/WhatsApp/Discord…)一键捕获灵感,AI自动提炼,Web Dashboard浏览。分级LLM路由:Agent内置LLM隐私分析 + TokenRouter云端分布式调用。当用户说「灵感」「捕获」「Muse」「Catch」「记下来」「收藏」「稍后读」时自动触发。
vendelieu/telegram-bot
Adds tests for the ktnip KSP processor. An agent skill from vendelieu/telegram-bot.
vendelieu/telegram-bot
Adds a new parameter resolution strategy to the ktnip KSP processor.
vendelieu/telegram-bot
Writes tests for Telegram Bot API actions. An agent skill from vendelieu/telegram-bot.
vendelieu/telegram-bot
Adds a new field to the Update type and wires it through ProcessedUpdate, UpdateType, ProcessUpdate, KSP (TypeConstants, TypeMapper), and FunctionalDSLUtils.
vendelieu/telegram-bot
Configures @WizardHandler annotation for wizard flows. An agent skill from vendelieu/telegram-bot.
vendelieu/telegram-bot
Implements WizardStep for wizard flows. An agent skill from vendelieu/telegram-bot.
Categories
Adds a new Telegram Bot API method (action class and top-level functions). Add Telegram API Action is an agent skill from vendelieu/telegram-bot. Adds a new Telegram Bot API method (action class and top-level functions).
Add Telegram API Action fits situations like: implementing a new Telegram API endpoint; adding support for a specific method (e.g.
Run `npx skills add vendelieu/telegram-bot --skill add-telegram-api-action -a claude-code`. Or copy the skill folder (.cursor/skills/add-telegram-api-action in vendelieu/telegram-bot) into .claude/skills/add-telegram-api-action in your project. Claude Code loads it when a task matches its description.
Run `npx skills add vendelieu/telegram-bot --skill add-telegram-api-action -a codex`. Or copy the skill folder (.cursor/skills/add-telegram-api-action in vendelieu/telegram-bot) into .agents/skills/add-telegram-api-action in your project. Codex loads it when a task matches its description.
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-api-action -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-api-action, .gemini/skills/add-telegram-api-action, .github/skills/add-telegram-api-action and .opencode/skills/add-telegram-api-action in your project.
SKILL.md names no scripts, command-line tools or credentials: Add Telegram API Action is instructions for the agent only.
SKILL.md names 1 domain. As links in the text: core.telegram.org. This is read from the text; nothing was executed.
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.
Add Telegram API Action 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.
About 974 tokens (SKILL.md is roughly 3.9k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
Skills that share tags, products or a category with Add Telegram API Action: Browser4 Dev (platonai/Browser4, 1.2k stars), Connekt Script Writer (Amplicode/spring-skills, 126 stars), Telegram (bubbuild/bub, 1.7k stars) and Pytdbot (pytdbot/client, 137 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
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.