contract-learner

Generate reusable contract interaction skills from verified on-chain ABIs.

181|10|Updated Mar 2, 2026
One-click install
npx skills add https://github.com/keypo-us/keypo-cli --skill contract-learner
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: contract-learner
Source: https://github.com/keypo-us/keypo-cli/tree/main/skills/contract-learner
Command: npx skills add https://github.com/keypo-us/keypo-cli --skill contract-learner

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It turns a verified smart contract into a reusable skill that helps agents interact with it safely and consistently through keypo-wallet.

Core Features & Use Cases

  • ABI-based analysis: Fetches the verified ABI, separates read and write functions, and builds accurate call instructions from the contract's real interface.
  • Proxy-aware support: Detects common proxy patterns, follows the implementation when needed, and still keeps the proxy address as the execution target.
  • Use Case: A developer can provide a deployed contract address and chain, then receive a complete skill file with function groups, calldata encoding guidance, and verification steps for repeatable use.

Quick Start

Ask the assistant to generate a contract interaction skill for a verified EVM address on your target chain so it can produce a ready-to-use SKILL.md for keypo-wallet.

Frequently Asked Questions about contract-learner

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

FAQPage Schema
How do I generate a reusable skill from a verified smart contract ABI?

Generating a reusable skill from a verified ABI requires a deployed EVM contract address and target chain. The skill fetches the verified ABI, separates read and write functions, and outputs a ready-to-use SKILL.md with calldata encoding guidance.

Can I interact with proxy contracts using Etherscan ABI verification?

Yes, you can interact with proxy contracts because the skill detects common proxy patterns and follows the implementation contract to fetch the correct ABI. It maintains the proxy address as the execution target for accurate calldata encoding.

What tools do I need to encode calldata and validate deployed EVM contracts?

Encoding calldata and validating deployed EVM contracts requires Foundry cast, an Etherscan API key, and chain-specific RPC access. These dependencies fetch metadata, encode function calls, and validate the contract interface.

How does proxy-aware workflow handle payable functions in smart contracts?

Proxy-aware workflows handle payable functions by validating the contract interface from the fetched ABI and building specific call instructions. The generated skill accurately groups read, write, and payable functions to ensure safe keypo-wallet execution.

Does this approach support generating interaction skills for any EVM chain?

Generating interaction skills supports any EVM chain provided you have chain-specific RPC access and a verified contract ABI on Etherscan. It applies to deployed EVM contracts needing read, write, and payable function handling.