Loading...
Loading...
Found 3 Skills
Use when the user mentions staking HAEDAL, locking, extending lock, claiming rewards, decay, or operating VeHaedal on Haedal Protocol (a DeFi ecosystem on SUI). Trigger phrases: "stake haedal", "lock haedal", "extend lock", "claim rewards from haedal", "unlock/redeem haedal", "add to stake", "start decay", "stop decay", "vehaedal". This skill calls https://skillsapi.haedal.xyz/api/v1/vehaedal/* via curl POST. add_stake and claim_rewards* need only signerAddress (+ amount/periods); add_to_existing_stake, extend_existing_lock, start_decay, stop_decay, unstake_and_claim require vehaedalObj — fetch via get_vehaedal_list(address), present the list with current_amount/locked_amount/is_decaying/lock_end_time to the user, then use their chosen objectId. All amounts are human-readable. On HTTP 200 returns txBytes (base64); on non‑200 returns msg.
Use when the user mentions staking WAL, withdrawing hawal, claiming rewards, or operating haWAL on Haedal Protocol (a DeFi/LST protocol on SUI). Trigger phrases: “stake hawal”,"stake hawal", "withdraw hawal", "withdraw wal","instant withdraw hawal","instant withdraw wal","claim hawal rewards","claim wal rewards" . This skill calls https://skillsapi.haedal.xyz/api/v1/hawal/* via curl POST. On HTTP 200 returns txBytes (base64); on non‑200 returns msg.
Helps Claude Code understand Sui blockchain's BCS (Binary Canonical Serialization) encoding, providing usage guidelines and examples for primitive types, composite types, Sui-specific types, serialization patterns, and transformation support. Use when working with BCS serialization in Sui development or when the user mentions BCS, binary serialization, or Move data encoding.