AI-bounty-skill MCP — Casos de uso, Instalar & Demo ao vivo

Por que usar

Principais recursos

Step-by-step flow for both EOA and Portkey CA claim paths
Defers all signing to Portkey — no private key or seed phrase handling
Explicit warning against using exchange/custodial addresses
Works on aelf tDVV sidechain only

Demo ao vivo

Como fica na prática

ai-bounty-skill.replay ▶ pronto

0/0

Instalar

Escolha seu cliente

~/Library/Application Support/Claude/claude_desktop_config.json · Windows: %APPDATA%\Claude\claude_desktop_config.json

{
  "mcpServers": {
    "ai-bounty-skill": {
      "command": "git",
      "args": [
        "clone",
        "https://github.com/aelf-hzz780/AI-bounty-skill",
        "~/.claude/skills/AI-bounty-skill"
      ],
      "_inferred": true
    }
  }
}

Abra Claude Desktop → Settings → Developer → Edit Config. Reinicie após salvar.

~/.cursor/mcp.json · .cursor/mcp.json

{
  "mcpServers": {
    "ai-bounty-skill": {
      "command": "git",
      "args": [
        "clone",
        "https://github.com/aelf-hzz780/AI-bounty-skill",
        "~/.claude/skills/AI-bounty-skill"
      ],
      "_inferred": true
    }
  }
}

Cursor usa o mesmo esquema mcpServers que o Claude Desktop. Config de projeto vence a global.

VS Code → Cline → MCP Servers → Edit

{
  "mcpServers": {
    "ai-bounty-skill": {
      "command": "git",
      "args": [
        "clone",
        "https://github.com/aelf-hzz780/AI-bounty-skill",
        "~/.claude/skills/AI-bounty-skill"
      ],
      "_inferred": true
    }
  }
}

Clique no ícone MCP Servers na barra lateral do Cline, depois "Edit Configuration".

~/.codeium/windsurf/mcp_config.json

{
  "mcpServers": {
    "ai-bounty-skill": {
      "command": "git",
      "args": [
        "clone",
        "https://github.com/aelf-hzz780/AI-bounty-skill",
        "~/.claude/skills/AI-bounty-skill"
      ],
      "_inferred": true
    }
  }
}

Mesmo formato do Claude Desktop. Reinicie o Windsurf para aplicar.

~/.continue/config.json

{
  "mcpServers": [
    {
      "name": "ai-bounty-skill",
      "command": "git",
      "args": [
        "clone",
        "https://github.com/aelf-hzz780/AI-bounty-skill",
        "~/.claude/skills/AI-bounty-skill"
      ]
    }
  ]
}

O Continue usa um array de objetos de servidor em vez de um map.

~/.config/zed/settings.json

{
  "context_servers": {
    "ai-bounty-skill": {
      "command": {
        "path": "git",
        "args": [
          "clone",
          "https://github.com/aelf-hzz780/AI-bounty-skill",
          "~/.claude/skills/AI-bounty-skill"
        ]
      }
    }
  }
}

Adicione em context_servers. Zed recarrega automaticamente ao salvar.

claude mcp add ai-bounty-skill -- git clone https://github.com/aelf-hzz780/AI-bounty-skill ~/.claude/skills/AI-bounty-skill

Uma linha só. Verifique com claude mcp list. Remova com claude mcp remove.

Casos de uso

Usos do mundo real: AI-bounty-skill

Claim an aelf AI bounty from an EOA wallet

👤 aelf developers holding the bounty in a self-custody EOA ⏱ ~15 min intermediate

Quando usar: You were rewarded in the aelf AI bounty program and want Claude to walk the RewardClaimContract Claim() call instead of hand-rolling it.

Pré-requisitos

aelf EOA wallet with gas on tDVV — Fund your address with ELF on the tDVV sidechain
Skill cloned into ~/.claude/skills/AI-bounty-skill — git clone https://github.com/aelf-hzz780/AI-bounty-skill ~/.claude/skills/AI-bounty-skill

Fluxo

Load your wallet context locally and ask the skill to lay out the call

Use the AI-bounty-skill to prepare a Claim() transaction on RewardClaimContract for my EOA. Show me the args and the signing preview before broadcast.✓ Copiado

