Requirements
- Target platform
- OpenClaw
- Install method
- Manual import
- Extraction
- Extract archive
- Prerequisites
- OpenClaw
- Primary doc
- SKILL.md
Tencent SkillHub ยท Developer Tools
Yield Agent
On-chain yield discovery, transaction building, and portfolio management via the Yield.xyz API. Use when the user wants to find yields, stake, lend, deposit into vaults, check balances, claim rewards, exit positions, compare APYs, or manage any on-chain yield across 80+ networks.
skill openclawclawhub Free
On-chain yield discovery, transaction building, and portfolio management via the Yield.xyz API. Use when the user wants to find yields, stake, lend, deposit into vaults, check balances, claim rewards, exit positions, compare APYs, or manage any on-chain yield across 80+ networks.
โฌ 0 downloads โ
0 stars Unverified but indexed
Install for OpenClaw
Quick setup
- Download the package from Yavira.
- Extract the archive and review SKILL.md first.
- Import or place the package into your OpenClaw setup.
Package facts
- Download mode
- Yavira redirect
- Package format
- ZIP package
- Source platform
- Tencent SkillHub
- What's included
- README.md, SKILL.md, skill.json, scripts/find-yields.sh, scripts/enter-position.sh, scripts/exit-position.sh
Validation
- Use the Yavira download entry.
- Review SKILL.md after the package is downloaded.
- Confirm the extracted package contains the expected setup assets.
Install with your agent
Agent handoff
Hand the extracted package to your coding agent with a concrete install brief instead of figuring it out manually.
- Download the package from Yavira.
- Extract it into a folder your agent can access.
- Paste one of the prompts below and point your agent at the extracted folder.
New install
I downloaded a skill package from Yavira. Read SKILL.md from the extracted folder and install it by following the included instructions. Then review README.md for any prerequisites, environment setup, or post-install checks. Tell me what you changed and call out any manual steps you could not complete.
Upgrade existing
I downloaded an updated skill package from Yavira. Read SKILL.md from the extracted folder, compare it with my current installation, and upgrade it while preserving any custom configuration unless the package docs explicitly say otherwise. Then review README.md for any prerequisites, environment setup, or post-install checks. Summarize what changed and any follow-up checks I should run.
Trust & source
Release facts
- Source
- Tencent SkillHub
- Verification
- Indexed source record
- Version
- 0.1.5
Provenance
- Publisher
- apurvmishra
- Source page
- View original listing
- Canonical URL
- Open canonical page
Documentation
YieldAgent by Yield.xyz
Access the complete on-chain yield landscape through Yield.xyz's unified API. Discover 2600+ yields across staking, lending, vaults, restaking, and liquidity pools. Build transactions and manage positions across 80+ networks.
CRITICAL: Never Modify Transactions From The API
DO NOT MODIFY unsignedTransaction returned by the API UNDER ANY CIRCUMSTANCES. Do not change, reformat, or "fix" any part of it โ not addresses, amounts, fees, encoding, or any other field, on any chain. If the amount is wrong: Request a NEW action from the API with the correct amount. If gas is insufficient: Ask the user to add funds, then request a NEW action. If anything looks wrong: STOP. Always request a new action with corrected arguments. Never attempt to "fix" an existing transaction. Modifying unsignedTransaction WILL RESULT IN PERMANENT LOSS OF FUNDS.
Key Rules
The API is self-documenting. Every yield describes its own requirements through the YieldDto. Before taking any action, always fetch the yield and inspect it. The mechanics field tells you everything: what arguments are needed (mechanics.arguments.enter, .exit), entry limits (mechanics.entryLimits), and what tokens are accepted (inputTokens[]). Never assume โ always check the yield first. Always fetch the yield before calling an action. Call GET /v1/yields/{yieldId} and read mechanics.arguments.enter (or .exit) to discover the exact fields required. Each yield is different โ the schema is the contract. Do not guess or hardcode arguments. Each field in the schema (ArgumentFieldDto) tells you: name: the field name (e.g., amount, validatorAddress, inputToken) type: the value type (string, number, address, enum, boolean) required: whether it must be provided options: static choices for enum fields (e.g., ["individual", "batched"]) optionsRef: a dynamic API endpoint to fetch choices (e.g., /api/v1/validators?integrationId=...) โ if present, call it to get the valid options (validators, providers, etc.) minimum / maximum: value constraints isArray: whether the field expects an array If a field has optionsRef, you must call that endpoint to get the valid values. This is how validators, providers, and other dynamic options are discovered. For manage actions, always fetch balances first. Call POST /v1/yields/{yieldId}/balances and read pendingActions[] on each balance. Each pending action tells you its type, passthrough, and optional arguments schema. Only call manage with values from this response. Amounts are human-readable. "100" means 100 USDC. "1" means 1 ETH. "0.5" means 0.5 SOL. Do NOT convert to wei or raw integers โ the API handles decimals internally. Set inputToken to what the user wants to deposit โ but only if inputToken appears in the yield's mechanics.arguments.enter schema. The API handles the full flow (swaps, wrapping, routing) to get the user into the position. ALWAYS submit the transaction hash after broadcasting โ no exceptions. For every transaction: sign, broadcast, then submit the hash via PUT /v1/transactions/{txId}/submit-hash with { "hash": "0x..." }. Balances will not appear until the hash is submitted. This is the most common mistake โ do not skip this step. Execute transactions in exact order. If an action has multiple transactions, they are ordered by stepIndex. Wait for CONFIRMED before proceeding to the next. Never skip or reorder. Consult {baseDir}/references/openapi.yaml for types. All enums, DTOs, and schemas are defined there. Do not hardcode values.
Quick Start
# Discover yields on a network ./scripts/find-yields.sh base USDC # Inspect a yield's schema before entering ./scripts/get-yield-info.sh base-usdc-aave-v3-lending # Enter a position (amounts are human-readable) ./scripts/enter-position.sh base-usdc-aave-v3-lending 0xYOUR_ADDRESS '{"amount":"100"}' # Check balances and pending actions ./scripts/check-portfolio.sh base-usdc-aave-v3-lending 0xYOUR_ADDRESS
Scripts
ScriptPurposefind-yields.shDiscover yields by network/tokenget-yield-info.shInspect yield schema, limits, token detailslist-validators.shList validators for staking yieldsenter-position.shEnter a yield positionexit-position.shExit a yield positionmanage-position.shClaim, restake, redelegate, etc.check-portfolio.shCheck balances and pending actions
Enter a Position
Discover yields: find-yields.sh base USDC Inspect the yield: get-yield-info.sh <yieldId> โ read mechanics.arguments.enter Enter: enter-position.sh <yieldId> <address> '{"amount":"100"}' For each transaction: wallet signs โ broadcast โ submit hash โ wait for CONFIRMED
Manage a Position
Check balances: check-portfolio.sh <yieldId> <address> Read pendingActions[] โ each has { type, passthrough, arguments? } Manage: manage-position.sh <yieldId> <address> <action> <passthrough>
Full Lifecycle
Discover โ 2. Enter โ 3. Check balances โ 4. Claim rewards โ 5. Exit
Transaction Flow
After any action (enter/exit/manage), the response contains transactions[]. For EACH transaction: Pass unsignedTransaction to wallet skill for signing and broadcasting Submit the hash โ PUT /v1/transactions/{txId}/submit-hash with { "hash": "0x..." } Poll GET /v1/transactions/{txId} until CONFIRMED or FAILED Proceed to next transaction Every transaction must follow this flow. Example with 3 transactions: TX1: sign โ broadcast โ submit-hash โ poll until CONFIRMED TX2: sign โ broadcast โ submit-hash โ poll until CONFIRMED TX3: sign โ broadcast โ submit-hash โ poll until CONFIRMED unsignedTransaction format varies by chain. See {baseDir}/references/chain-formats.md for details.
API Endpoints
All endpoints documented in {baseDir}/references/openapi.yaml. Quick reference: MethodEndpointDescriptionGET/v1/yieldsList yields (with filters)GET/v1/yields/{yieldId}Get yield metadata (schema, limits, tokens)GET/v1/yields/{yieldId}/validatorsList validatorsPOST/v1/actions/enterEnter a positionPOST/v1/actions/exitExit a positionPOST/v1/actions/manageManage a positionPOST/v1/yields/{yieldId}/balancesGet balances for a yieldPOST/v1/yields/balancesAggregate balances across yields/networksPUT/v1/transactions/{txId}/submit-hashSubmit tx hash after broadcastingGET/v1/transactions/{txId}Get transaction statusGET/v1/networksList all supported networksGET/v1/providersList all providers
References
Detailed reference files โ read on demand when you need specifics. API types and schemas: {baseDir}/references/openapi.yaml โ source of truth for all DTOs, enums, request/response shapes Chain transaction formats: {baseDir}/references/chain-formats.md โ unsignedTransaction encoding per chain family (EVM, Cosmos, Solana, Substrate, etc.) Wallet integration: {baseDir}/references/wallet-integration.md โ Crossmint, Portal, Turnkey, Privy, signing flow Agent conversation examples: {baseDir}/references/examples.md โ 10 conversation patterns with real yield IDs Safety checks: {baseDir}/references/safety.md โ pre-execution checks, constraints
Error Handling
The API returns structured errors with message, error, and statusCode. Read the message. Error shapes are in {baseDir}/references/openapi.yaml. Respect retry-after on 429s.
Add-on Modules
Modular instructions that extend core functionality. Read when relevant. {baseDir}/references/superskill.md โ 40 advanced capabilities: rate monitoring, cross-chain comparison, portfolio diversification, rotation workflows, reward harvesting, scheduled checks
Resources
API Docs: https://docs.yield.xyz API Recipes: https://github.com/stakekit/api-recipes Get API Key: https://dashboard.yield.xyz
Category context
Code helpers, APIs, CLIs, browser automation, testing, and developer operations.
Source: Tencent SkillHub
Largest current source with strong distribution and engagement signals.
Package contents
Included in package
3 Scripts2 Docs1 Config
- SKILL.md
- README.md
- scripts/enter-position.sh
- scripts/exit-position.sh
- scripts/find-yields.sh
- skill.json