一键导入
rlusd-transfer
Execute an explicit RLUSD transfer or payment workflow using the external rlusd-cli runtime with prepare, review, execute, and receipt steps.
用 Codex 或 Claude 帮你安装 复制这段 Prompt,粘贴到 Codex、Claude 或其他助手里,让它检查 Skill 页面并帮你完成安装。
菜单
Execute an explicit RLUSD transfer or payment workflow using the external rlusd-cli runtime with prepare, review, execute, and receipt steps.
用 Codex 或 Claude 帮你安装 复制这段 Prompt,粘贴到 Codex、Claude 或其他助手里,让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Use when a user wants to inspect or execute RLUSD Wormhole NTT bridge routes, estimates, prepared bridge plans, execution, or status/history across supported EVM chains.
Route RLUSD requests to the correct chain workflow and keep side effects behind explicit planning.
Use when an RLUSD workflow depends on a local rlusd-cli wallet name, the user says "my wallet", or a command needs `--from-wallet`, `--owner-wallet`, or `--wallet`.
XRPL x402 buyer flow. Use when the user wants to fetch a paid API resource using the x402 HTTP payment protocol with an XRPL wallet.
RLUSD on XRPL. Use for issuer resolution, trust-line semantics, read commands, prepare workflows, controlled execution, and transaction status checks.
RLUSD buy and redeem guidance. Use for manual provider, rail, and prerequisite instructions, not automated fiat execution.
| name | rlusd-transfer |
| description | Execute an explicit RLUSD transfer or payment workflow using the external rlusd-cli runtime with prepare, review, execute, and receipt steps. |
| user-invocable | true |
Use this skill when the user explicitly wants to move RLUSD and is ready to go through the action workflow rather than just inspect metadata or balances.
rlusd-trustline.rlusd-defi-action.evm transfer ... for token transfers and evm approve ...xrpl payment ...--from-wallet, --owner-wallet, or --wallet,
load rlusd-wallets to confirm the local wallet alias or provision one with
explicit user approval.prepare, review the resulting plan_id and plan_path,
then call execute with a matching --confirm-plan-id.rlusd evm transfer prepare --chain ethereum-mainnet --from-wallet ops --to 0x... --amount 25.5 --json
rlusd evm transfer execute --plan <plan_path_from_prepare> --confirm-plan-id <plan_id_from_prepare> --password "$RLUSD_WALLET_PASSWORD" --json
rlusd evm tx wait --chain ethereum-mainnet --hash 0x... --json
rlusd evm approve prepare --chain ethereum-mainnet --owner-wallet ops --spender 0x... --amount 1000 --json
rlusd evm approve execute --plan <plan_path_from_prepare> --confirm-plan-id <plan_id_from_prepare> --password "$RLUSD_WALLET_PASSWORD" --json
rlusd evm tx receipt --chain ethereum-mainnet --hash 0x... --json
rlusd xrpl payment prepare --chain xrpl-mainnet --from-wallet treasury-xrpl --to r... --amount 250 --json
rlusd xrpl payment execute --plan <plan_path_from_prepare> --confirm-plan-id <plan_id_from_prepare> --wallet treasury-xrpl --password "$RLUSD_WALLET_PASSWORD" --json
rlusd xrpl tx wait --chain xrpl-mainnet --hash ABCD... --json
rlusd xrpl payment receipt --chain xrpl-mainnet --hash ABCD... --json
plan_path and plan_id returned by prepare.ops or treasury-xrpl already
exist locally; use rlusd-wallets before wallet-backed transfer steps.--password "$RLUSD_WALLET_PASSWORD" explicitly for
predictability; the CLI can also read RLUSD_WALLET_PASSWORD from the
environment.evm transfer preparerlusd-wallets, then run evm transfer prepareevm approve preparexrpl payment prepare