{"id":"aelf-hzz780-ai-bounty-skill","name":"AI-bounty-skill","homepage":null,"repo_url":"https://github.com/aelf-hzz780/AI-bounty-skill","category":"devtools","subcategories":[],"tags":["aelf","agent-skill","blockchain","reward-claim","portkey","wallet","eoa","aa","ca"],"what_it_does":"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.","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)"],"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).","alternatives":["Manually calling the relevant aelf smart contract methods (after verifying method availability on-chain)","Using Portkey’s EOA and CA agent skills directly for the underlying signing/forward-call mechanics","A custom integration that directly constructs and signs transactions for RewardClaimContract"],"af_score":30.5,"security_score":37.0,"reliability_score":23.8,"package_type":"skill","discovery_source":["openclaw"],"priority":"high","status":"evaluated","version_evaluated":null,"last_evaluated":"2026-03-30T13:52:21.316244+00:00","interface":{"has_rest_api":false,"has_graphql":false,"has_grpc":false,"has_mcp_server":false,"mcp_server_url":null,"has_sdk":false,"sdk_languages":[],"openapi_spec_url":null,"webhooks":false},"auth":{"methods":["Portkey EOA skill integration (implied for EOA flow)","Portkey CA skill integration (implied for AA/CA flow)","Wallet manager signer for AA/CA forwarding (manager signer -> CA.ManagerForwardCall)"],"oauth":false,"scopes":false,"notes":"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":{"model":null,"free_tier_exists":false,"free_tier_limits":null,"paid_tiers":[],"requires_credit_card":false,"estimated_workload_costs":null,"notes":"No pricing information in the provided repository metadata/README excerpt."},"requirements":{"requires_signup":false,"requires_credit_card":false,"domain_verification":false,"data_residency":[],"compliance":[],"min_contract":null},"agent_readiness":{"af_score":30.5,"security_score":37.0,"reliability_score":23.8,"mcp_server_quality":0.0,"documentation_accuracy":55.0,"error_message_quality":null,"error_message_notes":"No structured error schema is documented; guidance is mostly behavioral (surface exact error, stop).","auth_complexity":45.0,"rate_limit_clarity":10.0,"tls_enforcement":70.0,"auth_strength":40.0,"scope_granularity":20.0,"dependency_hygiene":20.0,"secret_handling":30.0,"security_notes":"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.","uptime_documented":0.0,"version_stability":45.0,"breaking_changes_history":20.0,"error_recovery":30.0,"idempotency_support":"false","idempotency_notes":"Idempotency is not explicitly addressed; claim transactions may be non-idempotent depending on contract state.","pagination_style":"none","retry_guidance_documented":true,"known_agent_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."]}}