功能描述

End-to-end Celo development playbook (Feb 2026). Prefer viem for all client/transaction code (native fee currency support via CIP-64). Use thirdweb for wallet connection and React dApps. Foundry for smart contract development. Covers fee abstraction (pay gas in USDC/USDT/USDm), MiniPay Mini Apps, stablecoin integration, and AI agent infrastructure (ERC-8004 trust + x402 payments).

使用说明 (SKILL.md)

Celo Development Skill (viem-first)

Name: Celo Agent Skills
Author: viral-sangani

What this Skill is for

Use this Skill when the user asks for:

Celo dApp UI work (React / Next.js)
Wallet connection + fee currency selection
Transactions paying gas in stablecoins (USDC, USDT, USDm)
MiniPay Mini App development
Smart contract development, testing, and deployment
Stablecoin integration (Mento + bridged)
AI agent infrastructure (ERC-8004 identity/reputation, x402 payments)

Default stack decisions (opinionated)

1. Client SDK: viem first

viem is REQUIRED for fee abstraction (ethers.js/web3.js don't support feeCurrency)
Use viem/celo for Celo-specific transaction serialization
Never use ethers.js for new Celo projects


import { createWalletClient, custom } from "viem"; 

import { celo } from "viem/chains";  



const walletClient = createWalletClient({   

  chain: celo,   

  transport: custom(window.ethereum), 

});

2. UI & Wallets: thirdweb

Use thirdweb SDK for wallet connection and React components
ConnectButton supports 500+ wallets including MiniPay
Built-in support for Celo chains


import { ConnectButton } from "thirdweb/react"; 

import { celo } from "thirdweb/chains";  



\x3CConnectButton client={client} chain={celo} />

3. Fee Abstraction: always offer stablecoin gas

Celo's killer feature: pay gas fees in ERC-20 tokens without paymasters or relayers.

Use adapter addresses for 6-decimal tokens (USDC, USDT) - adapters normalize decimals
Use token addresses directly for 18-decimal tokens (USDm, EURm, REALm) - no adapter needed
Requires viem (ethers.js/web3.js don't support feeCurrency)
Only works with Celo-native wallets (MiniPay) or custom implementations


import { serializeTransaction } from "viem/celo"; 

import { parseGwei, parseEther } from "viem";  



// For 6-decimal tokens (USDC, USDT): use ADAPTER address 

const USDC_ADAPTER = "0x2F25deB3848C207fc8E0c34035B3Ba7fC157602B";  



// For 18-decimal tokens (USDm, EURm): use TOKEN address directly 

const USDM_TOKEN = "0x765DE816845861e75A25fCA122bb6898B8B1282a";  



const serialized = serializeTransaction({   

  chainId: 42220,   

  gas: 21001n,   

  feeCurrency: USDC_ADAPTER, // or USDM_TOKEN for USDm   

  maxFeePerGas: parseGwei("20"),   

  maxPriorityFeePerGas: parseGwei("2"),   

  nonce: 69,   

  to: "0x1234512345123451234512345123451234512345",   

  value: parseEther("0.01"), 

});

4. Smart Contracts: Foundry

Use Foundry (forge, cast, anvil) for all contract development
Fast compilation, powerful testing, built-in fuzzing
Native Celo verification support via Celoscan API


# Install Foundry 

curl -L https://foundry.paradigm.xyz | bash && foundryup  



# Create project 

forge init my-project && cd my-project  



# Deploy to Celo Sepolia 

forge script script/Deploy.s.sol \   

  --rpc-url https://forno.celo-sepolia.celo-testnet.org \   

  --broadcast --verify

5. MiniPay: mobile-first stablecoin UX

Detect MiniPay via window.ethereum?.isMiniPay
Users have stablecoins (USDm, USDC), not CELO
Hide "Connect Wallet" button - connection is implicit
Test via MiniPay Site Tester with ngrok


function isMiniPay(): boolean {   

  return typeof window !== "undefined" &&          

      window.ethereum?.isMiniPay === true; 

}

6. AI Agents: ERC-8004 + x402

For AI agent development on Celo:

ERC-8004: On-chain identity, reputation, and trust verification
x402: HTTP-native micropayments with stablecoins


// Verify agent trust before interaction 

const summary = await reputationRegistry.getSummary(agentId); 

if (summary.averageScore >= 80) {   

  // Make paid request to trusted agent   

  const response = await fetchWithPayment(serviceUrl); 

}

Operating procedure

1. Classify the task layer

| Layer | Tools |

|-------|-------|

| UI/wallet/hooks | viem + thirdweb |

| Scripts/backend | viem directly |

| Smart contracts | Foundry (forge) |

| MiniPay apps | MiniPay detection + stablecoin UX |

| AI agents | ERC-8004 + x402 |

2. Pick the right fee currency approach

| Scenario | Approach |

|----------|----------|

| User has MiniPay | Offer fee currency selection |

| User has MetaMask | Must pay in CELO (no fee abstraction) |

| Server-side/scripts | Always use fee currency with viem |

3. Implement with Celo-specific correctness

Always be explicit about:

Network: Mainnet (42220) vs Sepolia (11142220)
Fee currency: Adapter address (6-decimal) vs token address (18-decimal)
Wallet compatibility: MiniPay supports fee abstraction, MetaMask does not

4. Add tests

Test both CELO and fee currency transactions separately
Test wallet connection with MiniPay detection
For contracts, use forge test with fuzzing
For MiniPay apps, test in Site Tester on real device

5. Deliverables

When implementing changes, provide:

Exact files changed
Commands to install/build/test/deploy
Fee currency addresses used (mainnet vs testnet)
Wallet compatibility notes

Quick reference

Networks

|---------|----------|--------------|----------|

Fee Currency Addresses - Mainnet

Why adapters? Celo's gas calculations use 18 decimals internally. Tokens with different decimals (like USDC/USDT with 6 decimals) need adapter contracts to normalize the decimal conversion. Native Mento stablecoins (USDm, EURm, REALm) are already 18 decimals, so you use their token address directly.

|-------|----------|---------------------|------|

Fee Currency Addresses - Celo Sepolia

|-------|----------|---------------------|------|

Core Protocol Contracts - Mainnet

| Contract | Address |

|----------|---------|

| CELO Token | 0x471EcE3750Da237f93B8E339c536989b8978a438 |

| FeeCurrencyDirectory | 0x15F344b9E6c3Cb6F0376A36A64928b13F62C6276 |

| Registry | 0x000000000000000000000000000000000000ce10 |

Stablecoin Tokens - Mainnet

| Token | Address | Decimals |

|-------|---------|----------|

| USDm | 0x765DE816845861e75A25fCA122bb6898B8B1282a | 18 |

| EURm | 0xD8763CBa276a3738E6DE85b4b3bF5FDed6D6cA73 | 18 |

| USDC | 0xcebA9300f2b948710d2653dD7B07f33A8B32118C | 6 |

| USDT | 0x48065fbbe25f71c9282ddf5e1cd6d6a887483d5e | 6 |

Progressive disclosure (read when needed)

Detailed documentation for each topic is available in the celo-org/agent-skills repository:

Client & Frontend

viem - TypeScript client with fee currency support
wagmi - React hooks for Celo dApps
thirdweb - Full-stack Web3 development
evm-wallet-integration - Wallet connection patterns

Celo Features

fee-abstraction - Pay gas with stablecoins
minipay-integration - MiniPay Mini App development
celo-stablecoins - USDT, USDC, USDm, EURm, BRLm, XOFm, KESm, PHPm, COPm, NGNm, GHSm, GBPm, ZARm, CADm, AUDm, CHFm, JPYm, BRLA, VCHF, VEUR, VGBP, USDGLO, agEURA + COPM
celo-rpc - Blockchain interaction via RPC

Smart Contracts

evm-foundry - Foundry development (recommended)
contract-verification - Celoscan, Blockscout, Sourcify

AI Agent Infrastructure

8004 - ERC-8004 Agent Trust Protocol
x402 - HTTP-native agent payments

DeFi & Bridging

celo-defi - DeFi protocol integration
bridging - Asset bridging to/from Celo

Scaffolding

celo-composer - Project templates and scaffolding

Official Documentation

Token Contracts - All token addresses
Core Contracts - Protocol contract addresses
Fee Currency - Fee abstraction guide
MiniPay - Mini App development

Why Celo?

Fee abstraction: Pay gas in stablecoins without paymasters
Sub-second finality: ~1 second block times
Low fees: Gas costs under $0.001
Mobile-first: MiniPay with 12.6M activations
AI-native: ERC-8004 trust + x402 payments built for agents
Stablecoin ecosystem: Native USDT, USDC, USDm, EURm, BRLm, XOFm, KESm, PHPm, COPm, NGNm, GHSm, GBPm, ZARm, CADm, AUDm, CHFm, JPYm, BRLA, VCHF, VEUR, VGBP, USDGLO, agEURA + COPM

安全使用建议

This collection is a coherent Celo development playbook and appears benign, but take these precautions before using any instructions: - Secrets: Examples show using PRIVATE_KEY and API keys. Never paste real private keys into example files or share them in chat. Use environment variables, secure secret stores, or hardware wallets, and rotate keys after testing. - Deployment verification: Verification and deployment commands require private keys and API keys; only run them from a trusted environment (CI with secrets configured) — not from a shared shell. - Remote installers: The docs include curl | bash installer lines (Foundry). Verify the official source and the script contents before piping to sh; prefer package-managed or vetted installers when possible. - Addresses & endpoints: The skill lists many token addresses and RPC endpoints. Independently verify any token address or adapter address on block explorers before sending funds. - Test first: Use Sepolia/testnet addresses and faucets for development. Confirm behavior on testnet before mainnet. If you plan to let an agent act on this guidance autonomously, restrict what secrets it can access and review any commands it proposes before execution. If you want, I can point out every place in the files where a secret, private key, or potentially risky command appears so you can audit them quickly.

功能分析

Type: OpenClaw Skill Name: celo-agent-skills Version: 1.0.0 The skill bundle is classified as suspicious due to the inclusion of inherently risky, albeit common, development practices. Specifically, the `celo-dev` and `evm-foundry` skills instruct the agent to execute `curl -L https://foundry.paradigm.xyz | bash` for Foundry installation, which involves piping remote script output directly to a shell. Additionally, the `celo-composer` and `minipay-integration` skills use `npx @celo/celo-composer@latest create`, which executes a remote package. The `minipay-integration` skill also suggests using `ngrok http 3000` to expose a local development server publicly, although it includes security warnings. While these actions are standard in a developer context and no clear malicious intent (like data exfiltration or persistence) is observed, they represent high-risk capabilities that could be exploited if the remote sources were compromised or if the agent were to disregard the security warnings.

能力评估

✓ Purpose & Capability

The name/description (Celo development playbook) matches the actual contents: extensive guidance for viem, thirdweb, Foundry/forge/cast, stablecoins, MiniPay, contract verification, and agent payments. Examples, RPC endpoints, and token addresses are Celo-specific and expected for this purpose.

ℹ Instruction Scope

The SKILL.md files are developer-facing how-to instructions and remain within the stated domain (dApp UI, wallets, fee abstraction, smart contracts, verification). They include code snippets and CLI examples that reference private keys, env vars, and commands to deploy/verify contracts — appropriate for a dev playbook but potentially sensitive if followed without care. No instructions tell the agent to read unrelated system files or exfiltrate data to unexpected endpoints.

⚠ Install Mechanism

The skill itself has no install spec (instruction-only), which is low risk. However, the instructions recommend running common developer installers in-line — e.g., curl -L https://foundry.paradigm.xyz | bash && foundryup — which downloads and executes a remote script. That is a standard Foundry installation approach but is a high-risk action if executed blindly; users should verify the source before running such commands.

ℹ Credentials

The skill does not request environment variables or credentials at install time, which is good. The documentation repeatedly shows using PRIVATE_KEY, ETHERSCAN_API_KEY, NEXT_PUBLIC_WALLETCONNECT_PROJECT_ID, and examples that embed '0xYourPrivateKey' or call vm.envUint('PRIVATE_KEY'). These are expected for deployment and verification workflows, but they are sensitive — the skill's declared requirements omit them, so users must supply secrets manually. This is proportionate to the purpose but worth highlighting as sensitive.

✓ Persistence & Privilege

always is false and user-invocable is true. The skill is instruction-only and does not request persistent privileges or attempt to modify other skills or system-wide settings.

版本历史

v1.0.0

Initial release of celo-agent-skills v1.0.0: - Provides a complete Celo development playbook, focusing on end-to-end application and smart contract workflows. - Enforces viem as the client SDK for all Celo transactions, enabling native fee abstraction and stablecoin fee payments. - Recommends thirdweb for wallet connection and React dApp UI, with MiniPay support. - Details Foundry usage for contract development, testing, deployment, and verification. - Covers MiniPay Mini App development, stablecoin integration, and Celo's adapter/token fee currency system. - Includes guidance and examples for integrating AI agent infrastructure with ERC-8004 (identity/trust) and x402 (micropayments).

元数据

Slug celo-agent-skills

版本 1.0.0

许可证 —

累计安装 0

当前安装数 0

历史版本数 1

常见问题

Celo Agent Skills 是什么？

End-to-end Celo development playbook (Feb 2026). Prefer viem for all client/transaction code (native fee currency support via CIP-64). Use thirdweb for wallet connection and React dApps. Foundry for smart contract development. Covers fee abstraction (pay gas in USDC/USDT/USDm), MiniPay Mini Apps, stablecoin integration, and AI agent infrastructure (ERC-8004 trust + x402 payments). 它是一个面向 Claude Code / OpenClaw 的 AI Agent Skill 插件，目前累计下载 1216 次。

如何安装 Celo Agent Skills？

在 OpenClaw 或 Claude Code 对话框中运行命令「/install celo-agent-skills」即可一键安装，无需额外配置。

Celo Agent Skills 是免费的吗？

是的，Celo Agent Skills 完全免费（开源免费），可自由下载、安装和使用。

Celo Agent Skills 支持哪些平台？

Celo Agent Skills 跨平台运行，可在任意部署了 OpenClaw / Claude Code 的环境中使用（cross-platform）。

谁开发了 Celo Agent Skills？

由 viral-sangani（@viral-sangani）开发并维护，当前版本 v1.0.0。

Celo Agent Skills