transfer

Transfer STX, SIP-010 tokens, and SIP-009 NFTs via a single CLI.

9|43|Updated Feb 19, 2026
One-click install
npx skills add https://github.com/aibtcdev/skills --skill transfer-aibtcdev
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: transfer
Source: https://github.com/aibtcdev/skills/tree/main/transfer
Command: npx skills add https://github.com/aibtcdev/skills --skill transfer-aibtcdev

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires commander.

What problem does it solve?

Consolidates three transfer workflows—STX, SIP-010 fungible tokens, and SIP-009 NFTs—into a single, easy-to-use command-line experience, requiring only an unlocked wallet to execute transfers.

Core Features & Use Cases

  • Unified transfers: send native STX, fungible tokens, or NFTs from one CLI tool.
  • Subcommands: stx, token, nft, each performing signing, validation, and broadcast of transactions.
  • Safe-guarded operations: input validation for amounts, token IDs, and ownership status, plus fee handling and error reporting.
  • Output: returns a consistent JSON payload with txid, sender, recipient, asset details, network, and explorer URL for tracking.

Quick Start

Run bun run transfer/transfer.ts stx --recipient <address> --amount <microStx> to send STX, or use token or nft subcommands to transfer fungible tokens or NFTs.

Frequently Asked Questions about transfer

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I transfer STX, SIP-010 tokens, and SIP-009 NFTs on Stacks from one CLI?

You can transfer STX, SIP-010 tokens, and SIP-009 NFTs on Stacks using a unified CLI that supports stx, token, and nft subcommands. It requires an unlocked wallet to sign, validate, and broadcast transactions across all asset types.

Can I send Stacks NFTs and fungible tokens using the same command-line tool?

Yes, you can send Stacks NFTs and fungible tokens using the same command-line tool. It provides dedicated token and nft subcommands that handle signing, input validation for amounts and token IDs, and transaction broadcasting.

What do I need to broadcast Stacks token transfers from the command line?

To broadcast Stacks token transfers from the command line, you need an unlocked wallet and the recipient address, amount, or token ID. The CLI handles fee handling, ownership validation, and returns a JSON payload with the txid and explorer URL.

Does the Stacks CLI transfer tool support transaction memos and fee handling?

Yes, the Stacks CLI transfer tool supports optional memos and fee handling for transactions. It validates inputs and reports errors during the signing and broadcasting process to ensure safe-guarded operations.

What output format does the Stacks CLI return after a successful asset transfer?

The Stacks CLI returns a consistent JSON payload after a successful asset transfer. This output includes the txid, sender, recipient, asset details, network information, and an explorer URL for tracking the transaction.

Why does my Stacks token transfer fail during command-line execution?

Your Stacks token transfer may fail during command-line execution due to invalid input amounts, incorrect token IDs, or failed ownership status validation. The CLI performs input validation and provides error reporting to identify the issue.