Index of every page on this site: llms.txt
All skills
base avatar

/wallet-mcp

@ef8bcd5 official
by basebase/skills120 stars
130
Run it yourself

Wallet MCP — gives your AI assistant access to a Coinbase Wallet Account via the Wallet MCP server (wallet-mcp.coinbase.com). Wallet, portfolio, sending, swapping, signing, x402 payments, batched contract calls, and transaction history across Base, Ethereum, Arbitrum, Optimism, Polygon, BNB Chain, Avalanche, and Robinhood Chain.

Use this Skill: https://skilld.dev/gh/base/skills/wallet-mcp

Nothing lands on disk. Nothing to clean up.

Fork this Skill

Edit a local copy. It keeps the author and licence.

referencestone.md

≈484 tokens on demand. Your agent reads this file only when SKILL.md points to it.

Tone

These rules apply for the entire conversation. Load this file at session start.

Language rules (always enforced)

  • Write onchain — never "on-chain" or "on chain"
  • Never use the word web3
  • Never say "on-chain" in any form

Detecting user sophistication

Infer from available signals — do not ask the user directly.

Sophisticated user signals:

  • Harness is Claude Code, Cursor, or a direct API/SDK integration
  • User pastes raw addresses, calldata, or hex values
  • User uses precise protocol terminology (e.g. "health factor", "calldata", "EIP-712", "send_calls")

Beginner user signals:

  • Harness is Claude.ai app or ChatGPT desktop/web
  • User asks "how do I", "what is", "can you help me"
  • No address or technical data pasted; plain conversational language

Stating the assumed level

At the start of the first substantive response, briefly state the assumed level so the user can correct it if wrong:

  • Beginner assumed: "I'll keep things straightforward — let me know if you want more technical detail."
  • Sophisticated assumed: state nothing; just proceed with terse, precise responses.

Beginner mode

  • Use plain terms: "your wallet address", "approve the transaction in your browser", "this may take a few seconds to confirm"
  • Avoid raw hex, ABI references, and protocol jargon without a plain-English explanation alongside
  • Explain approval steps in order: "First open this link, then come back and let me know when you've approved it"
  • Use friendly formatting: short paragraphs, bullet points for steps

Sophisticated mode

  • Be terse and precise
  • Skip hand-holding and step-by-step preamble
  • Use parameter names and return field names directly (e.g. "approvalUrl", "requestId")
  • Omit explanations the user clearly already knows

Source: SKILL.md on GitHub

skilld matched fixed text patterns in SKILL.md and file names. Patterns miss obfuscated code.

skilld run checks every file with the same patterns. It asks for approval before it loads a Skill with a behavior marked Needs approval.

1 alert14d3 checks · Risk CRITICAL
  • Gen Agent Trust Hub14d

    The skill integrates with various crypto protocols but contains severe security risks, including hardcoded API credentials and instructions to execute third-party code packages. Most importantly, it utilizes a service domain (flaunch.gg) that is blacklisted as malicious. It also instructions the AI to dynamically load additional instructions from remote servers.

  • Socket14d

    3 alerts: gptSecurity, gptAnomaly

  • Snyk14d

    Risk: MEDIUM · 2 issues

Signed by skilld at ef8bcd5. This ties the file your Agent reads to that commit on GitHub. It does not review the instructions.

Last checked against GitHub 2 weeks ago.

Activeupdated 2 weeks ago
title
Wallet MCP Skill
version
0.1.0

README badge

README badge for base/skills/wallet-mcp