Skip to content

CosmosContracts/juno-network-skill

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 

History

3 Commits
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 

Repository files navigation

juno-network-skill

A Claude Code skill that makes any agent operational on the Juno Network blockchain — a CosmWasm-enabled Cosmos chain.

Given access to this skill, an agent can:

  • Read chain state (bank balances, staking, DAO governance, CosmWasm contract queries)
  • Sign and broadcast transactions
  • Store, instantiate, and call CosmWasm contracts
  • Drive DAO DAO governance, including the full agent-mandate stack (sub-DAOs, VetoConfig timelocks, cw-filter message-policy)
  • Install junod, pick the right RPC, set sensible gas defaults

The skill is mainnet-first by design — Juno is an experimental chain and the canonical operating environment is juno-1. uni-7 testnet is documented as the alternative for the rare cases where testnet is genuinely useful.

Install

Claude Code's .claude/skills/ convention picks up project-local skills automatically. To add this skill to a project:

cd <your-project>/.claude/skills
git submodule add https://github.com/CosmosContracts/juno-network-skill juno-network

Or clone it standalone and symlink:

git clone https://github.com/CosmosContracts/juno-network-skill /path/to/your/skills/juno-network

The agent loads juno-network/SKILL.md and follows its decision tree to the relevant reference.

Contents

SKILL.md                 orchestrator: when to trigger, decision tree, defaults, bundled-scripts table
references/
  chain.md               RPCs, chain-ids, denoms, IBC channels, gas
  install.md             junod install + sha256 verification
  keys.md                keyring backends, generate/import, phase guidance, mnemonic discipline
  transactions.md        tx anatomy, dry-run, broadcast modes, common error codes
  queries.md             read-only patterns: bank / staking / gov / wasm / ibc
  cosmwasm.md            store / instantiate / instantiate2 / execute / query / migrate
  dao-dao.md             DAO DAO ops: interact, create, member operations + end-to-end runbook + cw-filter mandates
scripts/
  instantiate-subdao.sh  parameterized 3-contract sub-DAO instantiate with VetoConfig (enforces timelock/voting-period unit-match)
  propose-bank-send.sh   bank.send proposal against a dao-proposal-single module
  verify-tx.sh           poll tx for inclusion, extract events (contract addresses, proposal_id, transfer, code_id)
evals/
  evals.json             6 test cases (5 unit-y + 1 end-to-end)

The references load progressively — SKILL.md is small (~180 lines) and routes the agent to specific references based on the task shape. The references can run long but the agent loads only what's needed.

Defaults

Setting Value
Network juno-1 mainnet
RPC https://juno-rpc.publicnode.com:443
junod version v29.x
Gas --gas auto --gas-adjustment 1.4 --gas-prices 0.075ujuno
Keyring backend test for hot/low-stakes (sub-DAO bounds blast radius); os/file/signer-service for treasury

See references/chain.md for testnet alternatives and additional providers.

What's in scope

  • The Juno chain (mainnet + testnet) and its native denom ujuno
  • CosmWasm operations on Juno
  • DAO DAO governance on Juno (the dominant on-chain DAO platform here)
  • Agent-mandate patterns: sub-DAOs, VetoConfig, cw-filter, the forward-looking dao-proposal-wavs integration

What's out of scope

  • Other Cosmos chains (Osmosis, Neutron, Cosmos Hub, etc.) — general SDK patterns transfer but defaults and code IDs don't
  • Validator selection (opinion territory)
  • IBC cross-chain ops beyond enough to identify denoms and channels (deeper IBC tooling is its own concern)

Verifying examples

Examples in references/dao-dao.md and the scripts encode chain-side constraints — most notably the TimelockDurationUnitMismatch rule (timelock_duration and max_voting_period must share unit), the cw-jsonfilter grammar, and the required delegation_module: null field on recent dao-proposal-single versions. These are verified against contract source in DA0-DA0/dao-contracts (v2.7.0 at time of writing). If a contract upgrade changes any of these, the skill needs to be re-verified — see CHANGELOG.md.

Mainnet code IDs (pinned to dao-contracts v2.7.0): DaoDaoCore 4862, DaoVotingCw4 4872, Cw4Group 1992, DaoProposalSingle 4869. Cross-check against dao-dao-ui/packages/utils/constants/codeIds.json before high-stakes use.

License

MIT — see LICENSE.

Origin

Authored 2026-05-15 → 16 across three eval-driven iterations by Juno AI working with Jake Hartnell. The skill encodes a synthesis of Juno chain operational knowledge, DAO DAO contract patterns, and agent-mandate primitives developed across the broader Juno workspace. See CHANGELOG.md for the iteration arc.

Contributing

Issues and PRs welcome at https://github.com/CosmosContracts/juno-network-skill.

If you're proposing a change to an example or a contract-shape assertion, please cite the upstream source (dao-contracts, dao-dao-ui, juno) — the lesson from the iteration history is that plausible-looking syntax invented from memory is the most common bug class.

About

A SKILL.md for your Juno agent.

Resources

License

Stars

3 stars

Watchers

0 watching

Forks

Packages

 
 
 

Contributors

Languages