Clanker

Before installing or running this skill, consider the following: - Sensitivity of private keys: The scripts expect you to place private keys in ~/.clawdbot/skills/clanker/config.json in plaintext. Do NOT put your mainnet/private funds key there. Prefer a throwaway/test key for experimentation. - Use hardware wallets or remote signing where possible: If you need mainnet deployments, avoid storing raw private keys on disk; instead use a wallet provider, remote signer, or sign transactions offline. - Verify contract addresses and endpoints: The Python helper includes specific Clanker contract addresses and RPC endpoints; verify these against official Clanker documentation (e.g., clanker.world) before broadcasting transactions. Malicious or incorrect contract addresses could lead to loss. - Dependency completeness: The SKILL.md suggests 'pip install web3' but deploy.py also imports eth_abi (eth-abi). Install both packages or review the Python script before running. - Scope and provenance: The skill source/homepage is 'unknown'/none in registry metadata while SKILL.md references https://clanker.world. Lack of a clear upstream source reduces ability to verify authenticity—exercise caution. - Test first on Sepolia: Follow the provided testnet flow and use small amounts of test ETH to validate behavior before any mainnet use. - Run in an isolated environment: Consider running the scripts in a disposable VM/container and inspect logs and network traffic if you want extra assurance. If you want to proceed: create a dedicated ephemeral testnet key, verify the code (deploy.py and clanker.sh) yourself, ensure the config file is created with restrictive permissions (chmod 600), and do not reuse the key for other services. If you require higher assurance, ask the skill author or maintainers for repository/source verification and signed releases.