Smart Accounts

Deploy and manage multi-signature smart accounts. Use when you or the user want to create a smart wallet, deploy a multi-sig, add or remove owners, change th...

Security Scan

The skill's instructions and requirements are consistent with its stated purpose (it simply wraps fdx CLI calls to deploy and manage multi-sig smart accounts), but it performs sensitive on-chain operations so you should ensure the correct wallet is authenticated and require human confirmation before executing commands.

Purpose & Capability

Name/description (deploy/manage multi-sig smart accounts) matches the instructions: all runtime steps are fdx CLI calls for deploying accounts, managing owners, and viewing account details. No unrelated binaries, env vars, or config paths are requested.

Instruction Scope

SKILL.md only tells the agent to run specific fdx commands (status, deploySmartAccount, manageSmartAccountOwnership, getWalletOverview). It does not instruct reading unrelated files or secrets. It does rely on an already-authenticated wallet but does not enforce or programmatically require explicit human confirmation before executing sensitive ownership-change actions (it only includes a textual admonition).

Install Mechanism

Instruction-only skill with no install spec, no downloads, and no code files — minimal persistence and no code written to disk.

Credentials

The skill declares no required env vars or credentials, which is consistent because it uses whatever wallet the fdx CLI is already authenticated to. This is proportionate, but it means the skill will act with whatever on-chain identity/configuration is present in the environment — a potentially sensitive capability that users should be aware of.

Persistence & Privilege

always:false and user-invocable:true. The skill does not request permanent presence or modify other skills/config. Model invocation is enabled (default), so the agent could run these commands autonomously if permitted by platform policies — not a platform anomaly but worth user attention given the sensitive operations.

Assessment

This skill is coherent and simply runs fdx CLI commands to deploy/manage multi-sig wallets. Before installing or invoking it: (1) confirm which wallet is authenticated in your environment (fdx status) — the skill will act with that identity; (2) test on a non-production/testnet chain first; (3) require explicit human approval for ownership-changing commands (add/remove owner, change threshold) because the SKILL.md only contains an advisory, not an enforced confirmation step; (4) restrict autonomous invocation or remove the skill if you don't want an agent to execute on-chain transactions without a manual checkpoint.

Smart Account Management

Deploy multi-signature smart accounts on any supported EVM chain and manage their ownership (add/remove owners, change signing threshold).

Confirm wallet is authenticated

fdx status

If the wallet is not authenticated, refer to the authenticate skill.

Deploying a Smart Account

Create a new smart account on a specific chain:

fdx call deploySmartAccount \
  --chainKey <chain>

deploySmartAccount Parameters

Parameter	Required	Description
--chainKey	Yes	Blockchain to deploy on (e.g. ethereum, polygon, base, arbitrum)
--initialOwners	No	Comma-separated list of owner addresses
--threshold	No	Number of signatures required to execute transactions

Examples

# Deploy a simple smart account on Ethereum
fdx call deploySmartAccount --chainKey ethereum

# Deploy a 2-of-3 multi-sig
fdx call deploySmartAccount \
  --chainKey ethereum \
  --initialOwners 0xOwner1...,0xOwner2...,0xOwner3... \
  --threshold 2

Managing Ownership

Add owners, remove owners, or change the signing threshold on an existing smart account:

fdx call manageSmartAccountOwnership \
  --chainKey <chain> \
  --accountAddress <smartAccountAddress> \
  --action <action>

manageSmartAccountOwnership Parameters

Parameter	Required	Description
--chainKey	Yes	Blockchain of the smart account
--accountAddress	Yes	Smart account address to manage
--action	Yes	Action to perform (e.g. addOwner, removeOwner, changeThreshold)
--ownerAddress	No	Owner address to add or remove (required for addOwner/removeOwner)
--newThreshold	No	New signing threshold (required for changeThreshold)

Examples

# Add a new owner
fdx call manageSmartAccountOwnership \
  --chainKey ethereum \
  --accountAddress 0xSmartAccount... \
  --action addOwner \
  --ownerAddress 0xNewOwner...

# Remove an owner
fdx call manageSmartAccountOwnership \
  --chainKey ethereum \
  --accountAddress 0xSmartAccount... \
  --action removeOwner \
  --ownerAddress 0xOldOwner...

# Change the threshold to 3-of-5
fdx call manageSmartAccountOwnership \
  --chainKey ethereum \
  --accountAddress 0xSmartAccount... \
  --action changeThreshold \
  --newThreshold 3

Viewing Smart Account Details

Check the smart account's holdings and activity:

fdx call getWalletOverview \
  --chainKey <chain> \
  --accountAddress <smartAccountAddress>

Flow

1. Check authentication with fdx status
2. Deploy a smart account with fdx call deploySmartAccount
3. Note the returned smart account address
4. Manage ownership as needed with fdx call manageSmartAccountOwnership
5. Use the smart account address in send-tokens or swap-tokens skills via --fromAccountAddress

Important: Ownership changes on multi-sig accounts are sensitive operations. Always confirm the action, addresses, and new threshold with your human before executing. Removing too many owners or setting the threshold too high can lock the account.

Prerequisites

• Must be authenticated (fdx status to check, see authenticate skill)
• Smart accounts are deployed on EVM chains only (not Solana)

Error Handling

• "Not authenticated" — Run fdx setup first, or see authenticate skill
• "Invalid account address" — Verify the smart account address exists on the specified chain
• "Threshold exceeds owner count" — Threshold must be ≤ number of owners