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

trade

Skill2 starsChanged 8 months agoMITView on GitHub

Swap tokens on Starknet via Fibrous DEX aggregator. Supports per-provider selection (avnu, ekubo, or auto to race all). Use this skill when the user wants to swap, exchange, trade, convert, buy, or sell one token for another on Starknet. Also use when the user asks about token prices, exchange rates, DEX routing, best swap route, or wants to check how much they would receive for a given amount — even if they don't explicitly say "swap".

5 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

10 rules. 0 are common, 0 are distinctive, and 10 are very specific to this project.

  • 0

    Common

    Most of the 5 edited versions we read keep these.

  • 0

    Distinctive

    This author's own choices. Worth a look.

  • 10

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    BEFORE any trade, you MUST run npx starkfi@latest status and npx starkfi@latest balance to verify connectivity and source token balance.

    line 29
  2. Very specific:

    Default slippage is 1%. To change, use --slippage <percent>.

    line 30
  3. Very specific:

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

    line 32
  4. Very specific:

    Use balance to check available tokens before trading.

    line 92
  5. Very specific:

    Use multi-swap for executing 2-3 swaps in a single transaction.

    line 93
  6. Very specific:

    Use batch for combining a swap with other operations (stake, supply, send, dca, troves).

    line 94
  7. Very specific:

    Use dca for recurring buy orders instead of a one-time swap.

    line 95
  8. Very specific:

    Use troves to deposit swap proceeds into yield vaults.

    line 96
  9. Very specific:

    Use lst for liquid staking after swapping to STRK.

    line 97
  10. Very specific:

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

    line 98

“Common” is measured: kept by at least 6 in 10 of the 5 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

Trade / Swap Tokens

Exchange one token for another on Starknet via Fibrous (default). Other providers (AVNU, Ekubo) can be selected with --provider, or use --provider auto to race all providers for the best price. All transactions are routed through the Paymaster by default (gas paid in STRK or configured token).

Prerequisites

  • Active session required.
  • Sufficient balance of the source token + gas fees.

Rules

  1. BEFORE any trade, you MUST run npx starkfi@latest status and npx starkfi@latest balance to verify connectivity and source token balance.
  2. Default slippage is 1%. To change, use --slippage <percent>.
  3. Suggest using --simulate first for large trades so the user can review the estimated fee and expected output before committing.
  4. AFTER a successful trade, you MUST verify the transaction using npx starkfi@latest tx-status <hash>.
  5. For multiple swaps in one transaction, use the multi-swap skill instead.

Commands

npx starkfi@latest trade <amount> <from> <to> [--provider <fibrous|avnu|ekubo|auto>] [--slippage <percent>] [--simulate] [--json]

Parameters

ParameterTypeDescriptionRequired
amountnumberAmount of source token to swapYes
fromstringSource token symbol (e.g. ETH, USDC)Yes
tostringTarget token symbol (e.g. STRK, DAI)Yes
--providerstringProvider: fibrous (default), avnu, ekubo, auto (race all)No
--slippagenumberSlippage tolerance in % (default: 1)No
--simulateflagEstimate fees without broadcastingNo
--jsonflagOutput as JSONNo

Examples

User: "Swap 100 USDC for ETH"

npx starkfi@latest status
npx starkfi@latest balance --token USDC
npx starkfi@latest trade 100 USDC ETH
npx starkfi@latest tx-status <hash>

User: "How much ETH would I get for 500 USDC?"

npx starkfi@latest trade 500 USDC ETH --simulate

User: "Convert 0.5 ETH to STRK with 2% slippage"

npx starkfi@latest status
npx starkfi@latest balance --token ETH
npx starkfi@latest trade 0.5 ETH STRK --slippage 2
npx starkfi@latest tx-status <hash>

Error Handling

ErrorAction
No route foundLiquidity may be too low or pair doesn't exist.
Insufficient balanceCheck balance and suggest a smaller amount.
Provider unavailableSpecified provider is invalid. Valid: fibrous, avnu, ekubo.
All providers failedAll providers timed out or errored. Retry later.
Simulation failedRoute is invalid or would revert. Do not retry blindly.
Not authenticatedRun authenticate-wallet skill first.

Related Skills

  • Use balance to check available tokens before trading.
  • Use multi-swap for executing 2-3 swaps in a single transaction.
  • Use batch for combining a swap with other operations (stake, supply, send, dca, troves).
  • Use dca for recurring buy orders instead of a one-time swap.
  • Use troves to deposit swap proceeds into yield vaults.
  • Use lst for liquid staking after swapping to STRK.
  • Use config to set a custom RPC if experiencing rate limits.

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.