Agent Skills - Fibrous Documentation

fibx-skills is a collection of eleven agent skills that wrap the fibx CLI for use by AI agents. Each skill defines a specific capability — authentication, the signing policy, balances, portfolio inspection, transfers, swaps, DeFi management, and transaction verification — with structured rules, allowed tools, and error handling. Skills follow the Agent Skills specification and can be imported into any compatible agent framework.

How Skills Work

Each skill is a structured YAML+Markdown file that defines:

Allowed tools — The CLI command patterns declared by the installed skill
Rules — Constraints and safety checks the agent must follow
Parameters — Inputs the agent extracts from the user’s natural language prompt
Error handling — How the agent should respond to specific failures

When a user gives a natural language instruction (e.g., “Swap 0.1 ETH to USDC”), the agent matches it to the appropriate skill, extracts parameters, follows the defined rules, and executes the CLI commands in sequence.

Getting Started

Install the skills directly using the Vercel Skills CLI:

npx skills add Fibrous-Finance/fibx-skills

Or clone the repository manually and import from the ./skills directory:

git clone https://github.com/Fibrous-Finance/fibx-skills.git

No separate installation of fibx is needed — all skills use npx fibx@latest.

Skills require Node.js 18+ and are compatible with fibx CLI v0.10.x. The installed SKILL.md files are the source of truth for allowed-tool patterns and rules; the summaries below describe the current published skills and may change independently of this page.

Available Skills

quote

Category: Read-OnlyFetches a swap price without a wallet or a session, so an agent can answer a pricing question for a user who has not logged in — and then offer authenticate-wallet if they want to execute.

Allowed Tools

Bash(npx fibx@latest quote *)

Rules

Never require or suggest authentication before quoting — this skill needs none.
If the user specifies a chain, include --chain <name>; otherwise default to base and say so.
Default slippage is 0.5%. Include --slippage only when the user explicitly requests another value.
Direct native/wrapped-native pairs return a 1:1 wrap or unwrap quote.
After quoting, offer trade as the execution step, noting that it does require a session.

Trigger Examples

User Prompt	Action
”How much USDC for 0.1 ETH?”	`quote 0.1 ETH USDC`
”What’s the MON price in USDC?”	`quote 1 MON USDC --chain monad`

authenticate-wallet

Category: AuthManages the wallet session. This skill must run before any other wallet operation. Three signing paths are available, and they are peers — auth setup presents the choice:

Your own wallet (auth connect) — pair a wallet you already have over WalletConnect. Every transaction is approved on the phone; nothing is signed on the machine.
Privy server wallet (auth login + auth verify) — a server-managed wallet via email OTP; runs unattended, bounded by Privy’s policy and the local one.
Imported private key (auth import) — encrypted locally; runs unattended, bounded by the local signing policy alone.

Allowed Tools

Bash(npx fibx@latest auth setup)
Bash(npx fibx@latest auth connect *)
Bash(npx fibx@latest auth login *)
Bash(npx fibx@latest auth verify *)
Bash(npx fibx@latest auth import)
Bash(npx fibx@latest auth logout)
Bash(npx fibx@latest status)

Rules

If the user has not said how they want to sign, run auth setup or ask. Do not default to Privy.
Never ask the user for a private key. auth import prompts for it in the terminal.
Before auth import, warn: “Your private key will be encrypted with AES-256-GCM and stored on this machine. With an imported key, the local signing policy is the only thing bounding what this wallet signs — I can set one with the policy skill. Proceed?”
auth login must complete before auth verify — they are sequential steps.
auth connect prints a QR and waits; tell the user to scan it with their wallet and approve. Every later trade or send blocks until they approve it on the phone.
After any of these, run status to confirm the session. Any of them replaces the active session; say so before switching.
Never store or log private keys, OTP codes, pairing URIs, or session data.

Trigger Examples

User Prompt	Action
”Which wallet setup should I use?”	`auth setup`
”Connect my own wallet” / “Use my MetaMask”	`auth connect`
”Import my private key”	`auth import`
”Log me in with user@example.com”	`auth login` then `auth verify`
”Log me out”	`auth logout`

policy

Category: AuthReads and changes the local signing policy — a file on the user’s machine that caps the native value per chain, allowlists chains and destinations, and expires. FibX evaluates it before every signature on all three signing paths. Use it when a transaction is refused with POLICY_BLOCKED, or when the user wants to bound what the wallet can sign. No session is needed.

