kaia-skills

Provides authoritative Kaia blockchain guidance for developers and corrects outdated network assumptions.

3|Updated Apr 15, 2026
One-click install
npx skills add https://github.com/Pieverse-Eng/purrfect-skills --skill kaia-skills
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: kaia-skills
Source: https://github.com/Pieverse-Eng/purrfect-skills/tree/main/kaia-skills
Command: npx skills add https://github.com/Pieverse-Eng/purrfect-skills --skill kaia-skills

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Kaia-skills corrects outdated or incorrect knowledge about the Kaia network and provides authoritative, Kaia-specific development and operational guidance so agents and developers avoid costly mistakes when building on Kaia.

Core Features & Use Cases

  • Network correctness: Provides verified chain IDs, RPC endpoints, and mainnet/testnet distinctions to prevent misconfiguration.
  • Transaction & account guidance: Explains Kaia-native transaction types, fee delegation flows, gas abstraction, role-based account keys, and required dual-signature patterns.
  • Ecosystem & tooling: Recommends maintained SDKs, verified system contract addresses, MEV auction mechanics, and migration notes for hardforks to support deployments and auditing.
  • Use Case: A developer migrating a dApp from legacy Klaytn to Kaia can use these instructions to update gas units, replace deprecated SDKs, and adapt signing flows for fee-delegated transactions.

Quick Start

Ask the agent to produce a Kaia developer checklist that lists RPC endpoints, chain IDs, recommended SDK packages, verified system contract addresses, and the correct flow for fee delegation and gas abstraction.

Frequently Asked Questions about kaia-skills

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I implement fee delegation for Kaia blockchain transactions?

To implement fee delegation on Kaia, you must use Kaia-native transaction types that support dual-signature patterns, allowing a fee payer to sign separately from the sender. This requires specific transaction type formatting and correct signature flows.

What are the correct chain IDs and RPC endpoints for Kaia mainnet and testnet?

Correct Kaia network configuration requires verified chain IDs and RPC endpoints to distinguish between mainnet and testnet environments. Using outdated assumptions can cause deployment failures, so verified network parameters must be applied to prevent misconfiguration.

How do I migrate a dApp from legacy Klaytn to Kaia?

Migrating a dApp from legacy Klaytn to Kaia involves updating gas units, replacing deprecated SDK packages, and adapting signing flows for fee-delegated transactions. You must apply verified system contract addresses and hardfork migration notes.

How does Kaia account key management and role-based keys work?

Kaia account key management supports role-based keys, allowing different keys for updating, fee payment, and transaction execution. This enables granular access control but requires understanding specific signature requirements for each transaction type.

What SDKs should I use for Kaia smart contract development?

For Kaia smart contract development, you should use maintained SDKs specifically recommended for the current network. Deprecated legacy Klaytn SDKs must be replaced to ensure compatibility with current transaction types and system contract addresses.

What are the limitations or precautions when interacting with Kaia MEV auctions?

Interacting with Kaia MEV auctions requires understanding specific auction mechanics and verified system contract addresses. Incorrect network assumptions or outdated gas pricing models can lead to failed bids or transaction misconfiguration.