AutoGineer summary
Written by AutoGineer from the skill’s own files, not by the author
This skill provides a structured approach to using the AWS End User Messaging SMS and Voice (pinpoint-sms-voice-v2) API. It guides users through the rapid setup of RCS Business Messaging test agents and Notify OTP configurations, as well as the more complex lifecycle of production registration for various messaging identities. It emphasizes using the AWS MCP server for secure, audited execution and provides clear paths for both testing and moving to production-grade messaging.
What it does
- Creates branded RCS test agents with rich cards and suggested replies.
- Configures Notify for OTP delivery using AWS-managed templates.
- Discovers registration requirements for specific countries and identity types.
- Executes the full registration lifecycle including submission and denial recovery.
- Provides procedures for exiting the SMS sandbox and upgrading to production tiers.
- Offers guidance on least-privilege IAM policies and security best practices.
When to use it
- When you need to send rich, branded RCS messages to test devices.
- When you require a fast, production-ready OTP verification solution.
- When you need to determine registration requirements for international messaging.
- When you are ready to move messaging identities from sandbox to production.
- When you need to manage the registration lifecycle for 10DLC, toll-free, or short codes.
Advantages
- Enables rapid prototyping with no phone number purchase required.
- Provides a unified engine for diverse registration types.
- Includes built-in failure mode analysis and cleanup procedures.
- Promotes secure practices through least-privilege IAM and audit logging.
- Supports both CLI and MCP-based execution for flexibility.
Usage examples
- “Help me set up an RCS test agent to send a branded message.”
- The agent will guide you through creating an RCS agent, adding a verified test device, and sending your first rich message using the pinpoint-sms-voice-v2 API.
- “How do I send an OTP code using AWS Notify?”
- The agent will assist in creating a Notify configuration, selecting an approved template, and sending a verification code to your specified phone number.
- “What are the registration requirements for sending SMS in France?”
- The agent will query live API definitions to identify the specific registration type and field requirements for the target country.
- “I need to move my SMS identity out of the sandbox.”
- The agent will walk you through the production go-to-production guide, including checking account attributes and managing spend limits.
Install
Download the skill as a ZIP:
https://autogineer.com/agent-skills/aws/aws-sms-voice/downloadUnzip it into the cross-client skills folder of your project:
mkdir -p .agents/skills && unzip aws-sms-voice.zip -d .agents/skills
Documentation by AWS
AWS End User Messaging — SMS, Voice, RCS & Notify
Overview
AWS End User Messaging SMS and Voice (the pinpoint-sms-voice-v2 API) is the
control and data plane for SMS, Voice, RCS Business Messaging, and Notify (OTP).
This skill covers the two fastest onboarding paths — each reaches
a real message on a real phone in about five minutes, with no phone-number
purchase and no carrier registration:
Create an RCS test agent and send your first branded message — a branded RCS Business Messaging agent, a verified test device, and a rich outbound + inbound message. See references/hello-rcs-test-agent.md.
Send an OTP with Notify — a one-time-passcode text through AWS-managed sending identities and pre-approved templates. See references/hello-notify-otp.md.
Beyond onboarding, this skill takes an identity to production registration in three steps:
Find which registration a country requires — discover the registration type and its live field set for a target country and identity type, reconciled with the official docs. See references/registration-requirements-by-country.md.
Run the registration lifecycle — the universal engine (create, derive fields, fill, submit, poll, recover from denial, resubmit) shared by every registration type, including RCS country launch. See references/registration-core-engine.md.
Take an identity to production — exit the SMS sandbox, launch RCS in a country with carrier monitoring and SMS fallback, upgrade Notify to Advanced, and apply production hygiene (keywords, configuration sets, protect configurations). See references/customer-go-to-production-guide.md.
Guardrail — where this skill's files live (MCP vs local install)
This skill can be loaded two ways, and the references/ files resolve differently:
Loaded through the AWS MCP
retrieve_skilltool. Reference files do not exist on the local filesystem. Fetch them viaretrieve_skillwith thefileparameter (e.g.,file="references/hello-rcs-test-agent.md"). Do NOTfile_readthese paths locally — they are not there.Installed locally (e.g.,
.kiro/skills/aws-sms-voice/). Read references from the local skill directory using the relative paths shown in this file.
This applies only to the skill's own packaged files. User-created artifacts (brand-assets/, temp files) are always in the user's working directory.
Execute commands using available tools from the AWS MCP server when connected — it provides sandboxed execution, audit logging, and observability. When the MCP server is not available, fall back to the AWS CLI or shell as needed.
Choosing a path
| You want to… | Go to |
|---|---|
| Send rich, branded messages (cards, logo, two-way) to your own test phone | hello-rcs-test-agent.md |
| Send a verification code / OTP to any supported phone, fastest possible path | hello-notify-otp.md |
| Find out which registration a country needs and what fields it requires | registration-requirements-by-country.md |
| Create and submit a registration of any type (10DLC, toll-free, sender ID, RCS launch, Notify tier) | registration-core-engine.md |
| Take an identity to production (sandbox exit, RCS carrier launch + fallback, Notify Advanced, hygiene) | customer-go-to-production-guide.md |
RCS test agents deliver only to verified test devices and require a short brand registration (auto-reviewed in minutes). Notify sends to any recipient in its supported countries immediately, but is limited to AWS-managed OTP templates. Pick RCS to explore rich messaging; pick Notify for the shortest path to a production-grade verification text.
Before you start (both paths)
The AWS MCP server is recommended for the best experience here — it runs the many
pinpoint-sms-voice-v2 and sts calls with sandboxed execution, audit logging, and
observability. It is not a hard requirement: every step also works with the plain AWS CLI or the
AWS Agent Toolkit when the MCP server is not available.
Credentials. Run
aws sts get-caller-identity --region <REGION>(pass--regionto use the regional STS endpoint; the globalsts.amazonaws.comendpoint is legacy). If it fails, configure the user's auth (named profile / SSO / access keys —--profile <PROFILE>on every command if a profile is in play) and prefer an assumed IAM role with ephemeral credentials. Each reference file's Prerequisites carry the full auth, CloudTrail-audit, and CLI-freshness steps.Least-privilege access. These tasks need a small set of specific
sms-voice:actions in the target account (the reference files enumerate the read/write actions each step uses — for examplesms-voice:DescribeRcsAgents,CreateRcsAgent,CreateRegistration,CreateNotifyConfiguration, andSendNotifyTextMessage). Scope the policy to exactly the actions the chosen path uses; do not grantsms-voice:*or*FullAccess.Don't trust the CLI version. Treat any
Invalid choice '<operation>'on apinpoint-sms-voice-v2command, at any step, as a stale/partial local service model (not a permissions or account problem). The RCS and Notify reference files (prerequisite 3) carry the full reactive resolution: clear a stale~/.aws/models/pinpoint-sms-voice-v2/override, else upgrade the AWS CLI, with a boto3 fallback.AccessDeniedExceptionmeans the identity is missing the requiredsms-voice:permissions.
Each reference file is self-contained: it tracks the IDs you collect as session state, audits required inputs against the service before any submit, and ends with a Failure modes table and a Cleanup section. Follow the file for the path the user chose rather than improvising the API sequence — several steps fail silently or depend on service-version-specific field sets that must be read live.
Security Considerations
Least-privilege IAM. Scope policies to specific
sms-voice:actions; never use*FullAccessorsms-voice:*in production. The reference files enumerate the minimal read/write actions each onboarding path needs.Ephemeral credentials. Assume an IAM role with ephemeral credentials; never embed long-lived access keys in code, config, or environment variables.
No secrets in messages or fields. OTP codes and message bodies can surface in CloudTrail and downstream logs — treat them as sensitive and never hardcode real codes. Enable CloudTrail logging for
sms-voiceAPI calls and encrypt CloudTrail logs and CloudWatch Log groups with a KMS CMK. Attach a configuration set with an event destination (CloudWatch Logs or Kinesis) for delivery monitoring before production traffic. Create CloudWatch alarms on key security signals (repeatedAccessDeniedException, unusual send volumes, spend limit approaching threshold) for proactive alerting. Registration contact fields (email, phone, URLs) are submitted to partner review; use real but non-sensitive business contacts.Consent and opt-out. Only message recipients who have opted in. Honor STOP / opt-out state; the RCS path shows how to check the opt-out list before sending. Test agents intentionally restrict delivery to verified test devices — do not work around that to reach unconsented numbers.
Spend limits and abuse. Default account spend limits are intentionally low; raise them deliberately and monitor. Notify enforces a non-adjustable per-day cap per destination — do not attempt to bypass it.
Destructive cleanup. The teardown steps delete agents, registrations, and configurations. They are irreversible — confirm with the user before running cleanup, and note RCS agents have deletion protection enabled by default in the onboarding flow.
Additional Resources
Files
- ATTRIBUTION.mdAdded by AutoGineer929 B
- LICENSELicence file added by AutoGineer9.9 KiB
- NOTICELicence file added by AutoGineer67 B
- SKILL.md9.7 KiB
- references/customer-go-to-production-guide.md17.4 KiB
- references/hello-notify-otp.md12.1 KiB
- references/hello-rcs-test-agent.md38.5 KiB
- references/registration-core-engine.md17.1 KiB
- references/registration-requirements-by-country.md11.5 KiB
SKILL.md
AWS End User Messaging — SMS, Voice, RCS & Notify
Overview
AWS End User Messaging SMS and Voice (the pinpoint-sms-voice-v2 API) is the
control and data plane for SMS, Voice, RCS Business Messaging, and Notify (OTP).
This skill covers the two fastest onboarding paths — each reaches
a real message on a real phone in about five minutes, with no phone-number
purchase and no carrier registration:
Create an RCS test agent and send your first branded message — a branded RCS Business Messaging agent, a verified test device, and a rich outbound + inbound message. See references/hello-rcs-test-agent.md.
Send an OTP with Notify — a one-time-passcode text through AWS-managed sending identities and pre-approved templates. See references/hello-notify-otp.md.
Beyond onboarding, this skill takes an identity to production registration in three steps:
Find which registration a country requires — discover the registration type and its live field set for a target country and identity type, reconciled with the official docs. See references/registration-requirements-by-country.md.
Run the registration lifecycle — the universal engine (create, derive fields, fill, submit, poll, recover from denial, resubmit) shared by every registration type, including RCS country launch. See references/registration-core-engine.md.
Take an identity to production — exit the SMS sandbox, launch RCS in a country with carrier monitoring and SMS fallback, upgrade Notify to Advanced, and apply production hygiene (keywords, configuration sets, protect configurations). See references/customer-go-to-production-guide.md.
Guardrail — where this skill's files live (MCP vs local install)
This skill can be loaded two ways, and the references/ files resolve differently:
Loaded through the AWS MCP
retrieve_skilltool. Reference files do not exist on the local filesystem. Fetch them viaretrieve_skillwith thefileparameter (e.g.,file="references/hello-rcs-test-agent.md"). Do NOTfile_readthese paths locally — they are not there.Installed locally (e.g.,
.kiro/skills/aws-sms-voice/). Read references from the local skill directory using the relative paths shown in this file.
This applies only to the skill's own packaged files. User-created artifacts (brand-assets/, temp files) are always in the user's working directory.
Execute commands using available tools from the AWS MCP server when connected — it provides sandboxed execution, audit logging, and observability. When the MCP server is not available, fall back to the AWS CLI or shell as needed.
Choosing a path
| You want to… | Go to |
|---|---|
| Send rich, branded messages (cards, logo, two-way) to your own test phone | hello-rcs-test-agent.md |
| Send a verification code / OTP to any supported phone, fastest possible path | hello-notify-otp.md |
| Find out which registration a country needs and what fields it requires | registration-requirements-by-country.md |
| Create and submit a registration of any type (10DLC, toll-free, sender ID, RCS launch, Notify tier) | registration-core-engine.md |
| Take an identity to production (sandbox exit, RCS carrier launch + fallback, Notify Advanced, hygiene) | customer-go-to-production-guide.md |
RCS test agents deliver only to verified test devices and require a short brand registration (auto-reviewed in minutes). Notify sends to any recipient in its supported countries immediately, but is limited to AWS-managed OTP templates. Pick RCS to explore rich messaging; pick Notify for the shortest path to a production-grade verification text.
Before you start (both paths)
The AWS MCP server is recommended for the best experience here — it runs the many
pinpoint-sms-voice-v2 and sts calls with sandboxed execution, audit logging, and
observability. It is not a hard requirement: every step also works with the plain AWS CLI or the
AWS Agent Toolkit when the MCP server is not available.
Credentials. Run
aws sts get-caller-identity --region <REGION>(pass--regionto use the regional STS endpoint; the globalsts.amazonaws.comendpoint is legacy). If it fails, configure the user's auth (named profile / SSO / access keys —--profile <PROFILE>on every command if a profile is in play) and prefer an assumed IAM role with ephemeral credentials. Each reference file's Prerequisites carry the full auth, CloudTrail-audit, and CLI-freshness steps.Least-privilege access. These tasks need a small set of specific
sms-voice:actions in the target account (the reference files enumerate the read/write actions each step uses — for examplesms-voice:DescribeRcsAgents,CreateRcsAgent,CreateRegistration,CreateNotifyConfiguration, andSendNotifyTextMessage). Scope the policy to exactly the actions the chosen path uses; do not grantsms-voice:*or*FullAccess.Don't trust the CLI version. Treat any
Invalid choice '<operation>'on apinpoint-sms-voice-v2command, at any step, as a stale/partial local service model (not a permissions or account problem). The RCS and Notify reference files (prerequisite 3) carry the full reactive resolution: clear a stale~/.aws/models/pinpoint-sms-voice-v2/override, else upgrade the AWS CLI, with a boto3 fallback.AccessDeniedExceptionmeans the identity is missing the requiredsms-voice:permissions.
Each reference file is self-contained: it tracks the IDs you collect as session state, audits required inputs against the service before any submit, and ends with a Failure modes table and a Cleanup section. Follow the file for the path the user chose rather than improvising the API sequence — several steps fail silently or depend on service-version-specific field sets that must be read live.
Security Considerations
Least-privilege IAM. Scope policies to specific
sms-voice:actions; never use*FullAccessorsms-voice:*in production. The reference files enumerate the minimal read/write actions each onboarding path needs.Ephemeral credentials. Assume an IAM role with ephemeral credentials; never embed long-lived access keys in code, config, or environment variables.
No secrets in messages or fields. OTP codes and message bodies can surface in CloudTrail and downstream logs — treat them as sensitive and never hardcode real codes. Enable CloudTrail logging for
sms-voiceAPI calls and encrypt CloudTrail logs and CloudWatch Log groups with a KMS CMK. Attach a configuration set with an event destination (CloudWatch Logs or Kinesis) for delivery monitoring before production traffic. Create CloudWatch alarms on key security signals (repeatedAccessDeniedException, unusual send volumes, spend limit approaching threshold) for proactive alerting. Registration contact fields (email, phone, URLs) are submitted to partner review; use real but non-sensitive business contacts.Consent and opt-out. Only message recipients who have opted in. Honor STOP / opt-out state; the RCS path shows how to check the opt-out list before sending. Test agents intentionally restrict delivery to verified test devices — do not work around that to reach unconsented numbers.
Spend limits and abuse. Default account spend limits are intentionally low; raise them deliberately and monitor. Notify enforces a non-adjustable per-day cap per destination — do not attempt to bypass it.
Destructive cleanup. The teardown steps delete agents, registrations, and configurations. They are irreversible — confirm with the user before running cleanup, and note RCS agents have deletion protection enabled by default in the onboarding flow.
Additional Resources
Requirements and compatibility
Works with: Claude Code, Claude apps, OpenAI Codex, GitHub Copilot, Cursor, Gemini CLI, Kiro, OpenCode, Goose, Amp, Roo Code, JetBrains Junie, Factory Droid, Devin (ex-Windsurf), Mistral Vibe, OpenHands, Letta
“Works with” means the tool reads the open Agent Skills format; a skill written for one tool may use features others lack.
Needs: Needs an MCP server
Security
What our scanner noticed· Low risk
- Instructions that use the network
A static scan is not a guarantee. Skills are third-party content: review a skill before you let an agent use it.
Attribution and licence
- Published by
- AWS
- Publisher
- AWS (Official)
- Source
- aws/agent-toolkit-for-aws · skills/specialized-skills/customer-communications-skills/aws-sms-voice · commit 0a218f8
- Licence
- Apache License 2.0 (redistribution allowed)
- LICENSE (added by AutoGineer from LICENSE)
- NOTICE (added by AutoGineer from NOTICE)
- ATTRIBUTION.md (written by AutoGineer)
- Synced
AutoGineer is not affiliated with or endorsed by AWS or AWS.
Related skills
Modal
K-Dense· Community
A serverless cloud platform for deploying and scaling Python applications, AI models, and GPU-accelerated workloads.
Cloud and DevOpsClaude CodeClaude appsOpenAI Codex+14 moreApache-2.0Low riskGitHub stars of the source repository56.4k
Cloud Infrastructure Network Engineer
Seth Hobson· Community
An expert network engineer persona specializing in cloud architecture, security, and performance optimization.
Cloud and DevOpsClaude CodeMITGitHub stars of the source repository42.3k
Deployment Validation Cloud Architect
Seth Hobson· Community
Expert cloud architect for multi-cloud infrastructure, cost optimization, and resilient system design.
Cloud and DevOpsClaude CodeMITGitHub stars of the source repository42.3k
Airflow Dag Patterns
Seth Hobson· Community
Best practices and design patterns for building and maintaining production-ready Apache Airflow DAGs.
Cloud and DevOpsClaude CodeClaude appsOpenAI Codex+14 moreMITGitHub stars of the source repository42.3k
Cost Optimization
Seth Hobson· Community
A comprehensive framework for reducing cloud infrastructure costs across AWS, Azure, GCP, and OCI.
Cloud and DevOpsClaude CodeClaude appsOpenAI Codex+14 moreMITGitHub stars of the source repository42.3k
Hybrid Cloud Networking
Seth Hobson· Community
A guide to configuring secure, high-performance network connectivity between on-premises infrastructure and major cloud providers.
Cloud and DevOpsClaude CodeClaude appsOpenAI Codex+14 moreMITGitHub stars of the source repository42.3k
Download ZIP
The ZIP holds the skill’s files, its licence files and an ATTRIBUTION.md. Download aws-sms-voice.zip