How do I install the Ton Manage Wallets skill?

Run npx skillmds@latest add ton-org/ton-manage-wallets in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Ton Manage Wallets safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Ton Manage Wallets?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Ton Manage Wallets free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Ton Manage Wallets?

ton-org (@ton-org) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Ton Manage Wallets by ton-org — Agent Skill

Name: Ton Manage Wallets
Author: ton-org

File contents

TON Wallet Management

Manage the local wallet registry and perform advanced agentic wallet operations including import and key rotation.

MCP Tools

Wallet Registry

Tool	Required	Optional
`list_wallets`	—	—
`get_current_wallet`	—	—
`set_active_wallet`	`walletSelector`	—
`remove_wallet`	`walletSelector`	—

Agentic Wallet Management

Tool	Required	Optional
`agentic_validate_wallet`	`address`	`network`, `ownerAddress`, `collectionAddress`
`agentic_list_wallets_by_owner`	`ownerAddress`	`network`
`agentic_import_wallet`	`address`	`name`
`agentic_rotate_operator_key`	`walletSelector`	—
`agentic_complete_rotate_operator_key`	`rotationId`	—

Workflows

Switch Active Wallet

Call list_wallets to see all stored wallets
Call set_active_wallet with a walletSelector (id, name, or address)
Confirm with get_current_wallet

Import Existing Agentic Wallet

Call agentic_validate_wallet to verify the wallet address and contract
Call agentic_import_wallet to add it to the registry
If the agent needs to sign transactions and no operator key is available, call agentic_rotate_operator_key and then agentic_complete_rotate_operator_key after the user applies the key change on-chain via the dashboard

Rotate Operator Key

Call agentic_rotate_operator_key — generates a new key pair and returns a dashboard URL for the user to apply the change on-chain
If local browser or shell tools are available, open the dashboard URL yourself; only send the raw link when automatic opening is unavailable or fails
Ask the user only to approve the on-chain key change in their wallet; do not require them to re-paste the URL or type a fixed confirmation phrase
Call agentic_complete_rotate_operator_key with the rotationId; if the chain state has not updated yet, wait briefly and retry instead of forcing extra user input

Notes

walletSelector accepts wallet id, name, or address
For one-off queries, pass walletSelector directly to wallet-scoped tools instead of changing the active wallet
Use available shell/browser tools to open dashboard URLs for the user whenever possible
For confirmations and small option sets, prefer the host client's structured confirmation/choice UI when available; otherwise use a short natural-language yes/no prompt and never require an exact magic word
Registry data is stored in ~/.config/ton/config.json (or TON_CONFIG_PATH)
Read tools work with imported agentic wallets that don't yet have an operator_private_key; write tools require it
Management tool responses never expose private keys, mnemonics, or API keys
To create a brand new agentic wallet, use the ton-create-wallet skill instead

---name: ton-manage-walletsdescription: Manage multiple TON wallets, import agentic wallets and rotate operator keys. Use when the user wants to switch wallets, list wallets, import an existing wallet, rotate an operator key, or manage their wallet registry.---# TON Wallet ManagementManage the local wallet registry and perform advanced agentic wallet operations including import and key rotation.## MCP Tools### Wallet Registry| Tool | Required | Optional || ---- | -------- | -------- || `list_wallets` | — | — || `get_current_wallet` | — | — || `set_active_wallet` | `walletSelector` | — || `remove_wallet` | `walletSelector` | — |### Agentic Wallet Management| Tool | Required | Optional || ---- | -------- | -------- || `agentic_validate_wallet` | `address` | `network`, `ownerAddress`, `collectionAddress` || `agentic_list_wallets_by_owner` | `ownerAddress` | `network` || `agentic_import_wallet` | `address` | `name` || `agentic_rotate_operator_key` | `walletSelector` | — || `agentic_complete_rotate_operator_key` | `rotationId` | — |## Workflows### Switch Active Wallet1. Call `list_wallets` to see all stored wallets2. Call `set_active_wallet` with a `walletSelector` (id, name, or address)3. Confirm with `get_current_wallet`### Import Existing Agentic Wallet1. Call `agentic_validate_wallet` to verify the wallet address and contract2. Call `agentic_import_wallet` to add it to the registry3. If the agent needs to sign transactions and no operator key is available, call `agentic_rotate_operator_key` and then `agentic_complete_rotate_operator_key` after the user applies the key change on-chain via the dashboard### Rotate Operator Key1. Call `agentic_rotate_operator_key` — generates a new key pair and returns a dashboard URL for the user to apply the change on-chain2. If local browser or shell tools are available, open the dashboard URL yourself; only send the raw link when automatic opening is unavailable or fails3. Ask the user only to approve the on-chain key change in their wallet; do not require them to re-paste the URL or type a fixed confirmation phrase4. Call `agentic_complete_rotate_operator_key` with the `rotationId`; if the chain state has not updated yet, wait briefly and retry instead of forcing extra user input## Notes- `walletSelector` accepts wallet id, name, or address- For one-off queries, pass `walletSelector` directly to wallet-scoped tools instead of changing the active wallet- Use available shell/browser tools to open dashboard URLs for the user whenever possible- For confirmations and small option sets, prefer the host client's structured confirmation/choice UI when available; otherwise use a short natural-language yes/no prompt and never require an exact magic word- Registry data is stored in `~/.config/ton/config.json` (or `TON_CONFIG_PATH`)- Read tools work with imported agentic wallets that don't yet have an `operator_private_key`; write tools require it- Management tool responses never expose private keys, mnemonics, or API keys- To create a brand new agentic wallet, use the `ton-create-wallet` skill instead

Frequently asked questions

Ton Manage Wallets