AI-bounty-skill MCP — Cas d'usage, Installer & Démo en direct

Pourquoi l'utiliser

Fonctionnalités clés

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

Démo en direct

Aperçu en pratique

ai-bounty-skill.replay ▶ prêt

0/0

Installer

Choisissez votre client

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

Ouvrez Claude Desktop → Settings → Developer → Edit Config. Redémarrez après avoir enregistré.

~/.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 utilise le même schéma mcpServers que Claude Desktop. La config projet l'emporte sur la globale.

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

Cliquez sur l'icône MCP Servers dans la barre latérale Cline, puis "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
    }
  }
}

Même format que Claude Desktop. Redémarrez Windsurf pour appliquer.

~/.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 utilise un tableau d'objets serveur plutôt qu'une 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"
        ]
      }
    }
  }
}

Ajoutez dans context_servers. Zed recharge à chaud à la sauvegarde.

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

Une seule ligne. Vérifiez avec claude mcp list. Supprimez avec claude mcp remove.

Cas d'usage

Usages concrets : 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

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

Prérequis

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

Déroulement

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.✓ Copié

→ 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.✓ Copié

→ Payload ready, you broadcast, claim lands

Résultat : Bounty claimed with a transaction hash you control, no custodial middleman.

Pièges

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

Quand l'utiliser : Your aelf identity is a Portkey CA, not a raw EOA.

Prérequis

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

Déroulement

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.✓ Copié

→ 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.✓ Copié

→ Portkey prompts, you approve, tx confirmed

Résultat : Bounty lands in your Portkey-managed CA address.

Pièges

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

Combinaisons

Associez-le à d'autres MCPs pour un effet 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.✓ Copié

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.✓ Copié

Outils

Ce que ce MCP expose

Outil	Entrées	Quand appeler	Coût
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

Coût et limites

Coût d'exécution

Quota d'API: None — skill is prompts only
Tokens par appel: <2k
Monétaire: Free skill. You pay aelf tDVV gas on broadcast.
Astuce: Batch any other pending actions into the same session to amortize context setup.

Sécurité

Permissions, secrets, portée

Stockage des identifiants : No credentials inside the skill. Private keys stay in your local aelf tool or Portkey.

Sortie de données : None by the skill itself. Broadcasting hits aelf tDVV RPC.

Ne jamais accorder : 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.

Dépannage

Erreurs courantes et correctifs

Claim() reverts with 'not eligible'

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

Vérifier : 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.

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

Alternatives

AI-bounty-skill vs autres

Alternative	Quand l'utiliser	Compromis
Direct aelf CLI	You're comfortable hand-writing the contract call	No guidance, but no skill dependency either

Plus

Ressources

📖 Lire le README officiel sur GitHub

🐙 Voir les issues ouvertes

🔍 Parcourir les 400+ serveurs MCP et Skills