Dependency Watch
telegramdesktop/tdesktop
Audit Telegram Desktop dependencies on freshly fetched origin/dev for releases and security fixes, including upstream lag and backport candidates in patched forks.
Send and receive messages via the Telegram Bot API using curl
Install Telegram
$ npx skills add laude-institute/headlong --skill telegram -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install laude-institute/headlong telegram --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/laude-institute/headlong.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/telegram .claude/skills/telegram && 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 "telegram" agent skill from https://github.com/laude-institute/headlong/tree/main/skills/telegram into .claude/skills/telegram/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "telegram", 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/laude-institute/headlong/tree/main/skills/telegramType 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 laude-institute/headlong --skill telegram -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install laude-institute/headlong telegram --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/laude-institute/headlong.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/telegram .agents/skills/telegram && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "telegram" agent skill from https://github.com/laude-institute/headlong/tree/main/skills/telegram into .agents/skills/telegram/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "telegram", 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 laude-institute/headlong --skill telegram -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install laude-institute/headlong telegram --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/laude-institute/headlong.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/telegram .cursor/skills/telegram && 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 "telegram" agent skill from https://github.com/laude-institute/headlong/tree/main/skills/telegram into .cursor/skills/telegram/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "telegram", 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/laude-institute/headlong.git --path skills/telegram--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 laude-institute/headlong --skill telegram -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install laude-institute/headlong telegram --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/laude-institute/headlong.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/telegram .gemini/skills/telegram && 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 "telegram" agent skill from https://github.com/laude-institute/headlong/tree/main/skills/telegram into .gemini/skills/telegram/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "telegram", 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 laude-institute/headlong telegramInstalls 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 laude-institute/headlong --skill telegram -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/laude-institute/headlong.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/telegram .github/skills/telegram && 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 "telegram" agent skill from https://github.com/laude-institute/headlong/tree/main/skills/telegram into .github/skills/telegram/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "telegram", 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 laude-institute/headlong --skill telegram -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install laude-institute/headlong telegram --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/laude-institute/headlong.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/telegram .opencode/skills/telegram && 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 "telegram" agent skill from https://github.com/laude-institute/headlong/tree/main/skills/telegram into .opencode/skills/telegram/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "telegram", 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
telegram- GitHub stars
- 1.2k
- Token cost
- ~623 tokens
- SKILL.md length
- 131 words
- Files
- 1
- Skills in repo
- 10
- Repo updated
- First seen
- Licence
- Apache-2.0
At a glance
Send and receive messages via the Telegram Bot API using curl
- Productivity & Automation work in your project
- Calls curl and jq; reaches api.telegram.org; needs TELEGRAM_BOT_TOKEN
What it does
Telegram is an agent skill from laude-institute/headlong. Send and receive messages via the Telegram Bot API using curl
Its SKILL.md is about 620 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. It works with Telegram. The repository describes itself as: An open source agent microharness featuring persistent agency and recursive LLMs. Of bash, by bash, for bash; it's shells all the way down. The licence is Apache-2.0.
When your agent uses it
- Productivity & Automation work in your project
Example prompts
- “/telegram”
Requirements
- A credential in TELEGRAM_BOT_TOKEN
What it can do on your machine
Read from SKILL.md and the folder at commit c43e597. 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
Shell commands in SKILL.md call:
curljq
From the folder's file list and the shell code blocks in SKILL.md.
Network
Hosts in commands or code, which the agent is likely to contact:
api.telegram.org
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names these keys or tokens, usually read from environment variables:
TELEGRAM_BOT_TOKEN
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Telegram loads about 623 tokens when it runs. Until then it costs about 18 tokens; SKILL.md has 131 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 laude-institute/headlong at commit c43e597, republished under its Apache-2.0 licence (© laude-institute). 131 words, ~623 tokens.
Download SKILL.mdSave it as
.claude/skills/telegram/SKILL.md (or your agent's skills folder).- name
- telegram
- description
- Send and receive messages via the Telegram Bot API using curl
telegram
Instructions
Use this skill to interact with Telegram via the Bot API. All operations use
curl against https://api.telegram.org/bot<TOKEN>/....
Prerequisites
The environment variable TELEGRAM_BOT_TOKEN must be set to a valid Telegram
Bot API token (obtained from @BotFather). The variable TELEGRAM_CHAT_ID should
be set to the target chat/group/channel ID for sending messages.
Sending a message
curl -s "https://api.telegram.org/bot${TELEGRAM_BOT_TOKEN}/sendMessage" \
-d chat_id="${TELEGRAM_CHAT_ID}" \
-d text="Hello from shellm" \
-d parse_mode=MarkdownSending a file/document
curl -s "https://api.telegram.org/bot${TELEGRAM_BOT_TOKEN}/sendDocument" \
-F chat_id="${TELEGRAM_CHAT_ID}" \
-F document=@/path/to/file.txtGetting updates (receiving messages)
Poll for new messages using getUpdates. Use offset to acknowledge
previously seen updates and only receive new ones.
# Get latest updates
curl -s "https://api.telegram.org/bot${TELEGRAM_BOT_TOKEN}/getUpdates" \
-d limit=10 \
-d timeout=0
# Acknowledge up to update_id 12345 and get only newer updates
curl -s "https://api.telegram.org/bot${TELEGRAM_BOT_TOKEN}/getUpdates" \
-d offset=12346 \
-d limit=10Parse the JSON response with jq:
curl -s "https://api.telegram.org/bot${TELEGRAM_BOT_TOKEN}/getUpdates" \
| jq -r '.result[] | "\(.update_id) \(.message.from.username): \(.message.text)"'Replying to a specific message
curl -s "https://api.telegram.org/bot${TELEGRAM_BOT_TOKEN}/sendMessage" \
-d chat_id="${TELEGRAM_CHAT_ID}" \
-d text="Reply text" \
-d reply_to_message_id=MESSAGE_IDGetting chat info
curl -s "https://api.telegram.org/bot${TELEGRAM_BOT_TOKEN}/getChat" \
-d chat_id="${TELEGRAM_CHAT_ID}" | jq .Error handling
All Telegram API responses return JSON with an ok field. Check it:
response=$(curl -s "https://api.telegram.org/bot${TELEGRAM_BOT_TOKEN}/sendMessage" \
-d chat_id="${TELEGRAM_CHAT_ID}" \
-d text="test")
if [ "$(echo "$response" | jq -r '.ok')" != "true" ]; then
echo "Telegram API error: $(echo "$response" | jq -r '.description')" >&2
fiRate limits
Telegram limits bots to ~30 messages/second to different chats, and ~20 messages/minute to the same chat. Add short delays between batch sends.
© laude-institute, 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 skills/telegram of laude-institute/headlong.
Open the folder on GitHubat commit c43e597
Compare with similar skills
Telegram 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 |
|---|---|---|---|---|---|---|
| Telegram this skilllaude-institute/headlong | 1.2k | — | ~623 | Automated safety check: Pass | Apache-2.0 | |
| Dependency Watchtelegramdesktop/tdesktop | 33k | 1 repos | ~2.2k | Automated safety check: Pass | GPL-3.0 | |
| Perform Tasktelegramdesktop/tdesktop | 33k | 2 repos | ~3k | Automated safety check: Pass | GPL-3.0 | |
| Continuetelegramdesktop/tdesktop | 33k | 2 repos | ~9.4k | Automated safety check: Pass | GPL-3.0 | |
| Process Inboxtelegramdesktop/tdesktop | 33k | 1 repos | ~5.4k | Automated safety check: Pass | GPL-3.0 | |
| Process InboxTDesktop-x64/tdesktop | 3k | — | ~4.3k | Automated safety check: Pass | GPL-3.0 |
Similar skills
Perform Task
telegramdesktop/tdesktop
Resolve, start or resume, implement, review, test, and publish exactly one existing ai-tdesktop task by short slug or full dated id, including rare blocked retries and split-required results.
Continue
telegramdesktop/tdesktop
Continue autonomous Telegram Desktop development from the shared ai-tdesktop repository.
Process Inbox
telegramdesktop/tdesktop
Process the local ignored ai-tdesktop inbox into durable, independently testable Telegram Desktop task records while task execution worktrees remain active.
Process Inbox
TDesktop-x64/tdesktop
Process the local ignored ai-tdesktop inbox into durable, independently testable Telegram Desktop task records while task execution worktrees remain active.
Telegram
bubbuild/bub
Telegram Bot skill for sending and editing Telegram messages via Bot API.
More from laude-institute/headlong
All 10 skills in this repoShellm Architecture Reference
laude-institute/headlong
Explains how shellm's bash-based recursive LLM shell fits together - its core engine, identity system, memory, skills and trajectory log.
ShellLM Skill Author
laude-institute/headlong
Scaffolds new ShellLM skills with the right frontmatter, directory layout and agent-facing writing style, so an agent can extend its own capabilities.
Web Research With curl
laude-institute/headlong
Looks things up online from the shell with curl: fetching pages, searching DuckDuckGo's HTML endpoint, stripping tags for readable text and pulling JSON APIs.
Google Workspace CLI
laude-institute/headlong
Drives Google Drive, Gmail, Calendar, Sheets, Docs and Chat from the shell with the gws CLI, including its sign-in, flags, helper commands and safety rules.
Obsidian
laude-institute/headlong
Read, write, search, and manage notes in an Obsidian vault. An agent skill from laude-institute/headlong.
Slack
laude-institute/headlong
Talk with people on Slack — recognize slack- senders and reach them via chat reply
Related
Works with
Categories
Questions about Telegram
What does Telegram do?
Send and receive messages via the Telegram Bot API using curl. Telegram is an agent skill from laude-institute/headlong.
When should I use Telegram?
Telegram fits situations like: productivity & Automation work in your project.
How do I install Telegram in Claude Code?
Run `npx skills add laude-institute/headlong --skill telegram -a claude-code`. Or copy the skill folder (skills/telegram in laude-institute/headlong) into .claude/skills/telegram in your project. Claude Code loads it when a task matches its description.
How do I install Telegram in Codex?
Run `npx skills add laude-institute/headlong --skill telegram -a codex`. Or copy the skill folder (skills/telegram in laude-institute/headlong) into .agents/skills/telegram in your project. Codex loads it when a task matches its description.
Can I use Telegram 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 laude-institute/headlong --skill telegram -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/telegram, .gemini/skills/telegram, .github/skills/telegram and .opencode/skills/telegram in your project.
What does Telegram need to run?
Going by SKILL.md and its folder, Telegram needs the command-line tools its instructions call (curl and jq) and credentials named TELEGRAM_BOT_TOKEN. Our summary lists: A credential in TELEGRAM_BOT_TOKEN.
Does Telegram access the network?
SKILL.md names 1 domain. In commands or code: api.telegram.org; the agent is likely to contact it when it follows the instructions. This is read from the text; nothing was executed.
Is Telegram 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 Telegram use?
Telegram 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 Telegram use?
About 623 tokens (SKILL.md is roughly 2.5k 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 Telegram?
Skills that share tags, products or a category with Telegram: Dependency Watch (telegramdesktop/tdesktop, 33k stars), Perform Task (telegramdesktop/tdesktop, 33k stars), Continue (telegramdesktop/tdesktop, 33k stars) and Process Inbox (telegramdesktop/tdesktop, 33k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Telegram?
laude-institute (a GitHub organization) maintains it in laude-institute/headlong, which has 1,216 GitHub stars. The repository holds 10 skills in this directory. The repository was last updated on October 9, 2026.
Source: laude-institute/headlong on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.