1 294 communication skills from 262 authors. They handle mail, chats, messengers and meetings. Half of them fit into 1 952 tokens or less — that is what one costs your context window when the agent loads it. 167 ship runnable scripts rather than instructions alone. 37 of them cannot work without an MCP server, most often rube. We also found 160 copies of these same skills sitting in other people's repositories — counted once here, not 160 times.
1 294 unique 262 authors 801 updated this month 161 from vendors
Posting, members, Telegram group management
Automatic inbound Telegram message processing
通过独立 Telegram Bot 向群聊或私聊推送消息，适合不依赖 OpenClaw channel 配置的通知场景。
Search Telegram channels, read posts, ad contacts
Automatic Telegram scraping
Telegram DM sending from CSV, rate limiting, idempotency
Create/update Telethon session
Read posts and comments from Telegram channels via MTProto (Pyrogram or Telethon). Fetch recent messages and discussion replies from public or private channels by time window.
微信 (WeChat) 与 OpenClaw 的双向集成通道。基于 Wechaty + PadLocal 实现微信消息的接收和发送，支持私聊、群聊、@提及检测、图片/文件传输。当需要通过微信与 AI 助手交互、接收微信消息触发 AI 响应、或从 OpenClaw 发送消息到微信时使用此技能。
企业微信个人账号直连自动化。基于 Wechaty 框架实现企业微信消息接收、自动同意好友、知识库问答、人工介入提醒。适用于企业微信个人机器人和自动化助手场景。
Automate Zoom meeting creation, management, recordings, webinars, and participant tracking via Rube MCP (Composio). Always search tools first for current schemas.
> Receive and verify Attentive webhooks. Use when setting up Attentive webhook handlers, debugging signature verification (x-attentive-hmac-sha256), or handling SMS and email events like sms.subscribed, sms.unsubscribed, email.opened, or custom_attribute.set.
> Receive and verify Customer.io Reporting Webhooks. Use when setting up Customer.io webhook handlers, debugging X-CIO-Signature verification, or handling messaging events like email delivered, email opened, email clicked, email bounced, sms sent, push delivered, or customer unsubscribed.
> Receive and verify Discord webhook events. Use when setting up Discord webhook handlers, debugging Ed25519 signature verification, handling PING endpoint validation, or processing events like APPLICATION_AUTHORIZED, ENTITLEMENT_CREATE, or LOBBY_MESSAGE_CREATE.
> Receive and verify Fireflies.ai webhooks. Use when setting up Fireflies webhook handlers, debugging X-Hub-Signature verification, or handling the meeting.transcribed, meeting.summarized, and meeting.bot_joined events from Webhooks V2. Also covers the legacy V1 scheme.
> Receive and verify Intercom webhooks. Use when setting up Intercom webhook handlers, debugging X-Hub-Signature verification, or handling customer messaging events like conversation.user.created, conversation.admin.replied, contact.user.created, or ticket.created.
> Receive and verify Mailgun webhooks. Use when setting up Mailgun webhook handlers, debugging Mailgun signature verification, or handling email events like delivered, failed, opened, clicked, unsubscribed, and complained.
> Receive and verify Nylas webhooks. Use when setting up Nylas webhook handlers, debugging x-nylas-signature verification, completing the challenge handshake, or handling email and calendar events like message.created, message.opened, event.created, event.updated, or grant.expired.
> Receive and process Postmark webhooks. Use when setting up Postmark webhook handlers, handling email delivery events, processing bounces, opens, clicks, spam complaints, or subscription changes.
> Receive and verify Resend webhooks. Use when setting up Resend webhook handlers, debugging signature verification, handling email events like email.sent, email.delivered, email.bounced, or processing inbound emails.
> Receive and verify SendGrid webhooks. Use when setting up SendGrid webhook handlers, debugging signature verification, or handling email delivery events.
> Receive and verify Slack Events API webhooks. Use when setting up Slack webhook handlers, debugging Slack signature verification, handling the url_verification challenge, or processing events like app_mention, message, reaction_added, team_join, or app_home_opened.
> Receive and verify Telnyx webhooks. Use when setting up Telnyx webhook handlers, debugging Ed25519 signature verification with the telnyx-signature-ed25519 and telnyx-timestamp headers, or handling messaging events like message.received, message.sent, or message.finalized.
> Receive and verify Zoom webhooks. Use when setting up Zoom webhook handlers, debugging signature verification, completing the endpoint.url_validation handshake, or handling meeting and recording events like meeting.started, meeting.ended, meeting.participant_joined, or recording.completed.
Use when the user wants to register, inspect, manually run, or remove scheduled Claude skills with Telegram push notifications. Presents a menu, discovers schedulable skills with headless-prompt frontmatter, converts natural-language schedules into cron entries with conflict confirmation, writes managed config, and verifies notification delivery. NOT for one-off task execution without scheduling or for running skills that lack a headless prompt.
>- Coordinate agents via the AMQ CLI for file-based inter-agent messaging. Use this skill whenever you need to send messages to another agent (codex, claude, or any named handle), check your inbox, drain queued messages, set up co-op mode between agents, join a swarm team, route messages across projects, or diagnose delivery issues. Also use it when you receive a message and need to know how to reply, inspect receipts, or handle priority. Covers any multi-agent coordination task where agents need to talk to each other — review requests, questions, status updates, decision threads, wake notifications, and orchestrator integration (Symphony, Kanban). For collaborative spec/design workflows specifically, prefer the /amq-spec skill which provides structured phase-by-phase guidance. Not intended for distributed systems design (RabbitMQ, Kafka), CI/CD pipelines, or single-agent tasks with no partner.
Format dates and times according to specific requirements for meeting confirmations
Parse meeting request emails from JSON format and extract duration and time constraints
Techniques for retrieving structured information from enterprise Slack/document JSON data files.
Workflow for parsing meeting request emails, matching constraints to calendar availability, and generating reply files.
Parse meeting request emails to extract duration and time constraints, then find the earliest available time slot on a calendar.
Read input JSON files with email requests and write results.json with reply filenames and recipients.
Skill to extract information from the structured JSON data, including Slack messages and document metadata.
Parse duration and time constraints from email text.
Algorithm to find earliest available meeting slots given constraints and existing appointments.
Uses regular expressions to parse dates, time ranges, and durations from natural language text like meeting requests.
Mine Slack data for embedded URLs, mentioned products, competitive intelligence, and cross-referencing with external data sources.
Correlate and merge data from multiple sources (documents, Slack, meetings, URLs) to answer enterprise questions.
Parse meeting requests with timezone handling and constraint detection
Comprehensive guide for retrieving structured information from enterprise JSON data files containing Slack messages, documents, meetings, and metadata.
Advanced patterns for analyzing Slack conversations to extract reviewers, competitor insights, and shared resources from enterprise product channels.
Schedule meetings into calendar free slots considering time constraints, timezone conversion, and blue-block overrides.
Finding competitor product discussions, insights, and demo URLs across all ContentForce-related Slack channels
Complete guide to retrieving structured answers from enterprise product JSON data files containing Slack, documents, meetings, and PRs
Schedule multiple meeting requests into a calendar with earliest-first logic, then generate formatted reply .txt files and a results.json summary.
Skill for scheduling meetings.
Deep parsing and structural querying of nested JSON documents, resolving implicit relations across multi-modal corporate datasets like Slack messages and PRs.
Extract evidence from all three tiers (explicit reviewers, substantive feedback contributors from Slack and transcripts, and other identifiable contributors). Follow artifact references and traverse relationships to collect complete answer sets.