access
Manage Telegram channel access — approve pairings, edit allowlists, set DM/group policy. Use when the user asks to pair, approve…
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.
$ npx -y skills add k1p1l0/claude-telegram-supercharged --skill context --agent claude-codeHow it fires
How this skill gets triggered: by you, by Claude, or both.
/contextContext preview
The summary Claude sees to decide when to auto-load this skill.
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.
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.
Transfer the current conversation context to the Telegram bot session so it can continue the work.
Summarize the current conversation into a structured context handoff. Include:
1. **What we were working on** — the main task/topic 2. **Key decisions made** — important choices, approaches taken 3. **Current state** — what's done, what's pending 4. **Files changed** — any relevant file paths 5. **Action items** — what the Telegram bot should do next (if any)
Keep it concise — under 2000 characters. The bot has limited context.
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.
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\"
}"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.
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]
Run Claude Code 24/7 from Telegram. Drop-in upgrade for the official plugin: voice notes both ways, a self-healing daemon, memory across restarts, and Agentic Mode (watch every tool call live). One-line install.
Manage Telegram channel access — approve pairings, edit allowlists, set DM/group policy. Use when the user asks to pair, approve…
Google Calendar integration — check schedule, create events, daily briefings, proactive reminders. Triggers on "what's on my…
Set up the Telegram channel — save the bot token and review access policy. Use when the user pastes a Telegram bot token, asks to…
Manage the Telegram daemon lifecycle — start, stop, restart, check status, tail logs. Use when the user says "start the bot",…
Monitor the Telegram daemon — check if it's alive, view recent logs, find the remote control URL, and diagnose MCP server issues.…