Allowed Tools

Bash(npx fibx@latest policy *)

Rules

Propose a concrete value and explain what it bounds; set it only after the user agrees.
maxValue bounds native value only — an ERC-20 transfer reaches the policy with value: 0. Only allowedDestinations bounds where tokens go. Never tell the user the cap limits token amounts.
On the imported-key path this file is the only bound. If policy show shows nothing on a private-key session, recommend at least a maxValue before any trade or send.
A refusal names its rule. Relay the rule and limit and ask; do not retry, and do not loosen the rule unasked.
policy clear with no rule removes the whole policy and asks for confirmation. Never pass -y unless the user explicitly asked to remove everything.

Trigger Examples

User Prompt	Action
”Cap what this wallet can sign to 0.05 ETH on Base”	`policy set base.maxValue 0.05`
”Only let it use Base and Monad”	`policy set allowedChains base,monad`
”What limits are on my wallet?”	`policy show`
”Remove the cap”	`policy clear base.maxValue`

wallet-info

Category: WalletReports which wallet is active — address, wallet ID, session type, and when the session was created. Use it when the user asks for their receiving address or which account they are signed in as.

Allowed Tools

Bash(npx fibx@latest address)
Bash(npx fibx@latest address *)
Bash(npx fibx@latest wallets)
Bash(npx fibx@latest wallets *)

Prerequisite: An active session is required. If no session is active, run the authenticate-wallet skill first.

Rules

Use address when only the receiving address is needed; use wallets for full session details.
Neither command takes --chain — the same address is used on every supported chain.
Always show the full address. Never truncate an address the user may need to copy.
Use --json when another skill or automation will consume the output.

Trigger Examples

User Prompt	Action
”What’s my wallet address?”	`address`
”Which wallet am I using?”	`wallets`

balance

Category: WalletFetches native and ERC-20 token balances for the authenticated wallet on any supported chain.

Allowed Tools

Bash(npx fibx@latest balance *)
Bash(npx fibx@latest balance)
Bash(npx fibx@latest status)

Rules

If the user specifies a chain, include --chain <name>.
If no chain is specified, default to base and state it.
Use --json when output is consumed by another skill.

Trigger Examples

User Prompt	Action
”Check my balance”	`balance` (defaults to Base)
“What’s my Monad balance?”	`balance --chain monad`

portfolio

Category: WalletFetches a consolidated cross-chain portfolio view with USD valuations for all token holdings and DeFi positions across Base, HyperEVM, and Monad.

Allowed Tools

Bash(npx fibx@latest portfolio *)
Bash(npx fibx@latest portfolio)
Bash(npx fibx@latest status)

Rules

This command fetches all supported chains in parallel, so no --chain flag is needed.
Use --json when the output will be consumed by another skill or automation pipeline.
Chains with zero holdings may be hidden in the output.
DeFi positions on Aave V3 are included automatically when present.

Trigger Examples

User Prompt	Action
”Show me my portfolio”	`portfolio`
”What’s my total net worth?”	`portfolio`
”Get my portfolio as JSON”	`portfolio --json`

send

Category: TransactionTransfers native tokens or ERC-20 tokens to a destination address. The CLI performs a command-specific preflight and supports --simulate for a transfer preview.

Allowed Tools

Bash(npx fibx@latest send *)
Bash(npx fibx@latest status)
Bash(npx fibx@latest balance *)
Bash(npx fibx@latest balance)
Bash(npx fibx@latest tx-status *)

Rules

Before any send, verify connectivity (status) and funds (balance).
If the recipient address was not previously mentioned, ask for explicit confirmation.
If the user specifies a chain, include --chain <name>; otherwise default to base and say so.
Use the correct native token symbol for each chain — never use ETH on non-Base chains.
After a successful send, verify the transaction with tx-status on the same chain.

Trigger Examples

User Prompt	Action
”Send 10 USDC to 0x123…”	`send 10 0x123... USDC`
”Send 0.05 MON to 0xdef… on Monad”	`send 0.05 0xdef... MON --chain monad`

trade

Category: TransactionSwaps tokens via Fibrous aggregation. Finds a route, handles approvals, estimates the main swap path, and executes.

Allowed Tools

Bash(npx fibx@latest trade *)
Bash(npx fibx@latest quote *)
Bash(npx fibx@latest status)
Bash(npx fibx@latest balance *)
Bash(npx fibx@latest balance)
Bash(npx fibx@latest tx-status *)

