@axon-chain/axon-skills
v0.2.0
Published
Installable Axon skill bundles that teach AI agents how to handle Axon mainnet wallet and validator workflows.
Maintainers
Readme
@axon-chain/axon-skills
Install official Axon skill bundles for AI agents with npx.
This package is not a node launcher, wallet app, or SDK. It is a distribution package that copies curated Axon skill folders into agent skill roots so tools such as OpenClaw can discover them and load them at the right time.
What Axon Is
Axon is the Axon Chain mainnet project. The official GitHub README describes it as a general-purpose blockchain for AI agents with:
- an independent L1 network
- full EVM compatibility
- agent-native on-chain capabilities
- validator and Agent participation flows
- wallet, RPC, SDK, and contract integration surfaces
For this package, the important operating facts are:
- node-facing Cosmos chain ID:
axon_8210-1 - wallet-facing EVM chain ID:
8210 - native token:
AXON - public JSON-RPC:
https://mainnet-rpc.axonchain.ai/
This package exists so an agent can answer three questions without first opening the Axon repository:
- What is Axon?
- Which Axon workflow is this request asking for?
- Which official Axon resources should I use next?
After installation, the agent gets:
axon-validator-node: an operator playbook for Axon mainnet validator, Agent-validator, and sync-node workaxon-mainnet-user: a user-and-Agent playbook for Axon mainnet users, non-validator Agents, balances, transfers, and public RPC reads
Install this package when you want the agent to understand:
- what Axon task it is handling
- which skill it should trigger
- which chain IDs, RPC endpoints, and guardrails apply
- which reference files it should read next for exact steps
What The Agent Can Do
With these installed skills, an agent can:
- explain what Axon is at a high level and separate wallet flows from validator flows
- configure Axon in MetaMask or other EVM wallets with the correct chain ID and RPC
- inspect chain state through the public JSON-RPC endpoint
- guide validator and sync-node bootstrap using the official public scripts
- help check funding, sync state,
create-validator, Agent registration, and heartbeat flows - point builders to the official SDKs, contract interfaces, release artifacts, and mainnet files
Role Guide
This package is now structured around three user intents:
- ordinary users who only need wallet access, transfers, balances, and public RPC usage
- users who want to become an active Agent and understand how Agent rewards work
- users who want to become a validator and understand validator duties and validator-side rewards
The package still installs two skills, but each skill owns a clear scope:
axon-mainnet-usercovers ordinary-user flows and non-validator active-Agent flowsaxon-validator-nodecovers validator and agent-validator flows
Ordinary Users: How To Use Axon
Ordinary users do not need to run a node or become a validator.
They typically need to:
- add Axon mainnet to an EVM wallet with chain ID
8210 - hold
AXONfor transfers and gas - check balances and send transfers
- inspect public chain state through
https://mainnet-rpc.axonchain.ai/ - connect EVM applications that support Axon mainnet
This path should trigger axon-mainnet-user.
Active Agent: Lifecycle And Reward Logic
Users who want to participate as active Agents without validator duties should stay in axon-mainnet-user, because the user skill now includes dedicated Agent guidance for:
- how to register an Agent
- how to keep the Agent online and active
- what causes reputation to rise or fall
- how Agent-side rewards are split between reputation rewards and contribution rewards
- when stake matters for non-validator Agent earnings
At a high level:
- a registered Agent is not the same thing as a validator
- a non-validator Agent can still earn Agent-side rewards
- becoming an active Agent does not require validator duties
Validators: Duties And Reward Logic
Users who want to become validators should also use axon-validator-node.
That skill now separates:
- the operational path to become a validator
- validator rights and obligations
- the extra steps to become an Agent validator
- validator mining and reward mechanics
At a high level:
- validators must be funded, synced, and created on chain before operating
- validators must protect signing keys and avoid downtime and double-signing
- validator-side rewards depend on proposer selection and validator-pool distribution
- Agent validators additionally depend on heartbeat freshness, reputation, and stake-weighted mining power
Included skills
validator: installsaxon-validator-nodefor validator, Agent-validator, and sync-node operationsuser: installsaxon-mainnet-userfor wallet setup, active-Agent flows, balances, transfers, and public RPC usageall: installs both skills
Install
npx @axon-chain/axon-skills install validator
npx @axon-chain/axon-skills install user
npx @axon-chain/axon-skills install allDefault installs copy skills into both agent roots:
${OPENCLAW_STATE_DIR:-~/.openclaw}/skills${AGENTS_SKILLS_DIR:-${AGENTS_HOME:-~/.agents}/skills}
Repeat installs replace the packaged skill folders in place so updates are easy to roll out.
Commands
npx @axon-chain/axon-skills list
npx @axon-chain/axon-skills install validator
npx @axon-chain/axon-skills install user
npx @axon-chain/axon-skills install all
npx @axon-chain/axon-skills install all --dry-run
npx @axon-chain/axon-skills install validator --dest /path/to/skillsHow Agents Use It
The installed folders are normal skill folders with SKILL.md entrypoints and bundled references. An agent reads the skill metadata to decide when to trigger it, then reads the body and reference files to answer Axon-specific requests safely.
In practice:
- wallet, public RPC, Agent registration, active-Agent, and Agent-reward requests should trigger
axon-mainnet-user - validator, sync, recovery, validator-economics, and agent-validator requests should trigger
axon-validator-node - the package gives the agent domain rules and routing, not a running service
Official GitHub References
Use these as the source of truth when more detail is needed:
- Project overview and mainnet facts: github.com/axon-chain/axon/blob/main/README.md
- Latest releases: github.com/axon-chain/axon/releases/latest
- Mainnet genesis: github.com/axon-chain/axon/blob/main/docs/mainnet/genesis.json
- Mainnet bootstrap peers: github.com/axon-chain/axon/blob/main/docs/mainnet/bootstrap_peers.txt
- Validator startup script: github.com/axon-chain/axon/blob/main/scripts/start_validator_node.sh
- Sync-node startup script: github.com/axon-chain/axon/blob/main/scripts/start_sync_node.sh
- TypeScript SDK: github.com/axon-chain/axon/tree/main/sdk/typescript
- Python SDK: github.com/axon-chain/axon/tree/main/sdk/python
- Solidity interfaces and precompile bindings: github.com/axon-chain/axon/tree/main/contracts/interfaces
- Agent heartbeat daemon: github.com/axon-chain/axon/blob/main/tools/agent-daemon/README_EN.md
Verify
openclaw skills listIf OpenClaw is not installed on the current machine, inspect the installed skill folders directly under the target roots and confirm SKILL.md exists in each installed directory.
