agentleFS
ahmetenesdurahmetenesdur/starkfi/skills/send/SKILL.md

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

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
  1. Very specific:

    BEFORE any send, you MUST run npx starkfi@latest status and npx starkfi@latest balance to verify connectivity and funds.

    line 29
  2. Distinctive:

    If the recipient address was NOT previously mentioned in the conversation, you MUST ask for explicit confirmation: _"Sending [amount] …

    line 30
  3. Very specific:

    AFTER a successful send, you MUST verify the transaction using npx starkfi@latest tx-status <hash>.

    line 32
  4. Very specific:

    Use balance to verify funds before sending.

    line 80
  5. Very specific:

    Use config to set a custom RPC if experiencing rate limits.

    line 81
  6. Very specific:

    Use trade if the user needs to swap tokens before sending.

    line 82
  7. Very specific:

    Use confidential for privacy-preserving transfers (hidden amounts, ZK proofs).

    line 83

“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.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

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

  1. BEFORE any send, you MUST run npx starkfi@latest status and npx starkfi@latest balance to verify connectivity and funds.
  2. If the recipient address was NOT previously mentioned in the conversation, you MUST ask for explicit confirmation: "Sending [amount] [token] to [address]. Confirm?"
  3. Suggest using --simulate first for large amounts so the user can review the estimated fee before committing.
  4. AFTER a successful send, you MUST verify the transaction using npx starkfi@latest tx-status <hash>.
  5. Starknet addresses start with 0x and can be up to 66 characters long (including the 0x prefix).

Commands

npx starkfi@latest send <amount> <token> <recipient> [--simulate] [--json]

Parameters

ParameterTypeDescriptionRequired
amountnumberAmount to send (e.g. 10, 0.5)Yes
tokenstringToken symbol (e.g. STRK, ETH, USDC)Yes
recipientstringDestination Starknet address (0x...)Yes
--simulateflagEstimate fees without broadcastingNo
--jsonflagOutput as JSONNo

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... --simulate

Error Handling

ErrorAction
Insufficient balanceInform user of current balance via balance.
Invalid addressValidate recipient is a valid 0x Starknet address.
Simulation failedTransaction would revert — check amount, token, and gas.
Not authenticatedRun authenticate-wallet skill first.

Related Skills

  • Use balance to verify funds before sending.
  • Use config to set a custom RPC if experiencing rate limits.
  • Use trade if the user needs to swap tokens before sending.
  • Use confidential for privacy-preserving transfers (hidden amounts, ZK proofs).

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.