Rules

Before any trade, verify connectivity and source token balance.
If the user specifies a chain, include --chain <name>; otherwise default to base and say so.
Default slippage is 0.5%. To change it, ask the user for confirmation.
Never use --approve-max unless the user explicitly requests it.
After a successful trade, verify the transaction with tx-status on the same chain.

trade --simulate does not broadcast an approval or swap. When an ERC-20 approval is required, it returns requiresApproval: true without a gas estimate.

A live routed ERC-20 trade can leave an approval on-chain if the later swap estimate or submission fails. Treat the approval and swap as separate transactions.

Trigger Examples

User Prompt	Action
”Swap 0.1 ETH for USDC”	`trade 0.1 ETH USDC`
”Buy USDC with 1 MON on Monad”	`trade 1 MON USDC --chain monad`

aave

Category: DeFiManages Aave V3 lending positions on Base only — status, markets, supply, borrow, repay, withdraw, and health factor monitoring. ETH supply and repay can auto-wrap to WETH, while ETH withdraw can auto-unwrap to ETH. Borrowing the ETH market returns WETH.aave markets is a public query. aave status and all transactional actions require an active session. An action with --simulate returns request metadata without on-chain validation or a gas estimate.

Allowed Tools

Bash(npx fibx@latest aave *)
Bash(npx fibx@latest status)
Bash(npx fibx@latest balance *)
Bash(npx fibx@latest balance)

Rules

This skill only works on Base. Refuse Aave operations on other chains.
Before any action, check balance for sufficient ETH for gas.
Before borrowing, check aave status for the Health Factor:
- Health Factor < 1.5 → Warn the user about liquidation risk
- Health Factor < 1.1 → Do not proceed without explicit double-confirmation
max is supported only for repay and withdraw. Use it when fully repaying debt or withdrawing a supplied position to avoid dust residuals.
Use ETH for ETH-market supply, repay, and withdraw so the CLI can apply the documented wrap/unwrap behavior. Borrowing that market returns WETH.
If a Rate limit / 429 error occurs, use the config skill to set a custom RPC.

ETH ↔ WETH Auto-Wrap Reference

Action	ETH Behavior
`supply 1 ETH`	Auto-wraps ETH → WETH before supplying
`borrow 1 ETH`	Borrows WETH; no automatic unwrap
`repay max ETH`	Auto-wraps ETH → WETH before repaying
`withdraw max ETH`	Withdraws WETH and auto-unwraps → ETH

Live wrap, approval, Aave, and unwrap steps are separate transactions, so an earlier step remains on-chain if a later one fails. aave withdraw max ETH unwraps the wallet’s entire post-withdraw WETH balance, including WETH held before the command.

Trigger Examples

User Prompt	Action
”How is my Aave position?”	`aave status`
”What markets are on Aave?”	`aave markets`
”Supply 1 ETH to Aave”	`aave supply 1 ETH`
”Supply 100 USDC to Aave”	`aave supply 100 USDC`
”Repay my ETH debt”	`aave repay max ETH`
”Repay all my USDC debt”	`aave repay max USDC`
”Withdraw all my ETH”	`aave withdraw max ETH`

config

Category: UtilityView and modify fibx CLI configuration — primarily used to set custom RPC URLs when hitting rate limits on public endpoints. Configuration is stored locally and persists across sessions.

Allowed Tools

Bash(npx fibx@latest config *)

Rules

If any command fails with a “Rate limit exceeded” or “429” error, use this skill to set a custom RPC for the affected chain.
Settings use the OS-specific FibX config directory and persist across sessions (for example, ~/.config/fibx-nodejs/config.json on Linux and ~/Library/Preferences/fibx-nodejs/config.json on macOS).
The CLI validates URL format but not connectivity — ensure the RPC URL is valid before setting.

Commands

# Set a custom RPC for a chain
npx fibx@latest config set-rpc <chain> <url>

# View the current RPC for a chain
npx fibx@latest config get-rpc <chain>

# Reset one chain or all chains to default
npx fibx@latest config reset-rpc <chain>
npx fibx@latest config reset-rpc

# List all custom configurations
npx fibx@latest config list

Trigger Examples

User Prompt	Action
”I’m getting rate limit errors”	`config set-rpc <chain> <url>`
”I’m getting rate limited on Base”	`config set-rpc base https://mainnet.base.org`
”Reset all RPCs to default”	`config reset-rpc`
”Check my current configuration”	`config list`

