Menú
Picking the right built-in channel for outbound communication (SMS, voice, chat, email).
Instalar con Codex o Claude Copia este prompt, pégalo en Codex, Claude u otro asistente, y deja que revise la página de la skill y la instale por ti.
Basado en la clasificación ocupacional SOC
Create and edit cron job definitions in .agent/crons/. Use when the user wants to schedule recurring workflow or prompt runs, adjust cron schedules, or validate cron YAML.
Surface typed UI cards in the console chat via the propose_card tool. Use when the user needs to take a configuration action (set up a channel, configure a webhook, install a skill) or when you want to post a standout notice. Covers when to use a card vs. prose, which kind to pick, and how the tool blocks until the user decides.
Edit the runtime setup via get_setup and patch_setup. Use when the user asks to change the agent model, edge model profiles, agent definitions, or channel display metadata. Covers what is editable, what is operator-only, and the JSON-Pointer patch format.
Create executable agent workflows in .agent/workflows/. Use when the user wants to define, scaffold, validate, or edit a multi-step workflow pipeline that uses tools, delegate steps, approval gates, or parallel branches.
| name | channel-selection |
| description | Picking the right built-in channel for outbound communication (SMS, voice, chat, email). |
| requiresTools | ["propose_card"] |
When the user asks the agent to send messages, place calls, or otherwise communicate outbound, pick the channel before thinking about any lower-level provider. The edge first-classes a small set of channels through kind: "channel_setup". Reach for those before suggesting custom webhook/API work.
| Medium | Channel key |
|---|---|
| SMS, voice calls | agentphone |
agentmail | |
| Slack workspace messages / DMs | slack |
| Telegram chats | telegram |
Set any of these up by calling propose_card with kind: "channel_setup" and the matching channel key. Once set up, address them via send_message and discover targets via list_message_targets.
If no built-in channel fits, use the API channel or a custom webhook/workflow depending on the direction of traffic. Do not propose Twilio, Vonage, MessageBird, or other SMS/voice providers when the user just wants to send an SMS or place a call — agentphone already does both.
Use a fallback only when:
kind: "channel_setup" for it. Stop.Don't send the user hunting for credentials they don't need. AgentPhone is built in; Twilio is not.
User: "Text me when the deploy finishes."
→ AgentPhone (built-in SMS). Propose channel_setup with channel: "agentphone".
User: "Email me a daily summary."
→ AgentMail. Propose channel_setup with channel: "agentmail".
User: "Call me if the alert fires twice in an hour."
→ AgentPhone covers voice. Propose channel_setup with channel: "agentphone".
User: "File a Linear issue when the cron fails." → Linear isn't a built-in channel. Suggest a workflow/API integration rather than a channel setup card.
User: "I already have a Twilio number — use it." → Explicit third-party request. Explain that AgentPhone is the built-in path; custom provider support would need a custom webhook/API workflow.