菜单
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.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
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.
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.
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-deposit |
| description | 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. |
| license | MIT |
Purpose: Run vault due diligence via vaults.fyi and execute deposits through Zerion CLI, with safety gates that block critical-flagged vaults and require explicit approval for warned ones.
zerion portfolio <address> — check current holdings and balanceszerion positions <address> — see existing DeFi positionszerion swap <chain> <amount> <from> <to> — swap into the vault's deposit asset if neededzerion bridge <from-chain> <token> <amount> <to-chain> <token> — bridge assets cross-chainvault_details — full vault metadata, score, flags, fees, curatorvault_apy_history — historical APY over 30 daysvault_tvl_history — historical TVL over 30 daysbenchmark_apy — network benchmark rate for comparisontransaction_context — deposit asset, decimals, wallet balance, available actionsbuild_vault_tx — construct unsigned deposit transactionvaults_search — resolve vault by name if no address givennpm install -g zerion-cliexport ZERION_API_KEY="zk_..."Check the wallet's current state with Zerion to confirm it has the assets needed.
zerion portfolio <address>
Note the available balances. If the user needs to acquire the deposit token first, handle that before proceeding.
If the user provided a vault name rather than an address:
vaults_search with the name, asset, and network to find the matching vault.If the user provided an address, call vault_details directly with the address and network.
Gather the full risk and performance picture:
vault_details for score, flags, fees, curator, protocol, capacity, and underlying asset.vault_apy_history for 30-day APY trend. Set fromTimestamp to 30 days ago (current unix timestamp minus 2592000) to get recent data.vault_tvl_history for 30-day TVL trend. Set fromTimestamp the same way.benchmark_apy with the matching benchmark (usd for stablecoins, eth for ETH-denominated vaults) on the vault's network.Use apyComposite.totalApy when present instead of top-level APY.
Present a due diligence summary:
| Field | Value |
|---|---|
| Vault | name, protocol, curator, network |
| APY | 1d / 7d / 30d, composite if applicable |
| vs Benchmark | spread over network benchmark |
| TVL | current, 30d trend |
| Score | value out of 100, penalty notes |
| Flags | active warnings or critical incidents |
| Fees | performance, management, withdrawal |
| Capacity | deposit cap or remaining capacity |
This is the hard safety check before building any transaction.
Call transaction_context with the wallet address, network, and vault ID to get:
If the wallet doesn't have enough of the deposit asset, use Zerion to acquire it:
zerion swap <chain> <amount> <held-token> <deposit-asset>
Or bridge it from another chain:
zerion bridge <from-chain> <held-token> <amount> <vault-chain> <deposit-asset> --cheapest
Inspect transactionalProperties.depositStepsType from vault_details or transaction_context:
"instant": Standard single-step deposit. Proceed to building the transaction."complex": Multi-step deposit flow. This may require multiple sequential transactions (e.g., approve → deposit → stake, or deposit → bridge → confirm). Present all steps to the user upfront with the expected sequence and any delays between steps. Some complex flows require waiting for on-chain confirmations between steps before the next step can execute.After safety and balance checks pass:
build_vault_tx with action: "deposit", userAddress, network, vaultId, and preferably humanAmount (e.g. "10") + decimals from transaction_context (e.g. 6 for USDC, 18 for WETH). The tool converts to base units automatically.build_vault_tx returns multiple ordered steps. Present all steps with their sequence and any required delays.After the user signs and broadcasts the transaction:
submit_tx_hash with sessionId and stepId (from the build_vault_tx response) and the broadcast txHash.get_transaction_status to confirm the deposit landed.zerion positions <address>
build_vault_tx may include a token approval step that's redundant if the wallet already has sufficient allowance. Note this rather than presenting every approval as required.vaults_search.depositStepsType: "complex"): Some vaults require multiple sequential transactions to complete a deposit. Steps may include approvals, deposits into intermediate contracts, staking, or bridging. Present the full sequence to the user before starting. Some steps require on-chain confirmation before the next step can execute — do not batch them blindly.redeemStepsType: "complex"): Even if the deposit is instant, the vault may have complex withdrawal mechanics (request-then-claim with delays, cooldown periods, quarterly settlement windows). Surface this during due diligence so the user knows the liquidity profile before entering. Check transactionalProperties.redeemStepsType and any vault-specific data about withdrawal timing.