sent
Routes broad or ambiguous Sent requests to the correct MCP-backed operation or specialist skill. Use when the user asks what Sent can do, says "help me with Sent" or "set up messaging," needs several Sent workflows, or has not made the channel, task, or desired operation clear enough to select a more specific skill.
- Installs
- 2.9K
- Last 24h
- —
- Trending rank
- —
- Security
- Not audited
Install
Works with every agent the skills CLI supports.
npx skills add https://github.com/sentdm/sent-plugin --skill sent- 01
Install
Run the command in your project. The CLI asks which agents to install for.
- 02
Describe the task
Ask your agent for something this skill covers. It loads sent automatically when relevant.
- 03
Review the result
The agent follows the SKILL.md steps, scripts and references bundled with the skill.
SKILL.md
The instructions your agent reads when the skill is triggered.
Sent Meta Dispatcher
Overview
This skill is a router, not a worker. When a request does not identify one clear Sent workflow, inspect the intent, ask only the clarification needed to select a route, and invoke the matching skill.
Sent spans direct account operations through its MCP server and specialist guidance for SMS, WhatsApp, RCS, Sender Profiles, templates, and delivery analysis. Prefer a direct-operation skill for live Sent data or mutations and a specialist skill for planning, compliance, diagnosis, or product design.
When to Use
Use when:
- The user mentions "Sent" broadly without naming a channel ("help me with Sent", "I want to use Sent for messaging")
- The user asks an open-ended question like "what can you help with on Sent?" or "where do I start?"
- The request could plausibly span multiple target skills (e.g., "messaging isn't working" — could be account readiness, 10DLC vetting, WABA template rejection, RBM capability, or an MDR funnel)
- The channel is ambiguous (SMS vs WhatsApp vs RCS not stated; geography matters because 10DLC is US-only)
- The surface is ambiguous (API integration vs dashboard UX vs compliance paperwork)
- The user pastes a Sent dashboard URL or API path without further context
Do not use when:
- The user has already named one supported operation or specialist workflow; invoke that skill directly.
- The question is purely about pricing, contracts, or unsupported product policy; point the user to
https://docs.sent.dmor Sent support.
Routing rules
MCP-backed operations
| User intent | Target skill |
|---|---|
| Preview, send, or schedule an existing templated message; inspect one message and its activity | sent-messaging |
| List, inspect, create, summarize, or delete Sent contacts | sent-contacts |
| Find, inspect, or delete existing Sent templates | sent-templates |
| Query dashboard messaging metrics or look up number capabilities | sent-analytics |
| Check the selected account, balance, onboarding state, or readiness to send | sent-account-readiness |
| Report a bug, missing feature, confusing result, or praise to Sent with user authorization | sent-feedback |
| Inspect SMS market fields, document requirements, or an exact setup call | sent-compliance |
| List, get, create, update, or delete owned Sender Profiles through MCP | sent-profile-provisioning |
Specialist guidance
| User intent | Target skill |
|---|---|
| SMS compliance, 10DLC, brand or campaign registration, TCR vetting, or carrier rejects | sms-10dlc-registration |
| Authoring WhatsApp template content, choosing a category, or fixing a Meta rejection | waba-template-author |
| Connecting a WABA through Embedded Signup, callbacks, token exchange, or phone-number mapping | waba-embedded-signup |
| Launching RCS, preparing an RBM agent, or deciding capabilities and fallback | rcs-agent-onboarding |
| Designing multi-tenant Sender Profile boundaries, routing, or rate-limit ownership | sender-profile-architect |
| Diagnosing delivery from MDR exports, funnels, cohorts, or cross-channel failure codes | messaging-performance-analyzer |
| Designing or auditing a tenant-facing template-builder UI | template-builder-ui |
Engineering and integration
| User intent | Target skill |
|---|---|
| Adding Sent to a codebase, choosing an SDK, or hardening retries, idempotency, and error handling before launch | sent-integration-starter |
| Building or debugging a webhook receiver, signature verification, dedupe, or an auto-disabled endpoint | sent-webhook-engineer |
| Choosing the channel field, expecting cross-channel fallback, or interpreting a route, reroute, or delivery outcome | sent-routing-strategist |
| Handling inbound messages, opt-out keywords, consent state, the WhatsApp 24-hour window, or conversation history | sent-two-way-messaging |
| Executing the Sender Profile lifecycle over the API, including completion callbacks, campaigns, and user roles | sent-profile-provisioning |
| Replacing Twilio, Sinch, Infobip, Vonage, or Bird with Sent, including cutover and rollback planning | migrate-to-sent |
Within this group, note two frequent hand-offs: sender-profile-architect decides the tenancy boundary and sent-profile-provisioning implements it, while migrate-to-sent plans a provider replacement and sent-integration-starter hardens the resulting integration.
If the request matches one row cleanly, invoke that skill and stop. If it spans several rows, state the proposed order and begin with the prerequisite. For example, check sent-account-readiness before a live send, use sent-templates to locate an existing template before sent-messaging, and use messaging-performance-analyzer when the user provides an export rather than asking for live dashboard metrics.
Clarifying questions to ask before routing
Ask only what's needed to pick a lane. Stop as soon as the channel + workflow are unambiguous.
- Channel — SMS, WhatsApp, RCS, or unsure?
- Workflow stage — fresh setup, in the middle of integration, or debugging something that was working?
- Geography — US only, international, or both? (Matters for SMS — 10DLC / TCR is US-only.)
- Surface — live account operation, API/backend integration, dashboard UX, or compliance paperwork?
- Audience — are you an end-tenant of Sent, or are you building the multi-tenant Sent platform itself? (Sender Profile vs single-tenant onboarding.)
- Symptom (if debugging) — error code, rejection reason, low vetting score, or pure delivery-rate drop?
- Artifact in hand — do you have a contact, template or message ID, template draft, MDR export, RBM agent ID, or
config_id?
One question per turn is fine; never fire all seven at once.
When to handle without routing
This skill is not a fallback for general questions. If the user asks about:
- Balance, onboarding state, or whether the selected account can send — use
sent-account-readiness. - Contracts, plan pricing, invoices, or account access that the available operations cannot answer — direct them to Sent support or
https://docs.sent.dm. - Generic engineering such as retries, queueing, or observability with no Sent-specific work — answer normally; route to
sent-integration-starteronce the question involves Sent's own retry, idempotency, or rate-limit contract. - Meta, Google, TCR, or carrier policy outside a specialist skill's scope — use current upstream documentation.
If after the clarifying questions the request still doesn't fit any target skill, say so plainly. Don't force a route.
Shared terminology
Read references/sent-glossary.md when a routing decision depends on Sent, SMS, WhatsApp, RCS, or MCP terminology. Keep operational details in the target skill rather than duplicating them here.
FAQ
What does the sent skill do?
Routes broad or ambiguous Sent requests to the correct MCP-backed operation or specialist skill. Use when the user asks what Sent can do, says "help me with Sent" or "set up messaging," needs several Sent workflows, or has not made the channel, task, or desired operation clear enough to select a more specific skill.
How do I install sent?
Run npx skills add https://github.com/sentdm/sent-plugin --skill sent in your project. The skills CLI detects the agents you use and copies the skill into the right folder. For Claude Code you can also place the skill folder at ~/.claude/skills/sent/ (personal) or .claude/skills/sent/ (project).
Which AI agents can use sent?
Any agent that supports the open Agent Skills format (a folder with a SKILL.md file), including Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, Windsurf, Cline, OpenCode and more.
Is sent safe to install?
No partner security audit is available yet. Skills can run commands and scripts, so read the SKILL.md and any bundled files before installing.
Who maintains sent?
It is published by sentdm in sentdm/sent-plugin. It has 2,921 recorded installs.
More from sentdm/sent-plugin
waba-template-author
sentdm/sent-plugin
Writes, classifies, validates, and repairs WhatsApp templates using the Sent v3 template definition contract. Use for utility, marketing, authentication, OTP, Meta review, rejected templates, variables, buttons, channel overrides, or submission-ready Sent payloads.
waba-embedded-signup
sentdm/sent-plugin
Guides WhatsApp Business Account onboarding through Sent, separating dashboard Embedded Signup, organization WABA inheritance, and direct child-profile credentials. Use for WABA connection, Meta signup, profile creation, access-token handling, phone number mapping, completion callbacks, or WhatsApp onboarding failures.
messaging-performance-analyzer
sentdm/sent-plugin
Analyzes Sent message delivery, webhook, and activity data to explain funnel drop-offs, delivery failures, read-rate gaps, channel fallback, and suspicious performance changes. Use when a user says MDR, delivery report, message activity, webhook event, failed messages, low delivery rate, RCS fallback, WhatsApp read rate, SMS filtering, campaign performance, or asks why messages did not arrive.
rcs-agent-onboarding
sentdm/sent-plugin
Guides current Sent RCS and RBM onboarding, launch evidence, carrier approval, text and suggestion-chip templates, Sender Profile readiness, and safe routing. Use for RCS launch, fallback, pinned-channel tests, or broadcast prevention.
sms-10dlc-registration
sentdm/sent-plugin
Prepares and validates Sent US A2P 10DLC brand and campaign registration through Sender Profiles, including inheritance, all campaign use cases, opt-in evidence, sample-message policy, autoresponses, sandbox validation, TCR status, and rejection remediation.
template-builder-ui
sentdm/sent-plugin
Designs and audits tenant-facing Sent template builders, previews, validation, lifecycle UX, and API payload mapping. Use for template editor forms, variables, channel overrides, WhatsApp review, RCS suggestion chips, authentication templates, and safe submission flows.
Popular ai & agents skills
google-agents-cli-publish
google/agents-cli
This skill should be used when the user wants to "publish an agent", "publish my ADK agent", "register an agent with Gemini", "publish to Gemini" (formerly Gemini Enterprise), or needs guidance on the agents-cli publish gemini command. Also use when the user wants to "manage agents in Agent Registry", "list/update/delete registered agents", or "register an MCP server". Covers ADK vs A2A registration modes, programmatic and interactive usage, flag reference, auto-detection from deployment metadata, Agent Registry fleet management, and troubleshooting. Part of the agents-cli skills suite. Do NOT use for deployment (use google-agents-cli-deploy).
google-agents-cli-eval
google/agents-cli
This skill should be used when the user wants to "run an evaluation", "evaluate my agent", "evaluate my ADK agent", "write an eval dataset", "analyze eval failures", "compare eval results", "optimize agent", or needs guidance on the Gemini platform eval methodology and the Quality Flywheel. Covers eval metrics, dataset schema, LLM-as-judge scoring, and common failure causes. Applies to any agents-cli project, whatever framework the agent is written in. Do NOT use for agent API code patterns (ADK: use google-agents-cli-adk-code), deployment (use google-agents-cli-deploy), or project scaffolding (use google-agents-cli-scaffold).
skill-creator
anthropics/skills
Create new skills, modify and improve existing skills, and measure skill performance. Use when users want to create a skill from scratch, edit, or optimize an existing skill, run evals to test a skill, benchmark skill performance with variance analysis, or optimize a skill's description for better triggering accuracy.
codex-pet
prime-skills/runcomfy-agent-skills
Codex Pet generator on RunComfy. Build a Codex-compatible Codex Pet spritesheet.webp + pet.json from a single reference image, drop it into ${CODEXHOME:-$HOME/.codex}/pets/ / and Codex picks it up as a custom Codex Pet next to the 8 built-ins. This skill produces the exact Codex Pet atlas Codex expects (1536x1872 PNG/WebP, 8 cols x 9 rows, 192x208 cells, 9 animation states — idle, running-right, running-left, waving, jumping, failed, waiting, running, review). Calls OpenAI GPT Image 2 edit ONCE via the local RunComfy CLI as runcomfy run openai/gpt-image-2/edit to produce a canonical Codex Pet pose, then assembles all 9 animation rows programmatically with ImageMagick micro-transforms — no Codex Pro, no $imagegen, no OPENAIAPIKEY required, only RUNCOMFYTOKEN. Triggers on "codex pet", "create codex pet", "make codex pet", "hatch codex pet", "/hatch image", "desktop pet codex", "codex pets", "spritesheet.webp", or any explicit ask to build a custom pet for OpenAI Codex.
full-output-enforcement
leonxlnx/taste-skill
Overrides default LLM truncation behavior. Enforces complete code generation, bans placeholder patterns, and handles token-limit splits cleanly. Apply to any task requiring exhaustive, unabridged output.
executing-plans
obra/superpowers
Use when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is available