telegram-reply
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.
More from avivsinai/telclaude
weather
Fetches weather forecasts using wttr.in. Use when users ask about weather, temperature, forecasts, or conditions for any location.
2gifgrep
Searches for GIFs from Tenor/Giphy and downloads them for sending via Telegram. Use when users want reaction GIFs, memes, or animated images.
1memory
Social memory management for Telegram and social agents
1text-to-speech
Converts text to speech audio using OpenAI TTS API. Use when users request audio versions of text or want responses read aloud.
1integration-test
Full SDK integration test that runs actual queries through the Claude SDK sandbox. Use after making changes to SDK client code, session management, skill loading, network proxy, voice/TTS, or image generation. Runs real prompts through the SDK to verify the complete path works.
1summarize
Extracts and summarizes web content from URLs. Use when users share links or ask to summarize articles, YouTube videos, or web pages.
1