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는 Claude Desktop과 동일한 mcpServers 스키마 사용. 프로젝트 설정이 전역보다 우선.

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

Cline 사이드바의 MCP Servers 아이콘 클릭 후 "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는 맵이 아닌 서버 오브젝트 배열 사용.

~/.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와 조합해 10배 효율

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

AI-bounty-skill

왜 쓰나요

핵심 기능

라이브 데모

실제 사용 모습

설치

클라이언트 선택

사용 사례

실전 활용법: AI-bounty-skill

Claim an aelf AI bounty from an EOA wallet

사전 조건

흐름

함정

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

사전 조건

흐름

함정

조합

다른 MCP와 조합해 10배 효율

도구

이 MCP가 노출하는 것

비용 및 제한

운영 비용

보안

권한, 시크릿, 파급범위

문제 해결

자주 발생하는 오류와 해결

대안

AI-bounty-skill 다른 것과 비교

더 보기

리소스