aap-agent-bounty

What This Skill Does

The aap-agent-bounty skill is a specialized verification-first tool designed for users interacting with the AAP bounty program on the Base network. It serves as a secure, non-custodial middleware that bridge the gap between proof verification and on-chain signaling. Rather than requiring users to manually manage raw hex data or transaction construction, the agent handles the heavy lifting by interfacing with local binaries like gh for identity validation and cast for blockchain interactions. The skill follows a strict verification-first architecture: it first audits the proof status and ensures all payload parameters are correctly formatted, then pauses for an explicit broadcast confirmation. This design prevents accidental transactions and ensures that every interaction is intentional. By utilizing a 0 ETH transfer mechanism, it acts as a 'proof signal' to the target smart contract, confirming eligibility without exposing the user to unnecessary financial risk. It is strictly scoped to respect the security boundaries of the user's environment, meaning it never asks for raw private keys or mnemonics.

Installation

To integrate this skill into your OpenClaw environment, execute the following command in your terminal: clawhub install openclaw/skills/skills/alphac007/aap-agent-bounty

Ensure that your environment variables include BASE_RPC_URL and that you have the gh and cast binaries installed and available in your PATH. If you are operating in a CI/CD or headless environment, you may optionally provide a GH_TOKEN to maintain authentication persistence.

Use Cases

• Automated Eligibility Verification: Use the agent to automatically check if your GitHub or X activity meets the specific criteria for the AAP program.
• Risk-Free Proof Submission: Submit bounty claims via 0 ETH transactions, ensuring your claim is logged on-chain without the complexity of interacting directly with bytecode.
• Identity Binding: Link your GitHub username and X handle to your wallet address securely within the transaction metadata payload.

Example Prompts

1. "Verify my eligibility for the current AAP bounty using my GH: username and X: @handle and show me the pending payload."
2. "Check the status of my proof for TRUMP_100 and prepare the transaction but do not broadcast yet."
3. "Broadcast my bounty claim for TRUMP_100. Confirming: confirm_broadcast=true. I have my wallet signer ready."

Tips & Limitations

• Hard Execution Gate: The skill will NEVER broadcast a transaction unless the input explicitly includes confirm_broadcast: true. If you are missing this, the skill will default to a pending status.
• Security: The skill relies on your local gh auth and cast signer configuration. If these are not configured, the skill will return a signer_context_missing or github_auth_missing error. Always ensure your environment is configured before calling the skill.
• Zero-Value Transactions: Remember that while these claims are 0 ETH, they still require gas fees in native Base ETH. Ensure your wallet is funded for gas.