Automation
Skill
/ai-bounty-claim
Claim the AI bounty on tDVV by delegating to the canonical repo SKILL and its branch docs; this public skill is AA/CA only and requires explicit write confirmation.
Install
$ npx -y skills add aelf-hzz780/AI-bounty-skill --skill ai-bounty-claim --agent claude-codeHow it fires
How this skill gets triggered: by you, by Claude, or both.
- Fires itselfAuto-invocation. Claude auto-loads it when your prompt matches the work.Auto-invocation is when the right skill fires by itself at the right moment, driven by a FLOW.md router and a hook, instead of you invoking it by name. It is the difference between a skill being installed and a skill actually getting used.Read the full definition →
- You can call itInvoke it directly when you want it.
- Slash command
/ai-bounty-claim
Context preview
The summary Claude sees to decide when to auto-load this skill.
Claim the AI bounty on tDVV by delegating to the canonical repo SKILL and its branch docs; this public skill is AA/CA only and requires explicit write confirmation.
SKILL.md
ai-bounty-claim.SKILL.mdname: ai-bounty-claim
description: Claim the AI bounty on tDVV by delegating to the canonical repo SKILL and its branch docs; this public skill is AA/CA only and requires explicit write confirmation.
homepage: https://github.com/aelf-hzz780/AI-bounty-skill
metadata: {"openclaw":{"homepage":"https://github.com/aelf-hzz780/AI-bounty-skill"}}AI Bounty Claim
This workspace OpenClaw skill is a thin bootstrap wrapper. The canonical instructions live in `SKILL.md` at the repository root.
Use this skill when
- the user wants to claim the AI bounty on `tDVV`
- the user wants to use `email` to recover/login before an `AA/CA` claim
- the user needs AA/CA onboarding, sync preflight, or AA/CA diagnostics on `tDVV`
Required steps
- Read `SKILL.md` at the repository root first and treat it as the source of truth.
- Choose exactly one branch and then read the matching files in `references/flows/` and `references/examples/`.
- Treat this public bounty skill as `AA/CA only`; accept `CA` as the same route alias.
- Require `@portkey/ca-agent-skills >= 2.3.0` for the AA/CA route because claim now depends on `manager-sync-status` / `portkey_manager_sync_status`.
- Before any AA/CA chain write, resolve local context and `caHash`, run `manager-sync-status`, run `GetHolderInfo(caHash)`, and stop unless both manager sync and holder lookup are ready on `tDVV`.
- If a user asks for the old EOA route, explain that this public skill no longer supports it and redirect them to AA/CA onboarding or diagnostics.
- Never infer a fee problem from `Holder is not found` or `CA holder not found`.
- Never ask the user to paste an exchange or custodial address.
- Before any chain write, show the manager signer, manager sync status, holder lookup status, `caHash`, CA contract raw address, reward contract raw address, method chain, receiver semantics, reward amount, and gas note, then require explicit confirmation.
- If a transaction fails, surface the exact chain error and stop.
Read more
name: ai-bounty-claim
description: Claim the AI bounty on tDVV by delegating to the canonical repo SKILL and its branch docs; this public skill is AA/CA only and requires explicit write confirmation.
homepage: https://github.com/aelf-hzz780/AI-bounty-skill
metadata: {"openclaw":{"homepage":"https://github.com/aelf-hzz780/AI-bounty-skill"}}AI Bounty Claim
This workspace OpenClaw skill is a thin bootstrap wrapper. The canonical instructions live in `SKILL.md` at the repository root.
Use this skill when
- the user wants to claim the AI bounty on `tDVV`
- the user wants to use `email` to recover/login before an `AA/CA` claim
- the user needs AA/CA onboarding, sync preflight, or AA/CA diagnostics on `tDVV`
Required steps
- Read `SKILL.md` at the repository root first and treat it as the source of truth.
- Choose exactly one branch and then read the matching files in `references/flows/` and `references/examples/`.
- Treat this public bounty skill as `AA/CA only`; accept `CA` as the same route alias.
- Require `@portkey/ca-agent-skills >= 2.3.0` for the AA/CA route because claim now depends on `manager-sync-status` / `portkey_manager_sync_status`.
- Before any AA/CA chain write, resolve local context and `caHash`, run `manager-sync-status`, run `GetHolderInfo(caHash)`, and stop unless both manager sync and holder lookup are ready on `tDVV`.
- If a user asks for the old EOA route, explain that this public skill no longer supports it and redirect them to AA/CA onboarding or diagnostics.
- Never infer a fee problem from `Holder is not found` or `CA holder not found`.
- Never ask the user to paste an exchange or custodial address.
- Before any chain write, show the manager signer, manager sync status, holder lookup status, `caHash`, CA contract raw address, reward contract raw address, method chain, receiver semantics, reward amount, and gas note, then require explicit confirmation.
- If a transaction fails, surface the exact chain error and stop.
Ships withai-bounty-skill
Public Codex skill for claiming AI bounty on aelf tDVV via RewardClaimContract, supporting EOA Claim() and Portkey CA ClaimByPortkeyToCa().
Get the whole plugin