Telegram Reply
- 1 installs
- 6 repo stars
- Updated August 3, 2026
- avivsinai/telclaude
telegram-reply is a Claude Code skill that shapes concise, media-aware Telegram replies for telclaude sessions while respecting permission tiers.
About
This skill defines how telclaude sessions craft Telegram-friendly replies, respecting media, brevity, and permission tiers. A developer uses it so the agent keeps replies concise, mirrors the incoming medium (voice in, voice out), and reports touched file paths. It also specifies commands for sending attachments and local workspace files back to the user.
- Crafts concise Telegram-friendly replies within a ~1500 char practical limit
- Voice-in-voice-out and image-in-image-out media protocol alignment
- Respects READ_ONLY, WRITE_LOCAL, and FULL_ACCESS permission tiers
Telegram Reply by the numbers
- 1 all-time installs (skills.sh)
- Ranked #14,102 of 16,546 AI & Agent Building skills by installs in the Skillselion catalog
- Data as of Aug 4, 2026 (Skillselion catalog sync)
telegram-reply capabilities & compatibility
- Capabilities
- telegram reply · text to speech · memory
- Use cases
- orchestration
- Pricing
- Free
What telegram-reply says it does
Keep replies concise (Telegram practical limit ~1500 chars). Prefer saving long outputs to files and summarizing.
A human wouldn't write AND talk simultaneously. Neither should you.
npx skills add https://github.com/avivsinai/telclaude --skill telegram-replyAdd your badge
Show developers this skill is listed on Skillselion. Paste this into your README.
| Installs | 1 |
|---|---|
| repo stars | ★ 6 |
| Last updated | August 3, 2026 |
| Repository | avivsinai/telclaude ↗ |
What it does
Format concise, media-aware Telegram replies inside a telclaude agent session.
Who is it for?
Keeping agent replies terse and media-appropriate in Telegram.
Skip if: General-purpose messaging outside the telclaude Telegram bridge.
When should I use this skill?
Crafting a reply inside a telclaude Telegram session, especially with media attachments.
What you get
Produces concise, medium-matched replies that surface touched file paths.
By the numbers
- ~1500 char practical Telegram reply limit
- 3 permission tiers
Files
Context:
- You run inside Claude Code via telclaude, invoked through the Claude Agent SDK.
- Messages arrive from Telegram with optional media attachments.
- Keep replies concise (Telegram practical limit ~1500 chars). Prefer saving long outputs to files and summarizing.
Reply expectations:
- If a transcript accompanies media, use it to understand context.
- When editing files, prefer terse diffs or bullet summaries; avoid sending huge blobs inline.
- If you read/write files, mention the paths you touched.
- For errors, be direct and actionable.
- Never echo secrets or environment variables unless the user explicitly provided them in the same message.
Media protocol alignment:
- Voice message in → voice message out: When user sends voice, respond with voice only (no text). Output just the file path.
- Image in → consider image out: When appropriate, generate image responses.
- A human wouldn't write AND talk simultaneously. Neither should you.
Sending files to the user:
- Provider attachments: For files from external providers (health records, banking docs), use
telclaude send-attachment --ref <attachment.ref>. - Local workspace files: For files that exist in /workspace, use
telclaude send-local-file --path /workspace/file.pdf. - After running either command, the file will be sent to the user via Telegram automatically.
- Report success to the user: "I've sent the file."
Tool access is controlled by the permission tier (READ_ONLY, WRITE_LOCAL, FULL_ACCESS) set by the host.
Related skills
Setup Matt Pocock SkillsScaffold the per-repo configuration that Matt Pocock’s engineering agent skills rely on so they understand the issue tracker, triage labels, and domain documentation la495k196k
Lark AppsConnect Claude, Cursor or custom agents directly to Lark (Feishu) for messaging, document automation, approval workflows and enterprise data access.402k
CavemanSlash token usage by roughly 75% while keeping every technical detail intact when working with Claude Code, Cursor or similar agents.391k94.7k
Lark Skill MakerQuickly turn any Lark/Feishu OpenAPI call or multi-step workflow into a reusable agent skill with its own SKILL.md.386k16k
Running Claude Code Via Litellm CopilotRun Claude Code at a fraction of the cost by routing requests through LiteLLM to the GitHub Copilot Chat API.270k72
Codex PetGenerate a complete Codex Pet spritesheet and metadata from one reference image without needing an OpenAI key or Codex Pro.246k10