AI-bounty-skill
A public “AI bounty claim” agent skill intended to help users claim AI bounty on the aelf tDVV mainnet via RewardClaimContract, supporting two routes: EOA (Claim()) and AA/CA (ManagerForwardCall -> reward.ClaimByPortkeyToCa(Hash ca_hash)). It provides routing, account-choice guidance, and operational steps intended to be followed by an AI agent.
Score Breakdown
⚙ Agent Friendliness
🔒 Security
No direct evidence of secure coding practices (dependency lists, CVE posture, or secret-handling implementation) is present in the provided excerpt. The skill emphasizes not using exchange/custodial addresses and to use local wallet context, which can reduce certain custody risks. However, there is no documented API-level auth, scope model, or secret storage guidance, and no explicit discussion of replay protection, signature handling, or idempotency/claim-state safety.
⚡ Reliability
Best When
When the user wants a step-by-step agent-guided process for aelf tDVV AI bounty claims and has compatible local EOA/AA/CA context (e.g., via Portkey skills).
Avoid When
When you need an audited, executable SDK/API with formal contracts for the claim steps (the repository content shown is instruction-based, and detailed on-chain/API behavior is not fully evidenced here).
Use Cases
- • Claiming aelf AI bounty on tDVV using EOA flow (Claim())
- • Claiming aelf AI bounty on tDVV using AA/CA Portkey route (ManagerForwardCall -> ClaimByPortkeyToCa)
- • Guiding an agent through choosing the correct local wallet/account context and resolving needed hashes/addresses
Not For
- • General-purpose wallet management unrelated to the specific AI bounty claim campaign
- • Providing custody/exchange support (the README explicitly warns against exchange/custodial addresses)
- • Acting as a standalone payment/claim API service (it’s a skill/guidance workflow)
Interface
Authentication
Authentication is not described as an API auth mechanism; instead, the workflow relies on user-controlled wallet/account context (local EOA/AA/CA) and signing/forward-call capabilities provided by Portkey agent skills. No explicit scope model is documented in the provided README excerpt.
Pricing
No pricing information in the provided repository metadata/README excerpt.
Agent Metadata
Known Gotchas
- ⚠ Must choose exactly one branch/route (EOA vs AA/CA) and follow matching flow/examples.
- ⚠ Do not send exchange/custodial addresses; use local account context.
- ⚠ Prefer AA/CA as default/fallback due to smoother gas experience and higher reward amount (per README).
- ⚠ Do not infer method availability from /api/contract/contractViewMethodList; use alternative introspection if needed.
- ⚠ Normalize contract address formats for node introspection endpoints rather than sending wrapped address strings directly.
- ⚠ Validate RPC reachability via chainStatus, not by requesting the RPC root URL.
- ⚠ If the submission returns txId, include it and the aelfscan tDVV tx link.
Alternatives
Full Evaluation Report
Comprehensive deep-dive: security analysis, reliability audit, agent experience review, cost modeling, competitive positioning, and improvement roadmap for AI-bounty-skill.
AI-powered analysis · PDF + markdown · Delivered within 30 minutes
Package Brief
Quick verdict, integration guide, cost projections, gotchas with workarounds, and alternatives comparison.
Delivered within 10 minutes
Score Monitoring
Get alerted when this package's AF, security, or reliability scores change significantly. Stay ahead of regressions.
Continuous monitoring
Scores are editorial opinions as of 2026-03-30.