TeddyMobile Vox Phone Notification
Paste the following prompt into your AI chat to install this skill:
Please install the @user_caf52609/teddymobile-vox-phone-notification skill into your AI assistant by following the guide at https://skillhub.cn/install/skillhub.md.
About this skill
The problem
In AI-agent workflows, phone notifications often require confirming “who to call” and “what to say” before placing a real call. Wiring directly into a voice platform introduces credential management, number compliance, and mis-dial risk; pure text simulation does not validate the actual outbound call path. This skill separates those stages: first verify the parsed request locally, then move to trial or live calling only after explicit user choices.
How it works
- Dry-run by default: it does not load credentials or place a call. It validates the destination phone number and notification content, and prompts for missing fields.
- Trial outbound calls: after a successful dry-run, up to 10 no-credential trial calls can be run. The flow requires reviewing the preview, confirming authorization to contact the number, and explicitly using
--confirm-real-call. Trial text is limited to 100 characters and local content safety checks apply. - Live setup: ongoing use requires TeddyMobile registration and configuration of
VOX_APP_ID,VOX_SECRET,VOX_BOT_ID, andVOX_OUTBOUND_NUMBER. Credentials can be provided through environment variables or~/.teddymobile/credentials.json, and should not be pasted into chat, logs, or tickets.
It works well as a controlled pre-call stage for voice-notification agents: mask and preview first, then make confirmed outbound calls, and finally connect to the production platform.
Limits
Both --trial and --live place real phone calls and transmit the phone number and message text to the platform, so they must run only after explicit confirmation. Formal use depends on a TeddyMobile account, a notification bot, and an outbound number. VOX_CALLBACK_URL is optional and only used for callback-driven flows. If platform approval, content safety checks, or local trial limits block the call, resolve registration or retry boundaries first instead of falling back to unconfirmed outbound calls.
Use Cases
- In a Claw workflow, parse a natural-language phone-notification request into a number and spoken message with a masked dry-run preview.
- After dry-run review, run up to 10 no-credential trial calls once the recipient confirms they can be called.
- After TeddyMobile onboarding, configure APPID, SecretID, BotID, and outbound number to run live notifications.
- Connect outbound-call requestId or task variables to later agent steps using the optional callback flow.
Best For
- Agent integration engineers who need to parse a phone-notification request and preview the number and message before any real call.
- Backend developers wiring TeddyMobile voice services who need to manage APPID, SecretID, BotID, and outbound number as local credentials.
- Workflow product engineers who want a staged user path: dry-run, limited trial, then formal live setup.
- Compliance-minded engineers who need to avoid pasting live secrets into chat or logs and keep trial usage bounded.
Related Skills
Turn vague requests into structured prompts with role, task, context, and constraints, outputting only usable prompts without executing the task.
A skill for game NPC and enemy AI that separates decision, steering, and pathfinding, covering FSMs, behavior trees, A*, path caching, and pitfalls.
Provides multi-turn emotional companion chat through a third-party Agent API and supports continuing sessions via session_id.
An evaluation-driven workflow for diagnosing, optimizing, validating, and logging Agent Skills based on design patterns and anti-patterns.