Telegram
olasunkanmi-SE/codebuddy
Send Telegram messages, files, and interact with Telegram bots via the telegram-send CLI tool.
Connect Caspian Telegram for OpenCode, enable telegram in caspian.json channels, and tell the user to restart.
Install Caspian Connect Telegram
$ npx skills add TryCaspian/caspian-sdk --skill caspian-connect-telegram -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install TryCaspian/caspian-sdk caspian-connect-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/TryCaspian/caspian-sdk.git skills-src && mkdir -p .claude/skills && cp -r skills-src/packages/opencode/src/skills/caspian-connect-telegram .claude/skills/caspian-connect-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 "caspian-connect-telegram" agent skill from https://github.com/TryCaspian/caspian-sdk/tree/main/packages/opencode/src/skills/caspian-connect-telegram into .claude/skills/caspian-connect-telegram/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "caspian-connect-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/TryCaspian/caspian-sdk/tree/main/packages/opencode/src/skills/caspian-connect-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 TryCaspian/caspian-sdk --skill caspian-connect-telegram -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install TryCaspian/caspian-sdk caspian-connect-telegram --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/TryCaspian/caspian-sdk.git skills-src && mkdir -p .agents/skills && cp -r skills-src/packages/opencode/src/skills/caspian-connect-telegram .agents/skills/caspian-connect-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 "caspian-connect-telegram" agent skill from https://github.com/TryCaspian/caspian-sdk/tree/main/packages/opencode/src/skills/caspian-connect-telegram into .agents/skills/caspian-connect-telegram/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "caspian-connect-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 TryCaspian/caspian-sdk --skill caspian-connect-telegram -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install TryCaspian/caspian-sdk caspian-connect-telegram --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/TryCaspian/caspian-sdk.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/packages/opencode/src/skills/caspian-connect-telegram .cursor/skills/caspian-connect-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 "caspian-connect-telegram" agent skill from https://github.com/TryCaspian/caspian-sdk/tree/main/packages/opencode/src/skills/caspian-connect-telegram into .cursor/skills/caspian-connect-telegram/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "caspian-connect-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/TryCaspian/caspian-sdk.git --path packages/opencode/src/skills/caspian-connect-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 TryCaspian/caspian-sdk --skill caspian-connect-telegram -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install TryCaspian/caspian-sdk caspian-connect-telegram --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/TryCaspian/caspian-sdk.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/packages/opencode/src/skills/caspian-connect-telegram .gemini/skills/caspian-connect-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 "caspian-connect-telegram" agent skill from https://github.com/TryCaspian/caspian-sdk/tree/main/packages/opencode/src/skills/caspian-connect-telegram into .gemini/skills/caspian-connect-telegram/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "caspian-connect-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 TryCaspian/caspian-sdk caspian-connect-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 TryCaspian/caspian-sdk --skill caspian-connect-telegram -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/TryCaspian/caspian-sdk.git skills-src && mkdir -p .github/skills && cp -r skills-src/packages/opencode/src/skills/caspian-connect-telegram .github/skills/caspian-connect-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 "caspian-connect-telegram" agent skill from https://github.com/TryCaspian/caspian-sdk/tree/main/packages/opencode/src/skills/caspian-connect-telegram into .github/skills/caspian-connect-telegram/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "caspian-connect-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 TryCaspian/caspian-sdk --skill caspian-connect-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 TryCaspian/caspian-sdk caspian-connect-telegram --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/TryCaspian/caspian-sdk.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/packages/opencode/src/skills/caspian-connect-telegram .opencode/skills/caspian-connect-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 "caspian-connect-telegram" agent skill from https://github.com/TryCaspian/caspian-sdk/tree/main/packages/opencode/src/skills/caspian-connect-telegram into .opencode/skills/caspian-connect-telegram/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "caspian-connect-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
caspian-connect-telegram- GitHub stars
- 973
- Token cost
- ~446 tokens
- SKILL.md length
- 185 words
- Files
- 1
- Skills in repo
- 8
- Repo updated
- First seen
- Licence
- Apache-2.0
At a glance
Connect Caspian Telegram for OpenCode, enable telegram in caspian.json channels, and tell the user to restart.
- Works in 3 steps: TELEGRAM_BOT_TOKEN in the environment → Project .env → TELEGRAM_BOT_TOKEN=... → ~/.config/opencode/caspian.env →…
- Linking a Telegram bot
- SKILL.md covers When to use, Prerequisites (token) and How
- Needs TELEGRAM_BOT_TOKEN
What it does
Caspian Connect Telegram is an agent skill from TryCaspian/caspian-sdk. Connect Caspian Telegram for OpenCode, enable telegram in caspian.json channels, and tell the user to restart. Use when linking a Telegram bot or running /caspian:connect-telegram.
Its SKILL.md is about 450 tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts. Compatibility notes: opencode
It sits in Productivity & Automation, covering Messaging and chat bots and Chatbots and conversational support. It works with Telegram. The repository describes itself as: Agent communication SDK. The open-source agent communication layer for AI agents — email, WhatsApp, Slack, Discord, Telegram, SMS. Python & TypeScript. The licence is Apache-2.0.
When your agent uses it
- Linking a Telegram bot
- Running /caspian:connect-telegram
Example prompts
- “/caspian-connect-telegram”
Requirements
- A credential in TELEGRAM_BOT_TOKEN
- Compatibility (from SKILL.md): opencode
Workflow steps
3 steps, taken from the first numbered list in SKILL.md.
- TELEGRAM_BOT_TOKEN in the environment
- Project .env → TELEGRAM_BOT_TOKEN=...
- ~/.config/opencode/caspian.env → TELEGRAM_BOT_TOKEN=...
What it can do on your machine
Read from SKILL.md and the folder at commit 718a96d. 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.
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 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.
Compatibility
opencode
From compatibility in the SKILL.md frontmatter.
Context cost
Caspian Connect Telegram loads about 446 tokens when it runs. Until then it costs about 51 tokens; SKILL.md has 185 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: notes
The automated check noted patterns worth knowing about, such as sudo or a known installer.
- NoteMentions a .env fileSKILL.md:30
2. Project `.env` → `TELEGRAM_BOT_TOKEN=...` - NoteMentions a .env fileSKILL.md:41
er, write `TELEGRAM_BOT_TOKEN=...` into `.env` or `caspian.env`, then
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 TryCaspian/caspian-sdk at commit 718a96d, republished under its Apache-2.0 licence (© TryCaspian). 185 words, ~446 tokens.
Download SKILL.mdSave it as
.claude/skills/caspian-connect-telegram/SKILL.md (or your agent's skills folder).- name
- caspian-connect-telegram
- description
- Connect Caspian Telegram for OpenCode, enable telegram in caspian.json channels, and tell the user to restart. Use when linking a Telegram bot or running /caspian:connect-telegram.
- compatibility
- opencode
- license
- Apache-2.0
- metadata.alias
- caspian:ConnectTelegram
- metadata.channel
- caspian
Caspian connect Telegram
Connect a Telegram bot to Caspian and enable telegram in the plugin admit
list (channels in ~/.config/opencode/caspian.json). Without telegram in
channels, Telegram events are rejected at admit (blast-radius wall).
When to use
- User asks to connect Telegram / BotFather / Telegram bot
- User runs
/caspian:connect-telegramor/caspian-connect-telegram
Prerequisites (token)
Bot token must exist in one of (prefer file over chat):
TELEGRAM_BOT_TOKENin the environment- Project
.env→TELEGRAM_BOT_TOKEN=... ~/.config/opencode/caspian.env→TELEGRAM_BOT_TOKEN=...
Do not store the token in caspian.json. Prefer not pasting the token into chat.
How
Call
caspian_connectionsto see if Telegram is already linked and whethertelegramis already in plugin channels.Call
caspian_connect_telegram.If the tool asks for a token, instruct the user to create a bot with @BotFather, write
TELEGRAM_BOT_TOKEN=...into.envorcaspian.env, then re-run the command. Do not invent a token.On success, present connection id / channels. If RESTART REQUIRED, say:
Restart OpenCode (quit and relaunch) so admit loads
"channels": ["email", "telegram"](or your updated list). Until then, Telegram messages are still rejected.After restart, Telegram inbound should flow into OpenCode like email.
© TryCaspian, 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 packages/opencode/src/skills/caspian-connect-telegram of TryCaspian/caspian-sdk.
Open the folder on GitHubat commit 718a96d
Compare with similar skills
Caspian Connect 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 |
|---|---|---|---|---|---|---|
| Caspian Connect Telegram this skillTryCaspian/caspian-sdk | 973 | — | ~446 | Automated safety check: Notes | Apache-2.0 | |
| Telegramolasunkanmi-SE/codebuddy | 141 | — | ~817 | Automated safety check: Pass | MIT | |
| Telegram BotOpenClaudia/openclaudia-skills | 713 | — | ~6k | Automated safety check: Notes | MIT | |
| Telegram Channel Setupanthropics/claude-plugins-official | 38k | 1 repos | ~1.1k | Automated safety check: Notes | Apache-2.0 | |
| Chat SDKdatabuddy-analytics/Databuddy | 1.2k | — | ~2.6k | Automated safety check: Pass | AGPL-3.0 | |
| Telegrambubbuild/bub | 1.7k | — | ~2.2k | Automated safety check: Pass | Apache-2.0 |
Similar skills
Telegram Bot
OpenClaudia/openclaudia-skills
Send messages, images, and marketing content to Telegram channels and groups via Bot API.
- Official
Telegram Channel Setup
anthropics/claude-plugins-official
Saves a Telegram bot token for the Telegram channel plugin and reviews who may message the bot, steering the policy toward a fixed allowlist.
Chat SDK
databuddy-analytics/Databuddy
Build multi-platform chat bots with Chat SDK (chat npm package).
Telegram
bubbuild/bub
Telegram Bot skill for sending and editing Telegram messages via Bot API.
Pytdbot
pytdbot/client
Write Telegram bots and userbots with Pytdbot (async TDLib wrapper with high-level helpers; not the Telegram Bot API).
More from TryCaspian/caspian-sdk
All 8 skills in this repoCaspian Toast Test
TryCaspian/caspian-sdk
Dummy skill to test OpenCode TUI toast UI (and optional system notification) via caspiantesttoast.
Caspian Connect Email
TryCaspian/caspian-sdk
Connect Caspian email for OpenCode: ensure credentials (sandbox or dashboard API key), write caspian.env, connect inbox, enable email in caspian.json.
Taste
TryCaspian/caspian-sdk
Domain-first store/port design for any codebase: product-shaped APIs, swappable backends, schema at boundaries, one vocabulary catalog (derive don’t re-author), no infrastructure names on the domain…
Caspian Connect Discord
TryCaspian/caspian-sdk
Connect Caspian Discord for OpenCode (install OAuth or BYO bot token), enable discord in caspian.json channels, and tell the user to restart.
Caspian Discord
TryCaspian/caspian-sdk
Post a Discord message via Caspian to a channel snowflake id.
Caspian Inbox
TryCaspian/caspian-sdk
Caspian Inbox (caspian:Inbox) — list agent email and other configured channel conversations/messages.
Related
Works with
Categories
Questions about Caspian Connect Telegram
What does Caspian Connect Telegram do?
Connect Caspian Telegram for OpenCode, enable telegram in caspian.json channels, and tell the user to restart. Caspian Connect Telegram is an agent skill from TryCaspian/caspian-sdk.json channels, and tell the user to restart.
When should I use Caspian Connect Telegram?
Caspian Connect Telegram fits situations like: linking a Telegram bot; running /caspian:connect-telegram.
How do I install Caspian Connect Telegram in Claude Code?
Run `npx skills add TryCaspian/caspian-sdk --skill caspian-connect-telegram -a claude-code`. Or copy the skill folder (packages/opencode/src/skills/caspian-connect-telegram in TryCaspian/caspian-sdk) into .claude/skills/caspian-connect-telegram in your project. Claude Code loads it when a task matches its description.
How do I install Caspian Connect Telegram in Codex?
Run `npx skills add TryCaspian/caspian-sdk --skill caspian-connect-telegram -a codex`. Or copy the skill folder (packages/opencode/src/skills/caspian-connect-telegram in TryCaspian/caspian-sdk) into .agents/skills/caspian-connect-telegram in your project. Codex loads it when a task matches its description.
Can I use Caspian Connect 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 TryCaspian/caspian-sdk --skill caspian-connect-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/caspian-connect-telegram, .gemini/skills/caspian-connect-telegram, .github/skills/caspian-connect-telegram and .opencode/skills/caspian-connect-telegram in your project.
What does Caspian Connect Telegram need to run?
Going by SKILL.md and its folder, Caspian Connect Telegram needs credentials named TELEGRAM_BOT_TOKEN. Our summary lists: A credential in TELEGRAM_BOT_TOKEN. Compatibility (from SKILL.md): opencode.
Does Caspian Connect Telegram 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 Caspian Connect Telegram safe to install?
Our automated static check of SKILL.md found notes only (mentions a .env file), nothing it rates as a warning. It is not a guarantee. Review the folder before installing.
What licence does Caspian Connect Telegram use?
Caspian Connect Telegram is published under the Apache-2.0 licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Caspian Connect Telegram use?
About 446 tokens (SKILL.md is roughly 1.8k 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 Caspian Connect Telegram?
Skills that share tags, products or a category with Caspian Connect Telegram: Telegram (olasunkanmi-SE/codebuddy, 141 stars), Telegram Bot (OpenClaudia/openclaudia-skills, 713 stars), Telegram Channel Setup (anthropics/claude-plugins-official, 38k stars) and Chat SDK (databuddy-analytics/Databuddy, 1.2k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Caspian Connect Telegram?
TryCaspian (a GitHub organization) maintains it in TryCaspian/caspian-sdk, which has 973 GitHub stars. The repository holds 8 skills in this directory. The repository was last updated on August 25, 2026.
Source: TryCaspian/caspian-sdk on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.