cosmos_skill

This skill helps you manage Cosmos ATOM transactions, IBC transfers, staking, and cross-chain navigation with clear, actionable guidance.
  • Python

2.5k

GitHub Stars

2

Bundled Files

2 months ago

Catalog Refreshed

4 months ago

First Indexed

Readme & install

Copy the install command, review bundled files from the catalogue, and read any extended description pulled from the listing source.

Installation

Preview and clipboard use veilstrat where the catalogue uses aiagentskills.

npx veilstrat add skill openclaw/skills --skill cosmos

  • _meta.json269 B
  • SKILL.md4.0 KB

Overview

This skill helps you navigate Cosmos ATOM transactions, IBC transfers, staking, validators, and cross-chain DeFi. It provides practical checks and guidance to avoid common mistakes, secure funds, and use wallets and bridges correctly. The focus is on safe transfers, staking flows, and choosing reliable validators across the Cosmos ecosystem.

How this skill works

The skill inspects destination chain prefixes, verifies active IBC channels and token wrapping status, and checks common transaction failure modes like account-not-found and sequence mismatches. It guides on staking actions (delegate, redelegate, unbond), estimates gas and fee tokens per chain, and recommends wallet and hardware setups. It also highlights governance and airdrop considerations tied to staking behaviour.

When to use it

  • Before sending tokens cross-chain via IBC to verify channel and address prefix.
  • When choosing a validator to delegate ATOM or other Cosmos tokens.
  • If a transaction fails with sequence mismatch, account not found, or stuck IBC transfer.
  • When preparing to participate in on-chain governance or claim an airdrop.
  • When configuring Keplr/Leap/Cosmostation or connecting a Ledger device.

Best practices

  • Always verify the bech32 prefix matches the destination chain (e.g., cosmos1 vs osmo1).
  • Confirm the IBC channel is active and check whether tokens will be wrapped on the destination chain.
  • Use hardware wallets (Ledger) for large balances and revoke unused wallet permissions frequently.
  • Delegate to multiple smaller validators for decentralization and check slashing history and uptime.
  • Allow time for relayers on IBC transfers; retry via another path or channel if a transfer stalls.

Example use cases

  • Send ATOM from Cosmos Hub to Osmosis and confirm you understand wrapped IBC ATOM vs native tokens.
  • Switch delegation between validators instantly with redelegation to avoid 21-day unbonding.
  • Resolve a stuck IBC transfer by checking relayer status and channel activity.
  • Prepare to vote on a Cosmos Hub governance proposal and calculate voting power from staked ATOM.
  • Set up Keplr with Ledger and verify addresses across multiple Cosmos chains before transacting.

FAQ

Many chains represent incoming assets as IBC-wrapped tokens. Verify the token denom and channel; wrapped tokens are expected behavior and still represent your original asset.

Can I use the same wallet seed across all Cosmos chains?

Yes. One seed generates addresses for each chain, but each chain uses a different bech32 prefix and derivation path, so always confirm the correct address format.

Built by
VeilStrat
AI signals for GTM teams
© 2026 VeilStrat. All rights reserved.All systems operational
cosmos skill by openclaw/skills | VeilStrat