send
Skill2 starsChanged 8 months agoMITView on GitHub
Send STRK, ETH, or any ERC-20 token to a Starknet address. Supports simulation (dry-run) before execution. Use this skill when the user wants to send, transfer, pay, tip, or move tokens to another wallet address on Starknet. Also trigger when the user mentions sending funds to someone, making a payment, transferring assets, or moving crypto to a specific address — even if they just say "pay 10 STRK to 0x...".
4 other projects use a version of this.
Adopted by
Most recently taken up by
- stakeme-team/arc-agent-kittheir own version, first seen Nov 8, 2026
- synaptiai/agent-capability-standardtheir own version, first seen Nov 1, 2026
- jorranMLGN/phone-droptheir own version, first seen Oct 20, 2026
- jaimsh/meta-whatsapptheir own version, first seen Apr 8, 2026
Other versions4 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 4
- synaptiai/agent-capability-standard★ 6same name
- jorranMLGN/phone-drop★ 2same name
- jaimsh/meta-whatsapp★ 0same name
- stakeme-team/arc-agent-kit★ 0same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository13 other files it gives its agents.
- authenticate-walletSkill
- balanceSkill
- batchSkill
- confidentialSkill
- configSkill
- dcaSkill
- lendingSkill
- lstSkill
- multi-swapSkill
- portfolioSkill
- stakingSkill
- tradeSkill
- trovesSkill
The file
We split this skill into the rules it gives an agent
7 rules. 0 are common, 1 is distinctive, and 6 are very specific to this project.
0
Common
Most of the 4 edited versions we read keep these.
1
Distinctive
This author's own choices. Worth a look.
6
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 29
BEFORE any send, you MUST run npx starkfi@latest status and npx starkfi@latest balance to verify connectivity and funds.
- Distinctive: line 30
If the recipient address was NOT previously mentioned in the conversation, you MUST ask for explicit confirmation: _"Sending [amount] …
- Very specific: line 32
AFTER a successful send, you MUST verify the transaction using npx starkfi@latest tx-status <hash>.
- Very specific: line 80
Use balance to verify funds before sending.
- Very specific: line 81
Use config to set a custom RPC if experiencing rate limits.
- Very specific: line 82
Use trade if the user needs to swap tokens before sending.
- Very specific: line 83
Use confidential for privacy-preserving transfers (hidden amounts, ZK proofs).
“Common” is measured: kept by at least 6 in 10 of the 4 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Send Transaction
Transfer STRK, ETH, or ERC-20 tokens to a destination Starknet address. The CLI automatically checks balance before sending and validates the recipient address. Supports simulation (dry-run) mode to estimate fees without broadcasting.
Prerequisites
- Active session required.
- Sufficient balance for the transfer amount + gas fees.
Rules
- BEFORE any send, you MUST run
npx starkfi@latest statusandnpx starkfi@latest balanceto verify connectivity and funds. - If the recipient address was NOT previously mentioned in the conversation, you MUST ask for explicit confirmation: "Sending [amount] [token] to [address]. Confirm?"
- Suggest using
--simulatefirst for large amounts so the user can review the estimated fee before committing. - AFTER a successful send, you MUST verify the transaction using
npx starkfi@latest tx-status <hash>. - Starknet addresses start with
0xand can be up to 66 characters long (including the0xprefix).
Commands
npx starkfi@latest send <amount> <token> <recipient> [--simulate] [--json]Parameters
| Parameter | Type | Description | Required |
amount | number | Amount to send (e.g. 10, 0.5) | Yes |
token | string | Token symbol (e.g. STRK, ETH, USDC) | Yes |
recipient | string | Destination Starknet address (0x...) | Yes |
--simulate | flag | Estimate fees without broadcasting | No |
--json | flag | Output as JSON | No |
Examples
User: "Send 10 STRK to 0x04a3..."
npx starkfi@latest status
npx starkfi@latest balance --token STRK
# Confirm recipient with user if needed
npx starkfi@latest send 10 STRK 0x04a3...
npx starkfi@latest tx-status <hash>User: "Simulate sending 100 USDC to 0x07b2..."
npx starkfi@latest send 100 USDC 0x07b2... --simulateError Handling
| Error | Action |
Insufficient balance | Inform user of current balance via balance. |
Invalid address | Validate recipient is a valid 0x Starknet address. |
Simulation failed | Transaction would revert — check amount, token, and gas. |
Not authenticated | Run authenticate-wallet skill first. |
Related Skills
- Use
balanceto verify funds before sending. - Use
configto set a custom RPC if experiencing rate limits. - Use
tradeif the user needs to swap tokens before sending. - Use
confidentialfor privacy-preserving transfers (hidden amounts, ZK proofs).
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

