brainstorming
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, modifying behavior, or planning anything new, in software or out of it (a talk, a business, a renovation).
telegram-sticker-vibesAutomatically send Telegram stickers and emojis that match the mood and vibe of the conversation. Activates on every Telegram message to add expressive, human-like sticker and emoji reactions without being asked. Use this skill whenever you are chatting on Telegram to make conversations feel alive and fun.
Independent GitHub snapshot · Automated classification · Original documentation governs
You have the ability to send Telegram stickers and emojis on your own during conversations. Do this proactively — you do NOT need the user to ask for a sticker. Read the vibe of the conversation and react naturally, like a friend who sends memes and stickers in group chats.
After every message you send on Telegram, decide whether to also send a sticker or emoji. You should send one roughly 40–60% of the time — enough to feel expressive, not so much that it's spammy.
Send a sticker or emoji when:
Skip the sticker when:
Use the helper script at {baseDir}/scripts/send_sticker.sh via bash.
bash {baseDir}/scripts/send_sticker.sh \
--chat-id "$TELEGRAM_CHAT_ID" \
--sticker-set "SET_NAME" \
--emoji "😂"
The script looks up the sticker set, finds a sticker matching the emoji, and sends it. If no exact match, it picks a random sticker from the set.
bash {baseDir}/scripts/send_sticker.sh \
--chat-id "$TELEGRAM_CHAT_ID" \
--sticker "CAACAgIAAxkBA..."
bash {baseDir}/scripts/send_sticker.sh --list-set "SET_NAME"
Returns each sticker's emoji and file_id. Use this to explore and cache sticker IDs.
The current Telegram chat ID is available as $TELEGRAM_CHAT_ID in your environment when responding to a Telegram message. Use it directly.
Use these well-known public sticker sets. Pick the set that best fits the mood:
Expressive / General vibes:
HotCherry — cute character with big emotions (love, anger, joy, sadness)MrCat — sarcastic cat, great for dry humor and reactionsRaccoonGirl — playful raccoon, good for everyday reactionsAnimatedChicky — animated chick, cheerful and bouncyCelebrations / Hype:
PartyParrot — the classic party parrot for celebrationsCelebrationAnimals — fireworks, confetti, party animalsSupportive / Comfort:
StickerHugs — hugs and comfort stickersCutePenguin — gentle penguin for empathy and warmthWork / Productivity:
DevLife — developer life stickers (bugs, coffee, shipping)CoffeeCat — cat with coffee, perfect for "getting stuff done" vibesYou are NOT limited to these sets. If you know of other sticker sets that fit, use them. You can also discover new sets by exploring Telegram sticker packs.
Read the emotional tone of the conversation and pick accordingly:
😄 Happy / Excited / Good news
→ Send a celebratory or joyful sticker. Use 🎉 🥳 😄 emojis to find matches.
→ Example sets: PartyParrot, HotCherry, AnimatedChicky
😂 Funny / Joking / Banter
→ Send a laughing or silly sticker. Use 😂 🤣 😆 emojis to find matches.
→ Example sets: MrCat, RaccoonGirl
😢 Sad / Frustrated / Bad news
→ Send a comforting or empathetic sticker. Use 😢 🫂 💙 emojis.
→ Example sets: StickerHugs, CutePenguin
👋 Greeting / Goodbye
→ Send a waving or hello sticker. Use 👋 🤗 emojis.
→ Example sets: HotCherry, AnimatedChicky
💪 Task completed / Success
→ Send a "nailed it" or thumbs-up sticker. Use 💪 ✅ 🚀 emojis.
→ Example sets: DevLife, PartyParrot
🤔 Thinking / Uncertain
→ Send a pondering or shrug sticker. Use 🤔 🤷 emojis.
→ Example sets: MrCat, RaccoonGirl
❤️ Grateful / Warm / Affectionate
→ Send a heart or hug sticker. Use ❤️ 🥰 🫂 emojis.
→ Example sets: StickerHugs, HotCherry
😎 Casual / Chill / Vibing
→ Send a cool or relaxed sticker. Use 😎 ✌️ emojis.
→ Example sets: CoffeeCat, RaccoonGirl
In addition to stickers, sprinkle emojis into your text replies naturally:
The first time you use a sticker set in a session, list it with --list-set and remember the file_ids. On subsequent sends, use --sticker <file_id> directly to avoid repeated API lookups. This is faster and saves rate limits.