tx-status

Category: UtilityChecks the on-chain status of a transaction and returns the block explorer link. No authentication is required — this is a public chain query.

Allowed Tools

Bash(npx fibx@latest tx-status *)

Rules

Use the same --chain flag that was used for the original transaction.
Use this skill after every send or trade to verify success.

Trigger Examples

User Prompt	Action
”Did my transaction go through?”	`tx-status <hash>`
”Check tx 0xabc…def on Monad”	`tx-status 0xabc...def --chain monad`

Agent Workflow Example

A typical multi-step interaction between a user and an AI agent using fibx-skills:

With Your Own Wallet
With Private Key
With Email OTP

User: 'Connect my own wallet'

Agent triggers authenticate-wallet:

npx fibx@latest auth connect
npx fibx@latest status

The user scans the QR with their wallet app and approves the pairing. Session is now active; every transaction from here is approved on the phone.

User: 'Swap 0.05 ETH to USDC'

Agent triggers balance then trade:

npx fibx@latest balance
npx fibx@latest trade 0.05 ETH USDC

Agent says: “Approve the swap in your wallet.” The command waits until the user does.

Agent verifies automatically

Agent triggers tx-status:

npx fibx@latest tx-status 0x7a3f...c21b

Agent responds: “Swap completed. 0.05 ETH → 47.23 USDC. View on BaseScan”

User: 'Import my private key'

Agent triggers authenticate-wallet:

npx fibx@latest auth import
npx fibx@latest status

The user pastes their private key in the interactive prompt. Session is now active.

Agent: 'Nothing limits this wallet yet — cap it at 0.05 ETH?'

Agent triggers policy after the user agrees:

npx fibx@latest policy set base.maxValue 0.05

User: 'Swap 0.05 ETH to USDC'

Agent triggers balance then trade:

npx fibx@latest balance
npx fibx@latest trade 0.05 ETH USDC

Agent verifies automatically

Agent triggers tx-status:

npx fibx@latest tx-status 0x7a3f...c21b

Agent responds: “Swap completed. 0.05 ETH → 47.23 USDC. View on BaseScan”

User: 'Log me in with alice@example.com'

Agent triggers authenticate-wallet:

npx fibx@latest auth login alice@example.com

Agent asks: “Please provide the OTP code sent to your email.”

User: '482910'

Agent completes authentication:

npx fibx@latest auth verify alice@example.com 482910
npx fibx@latest status

User: 'Swap 0.05 ETH to USDC'

Agent triggers balance then trade:

npx fibx@latest balance
npx fibx@latest trade 0.05 ETH USDC

Agent verifies automatically

Agent triggers tx-status:

npx fibx@latest tx-status 0x7a3f...c21b

Agent responds: “Swap completed. 0.05 ETH → 47.23 USDC. View on BaseScan”

​How Skills Work

​Getting Started

​Available Skills

​Allowed Tools

​Rules

​Trigger Examples

​Allowed Tools

​Rules

​Trigger Examples

​Allowed Tools

​Rules

​Trigger Examples

​Allowed Tools

​Rules

​Trigger Examples

​Allowed Tools

​Rules

​Trigger Examples

​Allowed Tools

​Rules

​Trigger Examples

​Allowed Tools

​Rules

​Trigger Examples

​Allowed Tools

​Rules

​Trigger Examples

​Allowed Tools

​Rules

​ETH ↔ WETH Auto-Wrap Reference

​Trigger Examples

​Allowed Tools

​Rules

​Commands

​Trigger Examples

​Allowed Tools

​Rules

​Trigger Examples

​Agent Workflow Example

How Skills Work

Getting Started

Available Skills

Allowed Tools

Rules

Trigger Examples

Allowed Tools

Rules

Trigger Examples

Allowed Tools

Rules

Trigger Examples

Allowed Tools

Rules

Trigger Examples

Allowed Tools

Rules

Trigger Examples

Allowed Tools

Rules

Trigger Examples

Allowed Tools

Rules

Trigger Examples

Allowed Tools

Rules

Trigger Examples

Allowed Tools

Rules

ETH ↔ WETH Auto-Wrap Reference

Trigger Examples

Allowed Tools

Rules

Commands

Trigger Examples

Allowed Tools

Rules

Trigger Examples

Agent Workflow Example