Skip to main content
The Initia Appchain Dev skill is a skill that teaches AI coding agents how to build on Initia. Once installed, your agent can help with:
  • Chain deployment using the Weave CLI
  • Smart contract development across all supported VMs
  • Frontend integration including using InterwovenKit

Installation

Using skills.sh

Manual Installation

For a project-local install:
For a custom destination:

Verify Installation

You should see one skill named initia-appchain-dev.

What the Skill Covers

The skill provides reference material organized by layer:

skill.md

The Initia docs also provide a skill.md file at docs.initia.xyz/skill.md. This is a lightweight skill file that teaches AI agents how to work with the documentation site itself. To add it:

Example Prompts

Once the skill is installed, try prompts like:
  • “Scaffold an EVM contract on Initia and add an oracle read function.”
  • “Set up InterwovenKit providers in my Next.js app and implement wallet connect.”
  • “Create a weave launch config for a testnet EVM rollup.”
  • “My rollup is not producing blocks. Help me debug it step by step.”
  • “Convert this 0x... address to Initia bech32 and add it to genesis accounts.”

Reference Material Included

The skill bundles references that your agent reads on demand:
  • Common tasks — funding, address conversion, token precision
  • Contracts — Move / Wasm / EVM development guides
  • Frontend (InterwovenKit) — provider setup, hooks, transactions
  • Frontend (EVM JSON-RPC) — wagmi + viem integration
  • End-to-end recipes — full workflows from contract to frontend
  • Runtime discovery — auto-detecting chain ID, VM, endpoints
  • Weave CLI commands — complete CLI reference
  • Rollup config schema — launch configuration format
  • Troubleshooting — error diagnosis and recovery

Contributing

The skill repository is open source.
  1. Fork the initia-labs/agent-skills repository
  2. Edit the relevant reference files in the skill/references/ directory
  3. Run the quality checks to validate your changes:
  4. Submit a pull request with a description of what you changed and why