Claude To Im
op7418/Claude-to-IM-skill
Bridge THIS Claude Code or Codex session to Telegram, Discord, Feishu/Lark, QQ, or WeChat so the user can chat with Claude from their phone.
Hands the current Claude Code session's context to a Telegram bot session by writing a short summary to the bot's memory file and sending it as a Telegram message.
Install Telegram Context Transfer
$ npx skills add k1p1l0/claude-telegram-supercharged --skill context -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install k1p1l0/claude-telegram-supercharged context --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/k1p1l0/claude-telegram-supercharged.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/context .claude/skills/context && 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 "context" agent skill from https://github.com/k1p1l0/claude-telegram-supercharged/tree/master/skills/context into .claude/skills/context/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "context", 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/k1p1l0/claude-telegram-supercharged/tree/master/skills/contextType 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 k1p1l0/claude-telegram-supercharged --skill context -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install k1p1l0/claude-telegram-supercharged context --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/k1p1l0/claude-telegram-supercharged.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/context .agents/skills/context && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "context" agent skill from https://github.com/k1p1l0/claude-telegram-supercharged/tree/master/skills/context into .agents/skills/context/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "context", 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 k1p1l0/claude-telegram-supercharged --skill context -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install k1p1l0/claude-telegram-supercharged context --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/k1p1l0/claude-telegram-supercharged.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/context .cursor/skills/context && 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 "context" agent skill from https://github.com/k1p1l0/claude-telegram-supercharged/tree/master/skills/context into .cursor/skills/context/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "context", 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/k1p1l0/claude-telegram-supercharged.git --path skills/context--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 k1p1l0/claude-telegram-supercharged --skill context -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install k1p1l0/claude-telegram-supercharged context --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/k1p1l0/claude-telegram-supercharged.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/context .gemini/skills/context && 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 "context" agent skill from https://github.com/k1p1l0/claude-telegram-supercharged/tree/master/skills/context into .gemini/skills/context/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "context", 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 k1p1l0/claude-telegram-supercharged contextInstalls 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 k1p1l0/claude-telegram-supercharged --skill context -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/k1p1l0/claude-telegram-supercharged.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/context .github/skills/context && 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 "context" agent skill from https://github.com/k1p1l0/claude-telegram-supercharged/tree/master/skills/context into .github/skills/context/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "context", 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 k1p1l0/claude-telegram-supercharged --skill context -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install k1p1l0/claude-telegram-supercharged context --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/k1p1l0/claude-telegram-supercharged.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/context .opencode/skills/context && 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 "context" agent skill from https://github.com/k1p1l0/claude-telegram-supercharged/tree/master/skills/context into .opencode/skills/context/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "context", 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
context- GitHub stars
- 132
- Token cost
- ~764 tokens
- SKILL.md length
- 244 words
- Files
- 1
- Skills in repo
- 5
- Repo updated
- First seen
- Licence
- Apache-2.0
At a glance
Hands the current Claude Code session's context to a Telegram bot session by writing a short summary to the bot's memory file and sending it as a Telegram message.
- Works in 4 steps: Gather context → Write to bot memory → Send as Telegram message → …
- Continuing a terminal Claude Code task from the Telegram bot
- SKILL.md covers Process, Context Format Template and Important Notes
- Calls curl; reaches api.telegram.org; needs TELEGRAM_BOT_TOKEN and BOT_TOKEN
What it does
The skill summarizes the conversation so far into a structured handoff covering what you were working on, key decisions, current state, files changed and action items for the bot, kept under 2000 characters because the bot has limited context. It asks what you want to transfer rather than dumping everything: saying teleport everything summarizes the whole conversation, while teleport this sends only the latest topic.
The summary is appended, never overwritten, to the bot's memory.md under ~/.claude/channels/telegram/data with a timestamp, so it survives restarts. It is also sent as a direct Telegram message through the bot, using the bot token read from the telegram .env file or the environment, with special Markdown characters escaped. The skill then confirms to you that both the memory write and the message happened.
When your agent uses it
- Continuing a terminal Claude Code task from the Telegram bot
- Sending the current task's state and next steps to your phone
- Persisting a session summary into the bot's memory
Example prompts
- “Teleport this to Telegram so the bot can keep going while I'm away.”
- “Send the context of the migration work to the Telegram bot.”
- “Transfer context to Telegram, but only the part about the failing deploy.”
Requirements
- A configured Telegram bot with TELEGRAM_BOT_TOKEN set
- curl
Workflow steps
4 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 688e8fc. 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:
curl
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_TOKENBOT_TOKEN
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Telegram Context Transfer loads about 764 tokens when it runs. Until then it costs about 68 tokens; SKILL.md has 244 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:46
T_TOKEN "$HOME/.claude/channels/telegram/.env" 2>/dev/null | cut -d= -f2 | tr -d '"' | tr -d "'") - NoteMentions a .env fileSKILL.md:48
# If not in .env, check environment - NoteMentions a .env fileSKILL.md:100
token is in `~/.claude/channels/telegram/.env` as `TELEGRAM_BOT_TOKEN`
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 k1p1l0/claude-telegram-supercharged at commit 688e8fc, republished under its Apache-2.0 licence (© k1p1l0). 244 words, ~764 tokens.
Download SKILL.mdSave it as
.claude/skills/context/SKILL.md (or your agent's skills folder).- name
- context
- description
- Transfer context from the current Claude Code terminal session to the Telegram bot session. Use when the user says "send this to telegram", "transfer context", "telegram:context", "teleport to telegram", or wants the Telegram bot to continue work from this session.
Context Transfer to Telegram Bot
Transfer the current conversation context to the Telegram bot session so it can continue the work.
Process
Step 1: Gather context
Summarize the current conversation into a structured context handoff. Include:
- What we were working on — the main task/topic
- Key decisions made — important choices, approaches taken
- Current state — what's done, what's pending
- Files changed — any relevant file paths
- Action items — what the Telegram bot should do next (if any)
Keep it concise — under 2000 characters. The bot has limited context.
Step 2: Write to bot memory
Append the context to the bot's memory file so it persists across restarts:
MEMORY_FILE="$HOME/.claude/channels/telegram/data/memory.md"Append a new section with timestamp:
## YYYY-MM-DD HH:MM — Context Transfer
**Chat 305120844**: [summary here]IMPORTANT: Do not overwrite the file — APPEND to it. Read existing content first, then write old + new.
Step 3: Send as Telegram message
Send the context as a direct message to the user's Telegram chat so the bot sees it immediately in the current session:
BOT_TOKEN=$(grep TELEGRAM_BOT_TOKEN "$HOME/.claude/channels/telegram/.env" 2>/dev/null | cut -d= -f2 | tr -d '"' | tr -d "'")
# If not in .env, check environment
if [ -z "$BOT_TOKEN" ]; then
BOT_TOKEN="$TELEGRAM_BOT_TOKEN"
fi
CHAT_ID="305120844"
curl -s -X POST "https://api.telegram.org/bot${BOT_TOKEN}/sendMessage" \
-H "Content-Type: application/json" \
-d "{
\"chat_id\": \"${CHAT_ID}\",
\"text\": \"📋 *Context transfer from CLI session*\n\n${CONTEXT_TEXT}\",
\"parse_mode\": \"Markdown\"
}"Step 4: Confirm
Tell the user:
Context transferred to Telegram bot:
✓ Written to memory (persists across restarts)
✓ Sent as message (bot sees it now)
Switch to Telegram and continue the conversation there.Context Format Template
Use this format for the transferred context:
📋 CONTEXT TRANSFER FROM CLI
🔧 Working on: [main task]
📁 Project: [project name/path]
Key context:
- [point 1]
- [point 2]
- [point 3]
Current state: [what's done / what's pending]
Next steps: [what to do next, if any]Important Notes
- Always ask the user what specific context they want to transfer — don't dump everything
- Keep it under 2000 chars (Telegram message limit considerations)
- Escape special Markdown characters in the curl message
- The bot token is in
~/.claude/channels/telegram/.envasTELEGRAM_BOT_TOKEN - The user's chat_id is
305120844 - If the user says "teleport everything" — summarize the full conversation
- If the user says "teleport this" — only transfer the most recent topic
© k1p1l0, 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/context of k1p1l0/claude-telegram-supercharged.
Open the folder on GitHubat commit 688e8fc
Compare with similar skills
Telegram Context Transfer 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 Context Transfer this skillk1p1l0/claude-telegram-supercharged | 132 | — | ~764 | Automated safety check: Notes | Apache-2.0 | |
| Claude To Imop7418/Claude-to-IM-skill | 2.9k | — | ~3.4k | Automated safety check: Notes | MIT | |
| Traul Message Searchdandaka/traul | 113 | — | ~3.9k | Automated safety check: Notes | AGPL-3.0 | |
| Conversation Historydashhuang/openclaw-chat-history-import | 144 | — | ~912 | Automated safety check: Pass | MIT | |
| Tlivey49/tlive | 215 | — | ~1.7k | Automated safety check: Notes | MIT | |
| Easy Openclawdaheiai/easy-openclaw | 112 | — | ~1.7k | Automated safety check: Notes | None |
Similar skills
Traul Message Search
dandaka/traul
Drives the traul CLI to sync, search and monitor messages from Slack, Telegram, Discord, Linear, Gmail, WhatsApp, Claude Code sessions and Markdown files.
Conversation History
dashhuang/openclaw-chat-history-import
A skill your agent uses when the user asks what was said earlier in a chat, wants an old decision, exact wording, prior links, or suspects the agent forgot conversation context across Telegram…
Tlive
y49/tlive
tlive — remote approvals (Telegram/Feishu/web), live web terminal, and session monitoring for Claude Code / Codex.
Easy Openclaw
daheiai/easy-openclaw
OpenClaw 配置优化向导。采用“第 0 层测试观测（可选）+ 前 3 轮优化 + 第 4 轮接入扩展”流程：基础推荐层（含联网搜索与权限模式）、渠道增强层（Discord/Feishu/Telegram 分支优化）、Skills 推荐层（可执行可跳过）、新增渠道接入引导（可跳过）。用于帮助用户快速完成 OpenClaw 初始化或优化配置。用户说到“优化…
Message Push
0xranx/golembot
Send proactive messages to IM groups or individual users via the gateway Send API.
More from k1p1l0/claude-telegram-supercharged
Google Calendar via Telegram
k1p1l0/claude-telegram-supercharged
Manages Google Calendar from a Telegram chat: lists the schedule, creates and updates events, finds free time and sends daily briefings and reminders.
Telegram Daemon Manager
k1p1l0/claude-telegram-supercharged
Starts, stops, restarts and checks the launchd-managed Telegram bot daemon for Claude Code, and tails its supervisor logs and remote control URL.
Telegram Daemon Monitor
k1p1l0/claude-telegram-supercharged
Checks whether the Telegram daemon is alive, shows recent logs, finds the remote control URL and diagnoses MCP server problems.
Telegram Plugin Updater
k1p1l0/claude-telegram-supercharged
Updates the enhanced Telegram plugin for Claude Code from its GitHub repository: compares file hashes, shows recent commits, asks first, then runs the installer.
Related
Works with
Categories
Questions about Telegram Context Transfer
What does Telegram Context Transfer do?
Hands the current Claude Code session's context to a Telegram bot session by writing a short summary to the bot's memory file and sending it as a Telegram message. The skill summarizes the conversation so far into a structured handoff covering what you were working on, key decisions, current state, files changed and action items for the bot, kept under 2000 characters because the bot has limited context. It asks what you want to transfer rather than dumping everything: saying teleport everything summarizes the whole conversation, while teleport this sends only the latest topic.
When should I use Telegram Context Transfer?
Telegram Context Transfer fits situations like: continuing a terminal Claude Code task from the Telegram bot; sending the current task's state and next steps to your phone; persisting a session summary into the bot's memory.
How do I install Telegram Context Transfer in Claude Code?
Run `npx skills add k1p1l0/claude-telegram-supercharged --skill context -a claude-code`. Or copy the skill folder (skills/context in k1p1l0/claude-telegram-supercharged) into .claude/skills/context in your project. Claude Code loads it when a task matches its description.
How do I install Telegram Context Transfer in Codex?
Run `npx skills add k1p1l0/claude-telegram-supercharged --skill context -a codex`. Or copy the skill folder (skills/context in k1p1l0/claude-telegram-supercharged) into .agents/skills/context in your project. Codex loads it when a task matches its description.
Can I use Telegram Context Transfer 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 k1p1l0/claude-telegram-supercharged --skill context -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/context, .gemini/skills/context, .github/skills/context and .opencode/skills/context in your project.
What does Telegram Context Transfer need to run?
Going by SKILL.md and its folder, Telegram Context Transfer needs the command-line tools its instructions call (curl) and credentials named TELEGRAM_BOT_TOKEN and BOT_TOKEN. Our summary lists: A configured Telegram bot with TELEGRAM_BOT_TOKEN set; curl.
Does Telegram Context Transfer 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 Context Transfer 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 Telegram Context Transfer use?
Telegram Context Transfer 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 Context Transfer use?
About 764 tokens (SKILL.md is roughly 3.1k 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 Context Transfer?
Skills that share tags, products or a category with Telegram Context Transfer: Claude To Im (op7418/Claude-to-IM-skill, 2.9k stars), Traul Message Search (dandaka/traul, 113 stars), Conversation History (dashhuang/openclaw-chat-history-import, 144 stars) and Tlive (y49/tlive, 215 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Telegram Context Transfer?
k1p1l0 (a GitHub user) maintains it in k1p1l0/claude-telegram-supercharged, which has 132 GitHub stars. The repository holds 5 skills in this directory. The repository was last updated on September 26, 2026.
Source: k1p1l0/claude-telegram-supercharged on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.