→ Claude enumerates contract address, method, and args — pauses for confirmation
Sign and broadcast via your own tool

Looks good — give me the signed tx payload to send via my local aelf CLI.✓ Copiado

→ Payload ready, you broadcast, claim lands

Resultado: Bounty claimed with a transaction hash you control, no custodial middleman.

Armadilhas

Using an exchange deposit address as target — Use a self-custody address — exchanges don't route the reward metadata correctly

Claim the bounty through a Portkey CA (account abstraction) wallet

👤 Users whose bounty is tied to a Portkey-managed social login ⏱ ~15 min intermediate

Quando usar: Your aelf identity is a Portkey CA, not a raw EOA.

Pré-requisitos

Portkey account recovery / login prepared — Use your registered email to recover/login at portkey.finance

Fluxo

Ask Claude to assemble a ClaimByPortkeyToCa() call

Use AI-bounty-skill to prepare ClaimByPortkeyToCa() — my CA hash is <hash>. Show me what will be signed by Portkey.✓ Copiado

→ Claude outputs the exact method and args, and tells you Portkey will prompt for signature
Approve in Portkey

Send it — I'll approve in Portkey.✓ Copiado

→ Portkey prompts, you approve, tx confirmed

Resultado: Bounty lands in your Portkey-managed CA address.

Armadilhas

Mixing EOA and CA code paths — Pick the one that matches how the bounty was assigned — the skill has separate flows for a reason

Combinações

Combine com outros MCPs para 10× de alavancagem

ai-bounty-skill + aelf-skill

Use aelf-skills to bootstrap your dev environment and verify wallet, then AI-bounty-skill to claim

Run aelf-skills health to confirm my wallet and node are working, then use AI-bounty-skill to prepare my bounty claim.✓ Copiado

ai-bounty-skill + filesystem

Read your local wallet config to confirm the correct address before claiming

Read my aelf wallet config at ~/.aelf/keys/, confirm the address, then use AI-bounty-skill to prepare the Claim() call for that address.✓ Copiado

Ferramentas

O que este MCP expõe

Ferramenta	Entradas	Quando chamar	Custo
prepare_eoa_claim	wallet address, bounty id	EOA holder ready to claim	0 — local prompt work
prepare_portkey_claim	CA hash, bounty id	Portkey CA holder ready to claim	0

Custo e limites

O que custa rodar

Cota de API: None — skill is prompts only
Tokens por chamada: <2k
Monetário: Free skill. You pay aelf tDVV gas on broadcast.
Dica: Batch any other pending actions into the same session to amortize context setup.

Segurança

Permissões, segredos, alcance

Armazenamento de credenciais: No credentials inside the skill. Private keys stay in your local aelf tool or Portkey.

Saída de dados: None by the skill itself. Broadcasting hits aelf tDVV RPC.

Nunca conceda: Paste your seed phrase into the chat — the skill never asks for it

Crypto domain — verify the contract address in the skill matches the official aelf bounty contract before signing anything.
Do not use an exchange deposit address as the claim target.
This skill is community-authored with modest stars; read SKILL.md end-to-end before use.

Solução de problemas

Erros comuns e correções

Claim() reverts with 'not eligible'

Confirm the bounty is assigned to the exact address you're calling from, on tDVV (not mainchain).

Verificar: Check RewardClaimContract view methods for your address

Portkey prompt never appears

Make sure you're logged into Portkey in the same browser session as the tool that relays the tx.

Transaction fails with insufficient gas

Fund your tDVV address with ELF tokens for gas. Use the aelf faucet for testnet or transfer from mainchain via cross-chain bridge.

Verificar: Check balance via aelf CLI: aelf-command call -a <address> AElf.ContractNames.Token GetBalance

Alternativas

AI-bounty-skill vs. outros

Alternativa	Quando usar	Troca
Direct aelf CLI	You're comfortable hand-writing the contract call	No guidance, but no skill dependency either

Mais

Recursos

📖 Leia o README oficial no GitHub

🐙 Ver issues abertas

🔍 Ver todos os 400+ servidores MCP e Skills