Results for “sending”

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.

Email inbox for AI agents. Check messages, send emails, and communicate via your own @agentmail.to address.

This skill should be used when the user asks to "send tokens", "transfer ETH", "send to ENS", "transfer to wallet", "send to @username", "transfer to Farcaster", "send to Twitter handle", or any asset transfer operation. Provides guidance on recipient resolution and transfer formats.

Delegate tasks to OpenAI Codex CLI and Google Antigravity CLI from Claude Code with topic-aware sessions.

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.

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.

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.

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.