메뉴
Move assets from one DeFi vault to another using vaults.fyi for exit/entry transaction construction and safety checks, with Zerion CLI handling swaps and cross-chain bridging between positions.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
Research a DeFi vault using vaults.fyi due diligence (risk, performance, fees, benchmarks), build a deposit transaction via vaults.fyi with pre-flight safety checks, and use Zerion CLI for asset acquisition and post-deposit verification.
Get the current state of the DeFi yield market using vaults.fyi benchmark rates, compare vaults side-by-side, evaluate curators, and check how a Zerion wallet's positions stack up against market rates.
Continuous risk monitoring for DeFi vault positions using vaults.fyi flags, incident tracking, score changes, benchmark deviations, and withdrawal constraints, paired with Zerion wallet data for full portfolio context.
Institutional-grade yield strategy analysis using vaults.fyi historical data, benchmark rate environments, share price trends, and curator track records, paired with Zerion wallet context.
Track wallets with Zerion's watchlist and run yield audits against vaults.fyi data to monitor positions, spot yield decay, detect new deployments, and surface opportunities across watched addresses.
Audit a Zerion wallet's DeFi positions against vaults.fyi yield data to find where you're leaving yield on the table, surface better alternatives, and identify idle assets that could be earning.
| name | zerion-vaultsfyi-rebalance |
| description | Move assets from one DeFi vault to another using vaults.fyi for exit/entry transaction construction and safety checks, with Zerion CLI handling swaps and cross-chain bridging between positions. |
| license | MIT |
Purpose: Execute a full vault-to-vault rebalance using vaults.fyi for withdrawal and deposit transaction construction (with safety gates at every step) and Zerion CLI for any swaps or cross-chain bridges needed between the exit and entry.
zerion portfolio <address> — confirm wallet state before and afterzerion positions <address> — verify DeFi positionszerion swap <chain> <amount> <from> <to> — swap between assets if the destination vault takes a different tokenzerion bridge <from-chain> <token> <amount> <to-chain> <token> — bridge assets cross-chain between exit and entryvault_details — inspect both source and destination vaultsposition_details — current position value and state in the source vaulttransaction_context — pre-flight check for both withdrawal and depositbuild_vault_tx — construct unsigned withdrawal and deposit transactionsvaults_search — find the destination vault if not specifiedbenchmark_apy — confirm the rebalance actually improves yield vs benchmarksubmit_tx_hash / get_transaction_status — track transactions post-signingnpm install -g zerion-cliexport ZERION_API_KEY="zk_..."Check the wallet's state and identify the source vault position.
zerion positions <address>
Call vaults.fyi position_details with the wallet address and source vault to get: current value, unrealized returns, the vault's withdrawal mechanics, and any active flags.
Call vault_details on the source vault and call transaction_context to inspect the redeem flow:
redeemStepsType): Check transactionalProperties.redeemStepsType. If "instant", withdrawal is a single transaction. If "complex", the exit requires multiple steps with potential delays between them (e.g., request withdrawal → wait for processing → claim). Complex redeems may involve cooldown periods (hours or days), withdrawal queues, or settlement windows. The vaultSpecificData field in transaction_context may contain timing details.Call vault_details on the destination vault. Run the same safety checks as the deposit skill:
vaults_search.Call benchmark_apy for the destination vault's network and asset type. Confirm the rebalance produces a meaningful APY improvement (at least 1 percentage point after fees).
Before building any transactions, show the user:
| Field | Source Vault | Destination Vault |
|---|---|---|
| Vault name | ||
| Curator | ||
| Network | ||
| Asset | ||
| 30d APY | ||
| Score | ||
| Flags | ||
| Fees (exit/entry) |
Require explicit user approval before proceeding.
Call build_vault_tx with action: "redeem" (or "request-redeem" for complex flows), userAddress, network, and vaultId for the source vault. Present the unsigned transaction to the user for signing.
After signing and broadcasting:
submit_tx_hash with sessionId, stepId (from the build_vault_tx response), and the broadcast txHash to track the withdrawal.get_transaction_status to confirm the withdrawal settled.zerion portfolio <address>
If the destination vault is on the same chain and accepts the same asset, skip to step 7.
If the destination vault accepts a different asset:
zerion swap <chain> <amount> <withdrawn-token> <deposit-token>
If the destination vault is on a different chain:
zerion bridge <source-chain> <token> <amount> <dest-chain> <token> --cheapest
For cross-chain + different asset, bridge first, then swap on the destination chain.
Call transaction_context for the destination vault to confirm the deposit asset, decimals, and wallet balance.
Call build_vault_tx with action: "deposit", userAddress, network, vaultId, and preferably humanAmount + decimals from transaction_context (the tool converts to base units automatically). Present the unsigned transaction for signing.
After signing and broadcasting:
submit_tx_hash with sessionId, stepId, and txHash to track the deposit.get_transaction_status to confirm the deposit settled.Confirm the new position with both Zerion and vaults.fyi:
zerion positions <address>
Call position_details on the destination vault to confirm the position is active with the expected value.
redeemStepsType: "complex"): The exit may require multiple transactions with delays between them. Common patterns: (1) request-then-claim with a processing period, (2) cooldown initiation followed by a waiting period before withdrawal unlocks (e.g., Ethena sUSDe), (3) quarterly settlement windows where withdrawals only process at specific dates. Check transaction_context for the specific flow and vaultSpecificData for timing. Inform the user upfront that the rebalance will span multiple sessions.depositStepsType: "complex"): The entry may also require multiple sequential transactions. Present the full deposit sequence after the withdrawal completes so the user knows the total operational cost.vaults_search with the same asset and network.