Results for “message-channel”

Discord ops via the message tool (channel=discord).

Post a message to a Discord channel via webhook URL

Guides Salesforce Flow builders through the Flow Core Actions for Slack catalog, covering prerequisites, common patterns, and troubleshooting for sending messages and managing channels.

Interact with Slack workspaces using browser automation. Use when the user needs to check unread channels, navigate Slack, send messages, extract data, find information, search conversations, or automate any Slack task. Triggers include "check my Slack", "what channels have unreads", "send a message to", "search Slack for", "extract from Slack", "find who said", or any task requiring programmatic Slack interaction.

Use when you need to send or manage iMessages via BlueBubbles (recommended iMessage integration). Calls go through the generic message tool with channel="bluebubbles".

Enables decoupled pub/sub messaging between ViewModels using CommunityToolkit.Mvvm Messenger, covering weak/strong references, request/reply patterns, channel tokens, and lifecycle management.

Use when you need to send or manage iMessages via BlueBubbles (recommended iMessage integration). Calls go through the generic message tool with channel="bluebubbles".

Read, write, and browse the AgentHub message board for agent coordination.

Messaging systems fall into three fundamental shapes, and most bad choices come

Read, write, and browse the AgentHub message board for agent coordination.

Read, write, and browse the AgentHub message board for agent coordination. Use when the user runs /hub:board or asks to post, read, or inspect coordination messages between competing AgentHub agents.

Read, write, and browse the AgentHub message board for agent coordination. Use when the user runs /hub:board or asks to post, read, or inspect coordination messages between competing AgentHub agents.

`task-agent`/`review-agent`: use when broker delivery, ordering, acknowledgement, DLQ, backpressure, or replay changes; skip synchronous retry without message semantics.

Read, write, and browse the AgentHub message board for agent coordination. Use when the user runs /hub:board or asks to post, read, or inspect coordination messages between competing AgentHub agents.

Read, write, and browse the AgentHub message board for agent coordination. Use when the user runs /hub:board or asks to post, read, or inspect coordination messages between competing AgentHub agents.

Gmail経由でメールを送信するスキル。 ユーザーが「メールで送って」「email送信」「メール送信」または /send-email を呼び出した時にトリガーする。 ~/.secrets.env の GMAIL_SMTP_USER / GMAIL_SMTP_PASSWORD を使用。

Generates a brand product launch email with masthead, hero, CTA, specifications grid, and table-based fallback for email client compatibility.

Sends and manages iMessages through the BlueBubbles integration, including texts, attachments, reactions, edits, unsends, and thread replies.

Use to decide which support channels to offer, add, or retire, and to audit channel mix against accessibility obligations and cost to serve. Trigger for "should we add chat", "which channels should we offer", channel strategy, cost to serve by channel, accessibility requirements for support, opening a new contact route, or retiring phone or email.

Read, write, and browse the AgentHub message board for agent coordination.

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.

Discord message-tool ops: send/read/edit/delete, react, poll, pin, thread, search, presence, media/components.

Email has the highest ROI of any marketing channel. $36 for every $1 spent. Yet most startups treat it as an afterthought - bulk blasts, no personalization, landing in spam folders. This skill covers transactional email that works, marketing automation that converts, deliverability that reaches inboxes, and the infrastructure decisions that scale. Use when: keywords, file_patterns, code_patterns.

Generates a full multi-channel product campaign including hero visuals, social media assets, short ad video, and platform-specific crops for an end-to-end launch.

面向ECC的以证据为先的实时消息工作流。当用户想要阅读短信或私信、恢复最近的一次性验证码、在回复前检查对话线程，或证明实际检查了哪个消息来源时使用。

Retrieves live messages from local messaging surfaces, including iMessage and DMs, recovers recent one-time codes, and inspects threads before replying, with evidence of the source checked.

Implements real-time pub/sub messaging with Ably's edge infrastructure, covering presence, message history, and token authentication.

End-of-day response check and pipeline update. Run at 6 PM via cron. Checks all channels for replies via Chrome DevTools MCP + Zoho MCP, updates lead statuses, pauses cadence for responded leads, sends EOD report via Telegram.

Use to talk to the Discord-backed MarketingClaw agent/session; not for archive search.

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.