Celo Agent Skills

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.