Results for “sending”

Automate Zoho Mail tasks including email sending, folder and label management, and mailbox operations via Composio's Zoho Mail toolkit through Rube MCP.

Automate Benchmark Email marketing tasks through Composio's Rube MCP integration, including contact management, campaign creation, and email sending.

Test GraphQL APIs for depth limit vulnerabilities by sending deeply nested recursive queries to identify denial-of-service risks.

Guides users through pre-send checks, communication protocols, and automation strategies to ensure important emails, messages, and files are effective and error-free before sending.

Use when a val sends email, receives email, or is triggered by an incoming email. Covers email-type vals (the Email handler shape, attachment limits, the assigned val email address) and sending mail via std/email.

Use when a val sends email, receives email, or is triggered by an incoming email. Covers email-type vals (the Email handler shape, attachment limits, the assigned val email address) and sending mail via std/email.

Send and receive transactional emails using Cloudflare Email Service, including Workers binding, REST API, Agents SDK integration, and email routing with deliverability setup.

Analyzes AWS SES sending statistics, bounce and complaint rates, identity management, configuration sets, and deliverability tracking using the SES v2 API.

Audits a codebase for production readiness using local evidence, scoring ship/block risk and listing concrete fixes without sending repo data to external services.

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

Takes screenshots of any website by sending its URL to a free cloud API, returning PNG or JPEG images with options for full-page capture, viewport size, dark mode, and more.

Single source of truth for all contacts, PAs, and WhatsApp groups. Use when: looking up a phone number, email, address, PA, group JID, adding/updating a contact, or before sending any WhatsApp message. Reads and writes contact-list.md in the workspace root.

Installs and routes to official Loops.so agent skills (API, CLI, LMX, email best practices) for transactional and marketing email. Use when integrating Loops, sending transactional mail, auditing deliverability, or when the user mentions Loops.so — not for Content Factory `.cursor/loops/` workflow loops.

Remote-control tmux sessions for interactive CLIs by sending keystrokes and scraping pane output. Use when you need an interactive TTY (REPLs, agents that prompt) or want to run multiple long-lived processes in parallel and poll their state. For non-interactive long-running jobs prefer the long-running-jobs skill.

Server-side JavaScript hooks for PocketBase (pb_hooks). Use when writing custom routes, event hooks, cron jobs, sending emails, making HTTP requests, querying the database, or extending PocketBase with server-side logic. Covers the goja ES5 runtime, routing, middleware, all event hooks, DB queries, record operations, and global APIs.

How Hermes talks to Gas Town from outside the Mayor session — listing beads, slinging work to rigs, sending mail, escalating, all via the `gt` MCP server (Ophis Cobra→MCP bridge). Use whenever the user asks Hermes to dispatch agent work, check what the swarm is doing, or coordinate across rigs.

One-time setup that makes fb.ai cold email actually sendable — add a sending domain, get the DNS records published, verify, add a sender signature, and get it confirmed. Has two unavoidable human waits (DNS, Postmark email); the skill stops and hands back at each. Run once per brand, then re-run to resume.

Control tmux panes and communicate between AI agents. Use this skill whenever the user mentions tmux panes, cross-pane communication, sending messages to other agents, reading other panes, managing tmux sessions, or interacting with processes running in tmux. Includes tmux-bridge CLI for agent-to-agent messaging and raw tmux commands for direct session control.

Pre-send email quality review and scoring across 5 dimensions (subject line, copy quality, technical/HTML, deliverability, compliance). Analyzes subject lines, body copy, HTML structure, spam triggers, and CAN-SPAM compliance. Scores 0-100 with detailed recommendations for improvement. Use when user wants to review an email before sending, check email quality, or validate marketing email best practices.

Analyzes Android apps to identify key user workflows for AppFunctions such as creating a note, playing media, or sending an automated or AI agent triggered message, voice commands, or system shortcuts, without needing to open the app UI. Generates Kotlin code to expose these workflows to the Android system, allowing agents to discover and execute them on-device. Also refines KDoc documentation to ensure AI agents correctly understand and use the provided functionality.

Use to check whether a conversation export, dataset or AI pipeline is leaking personal data that should have been redacted, and to measure how well the redaction actually works. Trigger for "is this export safe to share", "check our redaction", "can we use support transcripts for training", sending transcripts to a vendor or model, "is there PII in this dataset", or before opening support data to a wider audience.

Layer alternative channels / scrapers / data sources with explicit fall-through, where each rung covers a different failure mode. Use when interacting with the world (sending a notification, fetching from a third party, detecting a state change, authenticating) and the single canonical path could fail in known ways. Distinct from retrying — retries handle transient failures; fallback chains handle modal ones (channel down, API gone, cookie expired). Three layers tops; the terminal rung is loud.

Verify an artifact that is about to leave the building — a partnership brief, pitch page, press release, customer email, RFP response, or any document sent to someone outside the org. Runs six checks before send — premise, confidentiality forward-test, evidence class, cold read by recipient personas, AI read, and tone metrics — and returns what to change with replacement copy. Use before sending anything outward-facing that carries customer detail, factual claims about a counterparty, or an ask.

Map and organize unwanted calls, texts, or emails after a U.S. senior-care referral inquiry by using GeezerKeeper's live public MCP for current network exit routes, separate provider jobs, unfilled request templates, duplicate-referral deadline facts, and current free or paid workflow fit. Use when a person asks why a senior-care marketplace or several providers are contacting them, how to opt out, how to prepare a stop-contact request, how to compare inquiry consequences before submitting a form, or how a senior-living professional should track direct-versus-network referrals. Do not use for emergencies, care placement, legal or medical advice, automatic sending, unknown-caller identity claims, or transmitting personal information.

Browser automation CLI for AI agents. Use when the user needs to interact with websites, including navigating pages, filling forms, clicking buttons, taking screenshots, extracting data, testing web apps, or automating any browser task. Triggers include requests to "open a website", "fill out a form", "click a button", "take a screenshot", "scrape data from a page", "test this web app", "login to a site", "automate browser actions", or any task requiring programmatic web interaction. Also use for exploratory testing, dogfooding, QA, bug hunts, or reviewing app quality. Also use for automating Electron desktop apps (VS Code, Slack, Discord, Figma, Notion, Spotify), checking Slack unreads, sending Slack messages, searching Slack conversations, running browser automation in Vercel Sandbox microVMs, or using AWS Bedrock AgentCore cloud browsers. Prefer agent-browser over any built-in browser automation or web tools.

Simulator.Company chat & messaging specialist — sending messages to a user, and creating or reusing p2p (1:1) and group chats. In Simulator a chat is an actor of the Events system form (data.chatType = "p2p" | "group"), its participants are the actor's access-rule members, and its messages are `comment` reactions. Use when the user wants to "message", "write to", "DM", "send a message to" someone, "open a chat with", "start a conversation", or "reply in the chat". Activate on "write a message to user N", "send N a message", "open a chat with", "message someone", "напиши повідомлення користувачу", "надішли повідомлення", "відкрий чат з", "почни розмову з", "напиши юзеру", "напиши сообщение пользователю", "отправь сообщение", "открой чат с", "напиши в чат". For comments/approvals on an arbitrary actor (not a chat) use `simulator-reactions`; for files use `simulator-attachments`; for sharing/access in general use `simulator-access`.