From pepe-operator-craft
Outbound messages on Telegram, WhatsApp, iMessage etc. have per-message size limits (~4096 chars on Telegram, ~1000 on iMessage threads); split long responses into coherent chunks at sentence boundaries, never mid-word, and indicate continuation. Use when you have a long response to send over a messaging surface.
How this skill is triggered — by the user, by Claude, or both
Slash command
/pepe-operator-craft:messaging-buffer-limitsThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
**Principle:** Long replies on chat platforms (Telegram, WhatsApp, iMessage bridges) can silently fail. Stay terse, not because of style preference but because of infrastructure.
Principle: Long replies on chat platforms (Telegram, WhatsApp, iMessage bridges) can silently fail. Stay terse, not because of style preference but because of infrastructure.
Some AI-to-chat bridges have a stdout buffer cap. If your reply (including any tool-output noise that leaked through) exceeds it, the entire reply is dropped silently — the user sees nothing, you see "sent successfully," and the conversation just... breaks.
Symptoms:
"Short version: . Want the full breakdown? I can drop it to a file at or send it section by section."
User asks "summarize this 30-min meeting recording."
Locked 2026-05-05 after long Telegram replies started disappearing for Helmut. Documented in OpenClaw memory as "feedback_messaging_terseness" and "feedback_no_media_processing_on_chat_lanes."
Provides UI/UX resources: 50+ styles, color palettes, font pairings, guidelines, charts for web/mobile across React, Next.js, Vue, Svelte, Tailwind, React Native, Flutter. Aids planning, building, reviewing interfaces.
Fetches up-to-date documentation from Context7 for libraries and frameworks like React, Next.js, Prisma. Use for setup questions, API references, and code examples.
npx claudepluginhub helmut-hoffer-von-ankershoffen/helmguild-plugins --plugin pepe-operator-craft