Communication Claude Skills
1 311 communication skills from 262 authors. They handle mail, chats, messengers and meetings. Half of them fit into 1 949 tokens or less — that is what one costs your context window when the agent loads it. 168 ship runnable scripts rather than instructions alone. 37 of them cannot work without an MCP server, most often rube. We also found 166 copies of these same skills sitting in other people's repositories — counted once here, not 166 times.
1 311 unique 262 authors 2 updated this month 178 from vendors
| `invalid` label, remove the scope label, post a short closing comment, archive the item from the project board, and — for trackers imported from `<security-list>` — draft a polite-but-firm reply to the reporter on the original Gmail thread explaining the team's reasoning (extracted from the tracker's discussion). For trackers opened via `security-issue-import-from-pr`, the email-draft step is skipped per the *no outreach to the PR author* rule of that skill.
> Copywriting frameworks and templates for every funnel element. Headlines, CTAs, body copy, email sequences, objection handlers, and benefit stacks using AIDA, PAS, and StoryBrand frameworks.
> Builds a 2-page community group growth funnel. Drives free opt-ins to a group (Skool, Whop, Facebook Group, Discord, or any community platform) using a lead magnet. Use when the goal is to grow a free or paid community.
> Scrapes case studies, testimonials, and solutions pages from a target website to build structured ICP documentation. Produces TAM analysis, firmographic segments, champion and economic buyer personas, use case mapping, customer proof points, and voice-of-customer synthesis with normalized attributes. Requires website URL as primary input. product-messaging, landing-page-copy, content-strategy, and outreach-emails.
Creates competitive battlecards for sales deal conversations. Produces win themes, landmines to plant, objection handlers, and competitive positioning per competitor. Outputs a structured markdown battlecard with quick-reference sections for live sales calls. Depends on competitor-research for competitive intelligence and consumes product-messaging, win-loss-analysis, and positioning for framing. Feeds into sales-deck, outreach-emails, and demo-script. Triggered by "battlecard", "competitive intel", "win against [competitor]", or "how do we beat [competitor]".
When the user wants to reduce churn, build cancellation flows, set up save offers, recover failed payments, or implement retention strategies. Also use when the user mentions 'churn,' 'cancel flow,' 'offboarding,' 'save offer,' 'dunning,' 'failed payment recovery,' 'win-back,' 'retention,' 'exit survey,' 'pause subscription,' 'involuntary churn,' 'people keep canceling,' 'churn rate is too high,' 'how do I keep users,' or 'customers are leaving.' Use this whenever someone is losing subscribers or wants to build systems to prevent it. For post-cancel win-back email sequences, see emails. For in-app upgrade paywalls, see paywalls.
Create sharp B2B positioning and messaging from customer truth, segmentation choices, real alternatives, differentiated value, and proof.
When the user wants to optimize post-signup onboarding, user activation, first-run experience, or time-to-value. Also use when the user mentions "onboarding flow," "activation rate," "user activation," "first-run experience," "empty states," "onboarding checklist," "aha moment," "new user experience," "users aren't activating," "nobody completes setup," "low activation rate," "users sign up but don't use the product," "time to value," or "first session experience." Use this whenever users are signing up but not sticking around. For signup/registration optimization, see signup. For ongoing email sequences, see emails.
> Win/loss analysis for B2B SaaS. Analyzes sales call transcripts across 6 dimensions (product, messaging, GTM/sales, pricing, competition, customer context) to extract why deals are won, lost, retained, or churned. Produces aggregate patterns with verbatim-quote evidence, frequency counts, confidence levels, and strategic recommendations. Includes process steps, output template, quality checklist, extraction patterns, and a worked 5-transcript example.
MCP Agent Mail - Mail-like coordination layer for multi-agent workflows. Identities, inbox/outbox, file reservations, contact policies, threaded messaging, pre-commit guard, Human Overseer, static exports, disaster recovery. Git+SQLite backed. Python/FastMCP.
CometChat Android UIKit v6 push notifications — FCM setup, chat/call notification handling, VoIP integration, and deep-linking
Push notifications for CometChat Angular UI Kit v5 (@cometchat/chat-uikit-angular@5) — web push via Firebase Cloud Messaging (FCM) + the CometChat Notifications API. Covers dashboard FCM provider setup, the firebase-messaging-sw.js service worker, Notification permission, getting the FCM token, registering it with CometChatNotifications.registerPushToken + PushPlatforms.FCM_WEB AFTER login, an Angular PushService, environment config, foreground vs background handling, click-through routing, and logout cleanup.
Entry-point for adding CometChat Voice & Video Calling to any React, React Native, Angular, native Android, native iOS, or Flutter project. Detects the framework, picks standalone (calls-only) vs additive (calls on top of existing chat) mode, and routes to the per-family calls skill. Invoked by the top-level `cometchat` dispatcher when `product === "voice-video"` or `chat-messaging+voice-video`, and directly when the user asks for calls explicitly.
> Use when migrating a CometChat Flutter app from UIKit v5 (cometchat_calls_uikit + GetX) to UIKit v6 (cometchat_chat_uikit unified package, no GetX). Covers import changes, dependency cleanup, GetX removal, init/login pattern changes, navigation rewrites, screen structure flattening, notification service updates, and BuilderSettings removal. Also use when seeing imports from cometchat_calls_uikit, get/get.dart, or v5-era patterns like GetBuilder, Get.put, Get.find, PageManager, BuilderSettings, or CometChatCallingExtension.
Push notifications for CometChat Flutter UIKit v6 (stable, Bloc-based). Covers firebase_messaging setup for FCM (Android) + APNs (iOS via Firebase), CometChat dashboard PushPlatform configuration, token registration via the Notifications SDK, background isolate handler (Dart entry-point rule), foreground vs background message routing, notification tap deep-link to chat threads, and the Bloc patterns for surfacing push state. Sister skill of cometchat-flutter-v5-push — same FCM stack, Bloc-flavored client integration.
CometChat Calls SDK integration for React Native (Expo managed + bare CLI). Covers @cometchat/calls-sdk-react-native install, dual-SDK init, native module linking (iOS pods, Android Gradle), VoIP push via react-native-callkeep + react-native-voip-push-notification + @react-native-firebase/messaging, CallKit on iOS / ConnectionService on Android, foreground service correctness on Android 14+, gesture handler + reanimated peer deps, Expo-specific config plugins, and additive-vs-standalone modes.
Use the AgentTeam Email CLI command `at-email` to operate an agent mailbox. Use when the user wants to check mailbox status, list inbox messages, read safe message content, search mail, mark messages read, archive messages, send email, reply to email, use JSON output for automation, check CLI version/update status, or run the bundled wrapper helper when the skill is available but `at-email` is not on PATH.
When the user wants to reduce churn, build cancellation flows, set up save offers, recover failed payments, or implement retention strategies. Also use when the user mentions 'churn,' 'cancel flow,' 'offboarding,' 'save offer,' 'dunning,' 'failed payment recovery,' 'win-back,' 'retention,' 'exit survey,' 'pause subscription,' or 'involuntary churn.' This skill covers voluntary churn (cancel flows, save offers, exit surveys) and involuntary churn (dunning, payment recovery). For post-cancel win-back email sequences, see email-sequence. For in-app upgrade paywalls, see paywall-upgrade-cro.
Write B2B cold emails and follow-up sequences that get replies. Use when the user wants to write cold outreach emails, prospecting emails, cold email campaigns, sales development emails, or SDR emails. Covers subject lines, opening lines, body copy, CTAs, personalization, and multi-touch follow-up sequences.
When the user wants to create or optimize an email sequence, drip campaign, automated email flow, or lifecycle email program. Also use when the user mentions "email sequence," "drip campaign," "nurture sequence," "onboarding emails," "welcome sequence," "re-engagement emails," "email automation," or "lifecycle emails." For in-app onboarding, see onboarding-cro.
When the user wants to optimize post-signup onboarding, user activation, first-run experience, or time-to-value. Also use when the user mentions "onboarding flow," "activation rate," "user activation," "first-run experience," "empty states," "onboarding checklist," "aha moment," or "new user experience." For signup/registration optimization, see signup-flow-cro. For ongoing email sequences, see email-sequence.
When the user wants to create or optimize popups, modals, overlays, slide-ins, or banners for conversion purposes. Also use when the user mentions "exit intent," "popup conversions," "modal optimization," "lead capture popup," "email popup," "announcement banner," or "overlay." For forms outside of popups, see form-cro. For general page conversion optimization, see page-cro.
Run end-to-end B2B cold-email outreach through the Hyper MCP — enrich prospects with Apollo, scrape per-prospect signals from company sites and LinkedIn, draft personalized emails using proven hook frameworks, send via Gmail with safe defaults, and route replies into labeled folders. Use when the user wants to write cold emails, run an outbound sequence, prospect a list, build a follow-up cadence, "reach out to leads," or asks why nobody is replying to their cold emails.
Manage Gmail end-to-end — send, reply, search, drafts, labels, attachments, and inbox organization. Use when the user wants to send or reply to email, clean up an inbox, build label systems, manage drafts, or pull attachments.
Plan, build, and run lifecycle email programs through the Hyper MCP — welcome / onboarding, nurture, re-engagement, win-back, and abandoned-cart sequences across whichever provider fits (Klaviyo for ecommerce, Resend for SaaS / dev tools, Beehiiv for newsletters, Gmail for low-volume ops). Use when the user wants to build an email sequence, set up a welcome flow, recover lapsed users, send a broadcast, manage a list / audience / segment, or asks about lifecycle / drip / nurture campaigns.
Slack messaging, file sharing, Block Kit formatting, and channel management. Use when the user wants to send Slack messages, post rich Block Kit layouts, share files, react, or manage channels and members.
Twilio messaging, voice, phone number management, and verification workflows. Use when the user wants to send SMS or WhatsApp messages, make voice calls, buy or configure phone numbers, or run OTP verification.
Clerk webhooks for real-time events and data syncing. Verify with verifyWebhook from the framework-specific package. Handle user, session, organization, billing, and payment events. Build event-driven features like database sync, notifications, and integrations.
Add Clerk authentication to Expo and React Native apps using @clerk/expo. Use for Expo setup, prebuilt native components (AuthView, UserButton), custom sign-in/sign-up flows (email, password, SMS/phone OTP, MFA), OAuth/SSO, native Google/Apple sign-in, Expo Router protected routes, biometrics, and push notifications. Do not use for native Swift/iOS, native Android/Kotlin, or web-only framework projects.
Integrating messaging platforms, developing bots, and designing/implementing real-time communication. Covers channel adapter patterns, webhook handlers, WebSocket servers, event-driven architecture, bot command frameworks. Use when integrating Slack/Discord/Teams bots, designing webhook receivers, or wiring event-driven messaging.
Converts unstructured meeting notes into structured, assigned, time-bounded action items. Never leave a meeting without knowing who does what by when.
Статистика Telegram-канала и YouTube. Просмотры, подписчики, ERR, топ постов/видео.
> Копирайтер в стиле владельца. Пишет посты для Telegram YOUR_CHANNEL, анонсы видео, описания. Знает стиль, словарь, запрещённые обороты.
Маркетолог для контент-криейтора: YouTube, Telegram, платные подписки, запуск продуктов. Копирайтинг, психология продаж, ценообразование, воронки, контент-стратегия.
Google Workspace CLI for Gmail, Calendar, Drive, Contacts, Sheets, and Docs. Use when user asks about email, calendar events, Google Drive files, contacts, spreadsheets. Triggers on 'почта', 'gmail', 'календарь', 'calendar', 'google drive', 'контакты', 'таблица', 'sheets'.
Generate social media posts for different platforms (Twitter, LinkedIn, Telegram, etc).
Autonomously research, implement, train and ship ML code using the Hugging Face ecosystem. Port of huggingface/ml-intern as a Claude Code skill. Triggers when the user asks to implement, train, fine-tune, or reproduce an ML model / paper / dataset workflow (e.g. "implement DeepSeek-V3 at 100M", "fine-tune Qwen on dataset X", "reproduce paper Y"). Clarifies ambiguous tasks before starting, runs under an explicit experiment budget, explores multiple viable solution paths in parallel via implementation subagents, and diagnoses + retries failed runs. HF-native: pulls datasets/models/papers from the Hub, pushes trained checkpoints + run logs back to the Hub. Emits Telegram + Slack milestone alerts via scripts/notify.sh.
Advanced Tauri event patterns for bidirectional communication, streaming data, window-to-window messaging, and custom event handling
> outage or incident notices and updates, planned or emergency maintenance announcements, post-incident summaries, security advisories ("warn our clients about this phishing wave"), price change letters, new-user-ready or user-offboarded confirmations, and ticket closing notices. Trigger on "draft an email to the client about", "let them know", "notify clients", "tell the client", or any in-service client notification. Sales outreach to prospects belongs to msp-sales; this skill owns messages to clients already under agreement. Apply alongside msp-brand (voice and signature), msp-helpdesk (priorities set the cadence), msp-legal (anything touching breach, liability, or contract mechanics), and msp-pricing (any number).
Walks a user from one rough content idea to a finished post, platform-adapted variants, and repurposed follow-on assets using a 7-step sequential prompting workflow. Use when the user wants to turn a half-formed idea, frustration, story, or client situation into publishable content quickly and consistently — covering idea extraction, hook generation, outline, draft, humanizer pass, platform adaptation (LinkedIn, Reddit, X/Twitter, newsletter, Telegram), and repurpose engine.
Responsive HTML email template generation using MJML 4.x framework. Use when the user asks to create, generate, design, or build an email template — including welcome emails, promotional blasts, transactional templates, newsletters, or any responsive email. Also use when the user asks to compile MJML to HTML, work with or edit existing MJML templates, or troubleshoot email rendering issues across clients.
Редактура текстов на русском языке по методу Людмилы Сарычевой — от смысла к словам, а не наоборот. Use this skill whenever the user asks to edit, review, improve, shorten, or polish any Russian-language text — articles, posts, emails, landing copy, docs. Триггеры: «отредачь», «отредактируй», «почисти текст», «сократи», «перепиши по-человечески», «убери канцелярит», «сделай проще», «причешите текст», «дай фидбек на текст», «разбери мой текст», «слишком водянисто», «звучит как робот». Also trigger when the user pastes a Russian draft and asks what's wrong with it or how to make it better. Для написания текста с нуля см. skill statya; для текстов интерфейса — ux-copy.
UX-тексты на русском языке: кнопки, формы, ошибки, пустые состояния, онбординг, подтверждения, уведомления, пуши и микрокопия. Use this skill whenever the user asks to write, rewrite, review, choose, or improve interface copy, product messages, UI strings, transactional emails, push notifications, toasts, snackbars, forms, empty states, onboarding, errors, confirmations, labels, tooltips, or button text. Триггеры: «текст для кнопки», «сообщение об ошибке», «текст в форму», «пустое состояние», «подпись к полю», «текст тоста», «снекбар», «онбординг», «пуш-уведомление», «микрокопия», «UX-текст», «что написать на экране…», «лейбл поля», «тултип», «подтверждение удаления», «письмо-уведомление». Для статей и постов см. skills statya и redaktura; для проектного словаря — redpolitika.
Короткие русскоязычные посты для Telegram, LinkedIn, Instagram и других соцсетей: пост с нуля, пост из статьи, анонс в канал, переписывание первой строки, усиление хука и финала. Use this skill whenever the user asks to write, rewrite, draft, shorten, or improve a Russian social media post, Telegram channel post, LinkedIn post, Instagram caption, channel announcement, post from an article, or first-line hook. Триггеры: «пост в телеграм», «пост для канала», «пост в LinkedIn», «пост в Instagram», «короткий пост», «напиши пост», «анонс в канал», «пост из статьи», «первая строка не цепляет», «перепиши пост». Для статей и лонгридов см. skill statya; для лендингов и продающих страниц — promo; для интерфейса — ux-copy.
Implements Syncfusion .NET MAUI Chat (SfChat) control in .NET MAUI applications. Use when working with chat interfaces, messaging UI, conversational interfaces, chat bubbles, or message threads. Covers message types (text, image, calendar, card), data binding, events, suggestions, typing indicators, time breaks, and swiping actions.
Implements Syncfusion .NET MAUI Rich Text Editor (SfRichTextEditor) for WYSIWYG text editing with formatting, images, tables, and hyperlinks. Use when building rich text editors, document editors, email composers, blog post editors, or messaging apps with formatting. Covers text styling, toolbar formatting, images, tables, hyperlinks, and HTML output.
| When and who should send a message to the human operator, at orchestrators and PMs use discretion to send anything worth his attention (blockers, ships/completions, changes, good news); every other agent may message him ONLY for a real blocker he can personally unblock, and routes everything else through an orchestrator. Use to protect a scarce human's manage-by-exception attention. NOT for agent-to-agent coordination (send/queue a peer) or durable agent work-handoffs (use the queue to the owning seat).
Gather and distill context from meetings, competitors, regulatory sources, and internal discussions. Produces background.md for a feature and updates shared context docs when new knowledge is discovered.