# AI use cases for Skills (sv-number/skills) Repo: [sv-number/skills](https://github.com/sv-number/skills) | Use cases: 3 | Page: https://dedupedai.com/use-cases/sv-number-skills/ A markdown agent skill that lets an AI agent order a temporary phone number over the SV Number API, read the SMS verification code, and close the activation. This file holds every use case of this repo. Each one starts with a "## " heading and ends with its URL. - Receive a signup SMS code on a number in a chosen country: https://dedupedai.com/use-cases/sv-number-skills/get-verification-code-for-signup/ - Count live country coverage before choosing a number: https://dedupedai.com/use-cases/sv-number-skills/check-country-coverage-before-ordering/ - Compute a TOTP code locally for an account's second factor: https://dedupedai.com/use-cases/sv-number-skills/complete-authenticator-second-factor/ ## How to receive a signup SMS code on a number in a chosen country with Skills Repo: [sv-number/skills](https://github.com/sv-number/skills) | Difficulty: Intermediate | Time: 15 minutes | Basis: From the README An agent orders a number in the country a service expects, reads the code, and closes the activation. **Who it is for:** A developer or agent operator whose automated signup is blocked by a 'we sent a code to your phone' step and who needs a number in a specific country. **The problem:** The agent has no phone number, and verification checks often reject numbers from the wrong country before any SMS is sent. **The outcome:** The agent holds a number in the requested country, receives the verification code through the API, and closes the activation so the charge stays or the money returns. ### Steps 1. Run `curl -O https://raw.githubusercontent.com/sv-number/skills/main/sv-number/SKILL.md` to download the skill file. 2. Run `export SVN_API_KEY=your_key_here` with your key from your SV Number profile. 3. Run `python sv-number/scripts/order_number.py` or `node sv-number/scripts/order_number.mjs` after the skill is in place. (inferred, check the README) 4. Let the script call getNumber, then poll getStatus every 3 to 5 seconds until it returns STATUS_OK with the code. 5. Confirm the script calls setStatus 6 after the code is used, or setStatus 8 if nothing arrived. ### Prompt to paste into your agent ```text Read the sv-number skill in the sv-number-skills repo and order a number for in . Expected output: a phone number, the verification code, and a confirmation that the activation was closed with setStatus 6 or 8. Verify that the activation status is no longer waiting before you report success. ``` ### Caveat The README says these numbers are not for banking, payment or government accounts and do not send SMS or take calls, so use them only for receiving codes. Risk, credentials: The SVN_API_KEY grants access to your balance, so keep it in the agent environment and do not paste it into prompts or logs. Dual-use notice: only use this on software, sites and systems you own or are authorized to test. Disclaimer: Third-party repos we don't own or vouch for. AI-generated use cases can be wrong: review everything and run at your own risk. Full text: https://dedupedai.com/disclaimer/ URL: https://dedupedai.com/use-cases/sv-number-skills/get-verification-code-for-signup/ ## How to count live country coverage before choosing a number with Skills Repo: [sv-number/skills](https://github.com/sv-number/skills) | Difficulty: Intermediate | Time: 15 minutes | Basis: From the README An agent lists available countries and per-service pool data to pick a country that is likely to deliver codes. **Who it is for:** An operator who wants to confirm the catalogue covers a target country before committing an agent to a signup flow. **The problem:** Choosing a country with no working pool wastes time and money, and the README's coverage claim is one the user should be able to check. **The outcome:** The user gets a country count from the live catalogue and can see per-service and per-country pool data before ordering. ### Steps 1. Run `export SVN_API_KEY=your_key_here` if the key is not already set. 2. Run `curl -s "https://sms-verification-number.com/stubs/handler_api?api_key=$SVN_API_KEY&action=getCountryAndOperators&lang=en" | jq length` to count the countries returned. (inferred, check the README) 3. Read the catalogue response for the share of codes delivered to other users and the count of live numbers per service and country, where the README says these are measured. 4. Pick the country where the pool data shows live numbers and a delivery share that fits the service you need. ### Prompt to paste into your agent ```text Using the sv-number skill from the sv-number-skills repo, fetch the country catalogue and tell me how many countries it lists and which ones have live numbers for . Expected output: a country count and a short list. Verify that the count matches the jq length output before you recommend a country. ``` ### Caveat The README says the delivery share is shown only where it is measured, so for other pairs you have only the size of the live pool to judge by. Dual-use notice: only use this on software, sites and systems you own or are authorized to test. Disclaimer: Third-party repos we don't own or vouch for. AI-generated use cases can be wrong: review everything and run at your own risk. Full text: https://dedupedai.com/disclaimer/ URL: https://dedupedai.com/use-cases/sv-number-skills/check-country-coverage-before-ordering/ ## How to compute a TOTP code locally for an account's second factor with Skills Repo: [sv-number/skills](https://github.com/sv-number/skills) | Difficulty: Advanced | Time: 30 minutes | Basis: From the README An agent stores a TOTP secret beside its API key and computes six-digit codes on the machine per RFC 6238. **Who it is for:** An operator whose agent-run account asks for an authenticator app code after the phone step and who wants the agent to finish that step without a human. **The problem:** After the SMS code, many accounts ask for a time-based one-time password that the agent cannot produce from a phone number alone. **The outcome:** The agent computes the current six-digit TOTP code on the local machine and enters it, so the secret never leaves the machine. ### Steps 1. Store the TOTP secret for the account in the agent environment next to SVN_API_KEY, not in the repo. 2. Use a local RFC 6238 TOTP library or script to compute the six-digit code from the stored secret. (inferred, check the README) 3. Enter the computed code within its validity window when the account asks for the authenticator step. 4. Confirm the account accepts the code and record that the secret stayed on the machine. ### Prompt to paste into your agent ```text Using the sv-number skill from the sv-number-skills repo, store the TOTP secret for in the local environment and compute the current six-digit code per RFC 6238. Expected output: a six-digit code accepted by the account. Verify that the secret was not sent to any remote service before you report the code. ``` ### Caveat The README describes the TOTP step as part of this skill but does not show the code or library for it, so the exact implementation is left to you. Risk, credentials: A TOTP secret is equivalent to the second factor itself, so anyone who reads it can log into the account; store it with the same care as a password. Dual-use notice: only use this on software, sites and systems you own or are authorized to test. Disclaimer: Third-party repos we don't own or vouch for. AI-generated use cases can be wrong: review everything and run at your own risk. Full text: https://dedupedai.com/disclaimer/ URL: https://dedupedai.com/use-cases/sv-number-skills/complete-authenticator-second-factor/