AI-bounty-skill MCP — Сценарии использования, Установка & Живое демо

Зачем использовать

Ключевые функции

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

Живое демо

Как выглядит на практике

ai-bounty-skill.replay ▶ готово

0/0

Установка

Выберите клиент

~/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
    }
  }
}

Откройте Claude Desktop → Settings → Developer → Edit Config. Перезапустите после сохранения.

~/.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 использует ту же схему mcpServers, что и Claude Desktop. Конфиг проекта приоритетнее глобального.

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
    }
  }
}

Щёлкните значок MCP Servers на боковой панели Cline, затем "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
    }
  }
}

Тот же формат, что и Claude Desktop. Перезапустите Windsurf для применения.

~/.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"
      ]
    }
  ]
}

Continue использует массив объектов серверов, а не 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"
        ]
      }
    }
  }
}

Добавьте в context_servers. Zed перезагружается автоматически.

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

Однострочная команда. Проверить: claude mcp list. Удалить: claude mcp remove.

Сценарии использования

Реальные сценарии: 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

Когда использовать: You were rewarded in the aelf AI bounty program and want Claude to walk the RewardClaimContract Claim() call instead of hand-rolling it.

Предварительные требования

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

Поток

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.✓ Скопировано

→ 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.✓ Скопировано

→ Payload ready, you broadcast, claim lands

Итог: Bounty claimed with a transaction hash you control, no custodial middleman.

Подводные камни

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

Когда использовать: Your aelf identity is a Portkey CA, not a raw EOA.

Предварительные требования

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

Поток

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.✓ Скопировано

→ 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.✓ Скопировано

→ Portkey prompts, you approve, tx confirmed

Итог: Bounty lands in your Portkey-managed CA address.

Подводные камни

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

Комбинации

Сочетайте с другими MCP — эффект x10

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.✓ Скопировано

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.✓ Скопировано

Инструменты

Что предоставляет этот MCP

Инструмент	Входные данные	Когда вызывать	Стоимость
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

Стоимость и лимиты

Во что обходится

Квота API: None — skill is prompts only
Токенов на вызов: <2k
Деньги: Free skill. You pay aelf tDVV gas on broadcast.
Совет: Batch any other pending actions into the same session to amortize context setup.

Безопасность

Права, секреты, радиус поражения

Хранение учётных данных: No credentials inside the skill. Private keys stay in your local aelf tool or Portkey.

Исходящий трафик: None by the skill itself. Broadcasting hits aelf tDVV RPC.

Никогда не давайте: 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.

Устранение неполадок

Частые ошибки и исправления

Claim() reverts with 'not eligible'

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

Проверить: 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.

Проверить: Check balance via aelf CLI: aelf-command call -a <address> AElf.ContractNames.Token GetBalance

Альтернативы

AI-bounty-skill в сравнении

Альтернатива	Когда использовать	Компромисс
Direct aelf CLI	You're comfortable hand-writing the contract call	No guidance, but no skill dependency either

Ещё

Ресурсы

📖 Читать официальный README на GitHub

🐙 Открытые задачи

🔍 Все 400+ MCP-серверов и Skills