New: 98,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Agent skill

Sponge Wallet

by LeoYeAI in LeoYeAI/openclaw-master-skills

Manage crypto wallets, transfers, swaps, and balances via the Sponge Wallet API.

MITAuto-check passed

Install Sponge Wallet

skills CLI
$ npx skills add LeoYeAI/openclaw-master-skills --skill sponge-wallet -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install LeoYeAI/openclaw-master-skills sponge-wallet --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/LeoYeAI/openclaw-master-skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/wallet-skills .claude/skills/sponge-wallet && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
sponge-wallet
GitHub stars
2.2k
Token cost
~4.3k tokens
SKILL.md length
1,104 words
Files
2
Skills in repo
1,235
Repo updated
First seen
Licence
MIT

At a glance

Manage crypto wallets, transfers, swaps, and balances via the Sponge Wallet API.

  • Works in 5 steps: Agent Registration (AI agents only) → Human Login (existing accounts only) → Register (agents only) → …
  • SKILL.md covers Why the steps matter (short…, Standard credential storage…, Base URL & Auth and CRITICAL: AI Agents Must Use…, plus 3 more sections
  • Calls curl and jq; reaches api.wallet.paysponge.com and wallet.paysponge.com; needs SPONGE_API_KEY

What it does

Sponge Wallet is an agent skill from LeoYeAI/openclaw-master-skills. Manage crypto wallets, transfers, swaps, and balances via the Sponge Wallet API.

Its SKILL.md is about 4.3k tokens, which your agent loads only when the skill is triggered. The skill folder holds 1 other file (for example `_meta.json`).

The repository describes itself as: 🧠 Curated collection of 1209+ best OpenClaw skills — weekly updated by MyClaw.ai. The licence is MIT.

Example prompts

  • “/sponge-wallet”

Requirements

  • A credential in SPONGE_API_KEY

Workflow steps

5 steps, taken from the step headings in SKILL.md.

  1. Agent Registration (AI agents only)
  2. Human Login (existing accounts only)
  3. Register (agents only)
  4. Check balance
  5. Transfer USDC on Base

What it can do on your machine

Read from SKILL.md and the folder at commit e5199b5. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Shell commands in SKILL.md call:

    • curl
    • jq

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    Hosts in commands or code, which the agent is likely to contact:

    • api.wallet.paysponge.com
    • wallet.paysponge.com
    • amazon.com
    • api.paysponge.com

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names these keys or tokens, usually read from environment variables:

    • SPONGE_API_KEY

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Sponge Wallet loads about 4.3k tokens when it runs. Until then it costs about 24 tokens; SKILL.md has 1,104 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~24
When it runs · the whole SKILL.md, loaded when a task matches
~4.3k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from LeoYeAI/openclaw-master-skills at commit e5199b5, republished under its MIT licence (© LeoYeAI). 1,104 words, ~4,347 tokens.

Download SKILL.mdSave it as .claude/skills/sponge-wallet/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.
name
sponge-wallet
description
Manage crypto wallets, transfers, swaps, and balances via the Sponge Wallet API.
version
1.0.0
homepage
https://wallet.paysponge.com
user-invocable
true
SPONGE WALLET API QUICK REFERENCE v1.0.0
Base:   https://api.wallet.paysponge.com
Auth:   Authorization: Bearer <SPONGE_API_KEY>
Docs:   This file is canonical (skills guide + params)

Key endpoints:
  POST /api/agents/register              -> register (no auth)
  POST /api/oauth/device/authorization   -> device login start (humans)
  POST /api/oauth/device/token           -> device token poll (agents + humans)
  GET  /api/balances                     -> get balances (includes Polymarket USDC.e)
  POST /api/transfers/evm                -> EVM transfer (ETH/USDC)
  POST /api/transfers/solana             -> Solana transfer (SOL/USDC)
  POST /api/transactions/swap            -> Solana swap
  POST /api/transactions/base-swap       -> Base swap (0x)
  POST /api/transactions/bridge          -> Bridge (deBridge)
  GET  /api/solana/tokens                -> list SPL tokens
  GET  /api/solana/tokens/search         -> search Jupiter token list
  GET  /api/transactions/status/:txHash  -> transaction status
  GET  /api/transactions/history         -> transaction history
  POST /api/funding-requests             -> request funding from owner
  POST /api/wallets/withdraw-to-main     -> withdraw to owner
  POST /api/x402/fetch                   -> x402 fetch (auto-pay 402s)
  GET  /api/x402/discover                -> discover x402 services (Bazaar)
  POST /api/polymarket                   -> Polymarket prediction market trading
  POST /api/checkout                      -> Amazon checkout (initiate purchase)
  GET  /api/checkout/:sessionId           -> checkout status
  DELETE /api/checkout/:sessionId         -> cancel checkout
  GET  /api/checkout/history              -> checkout history
  POST /api/checkout/amazon-search        -> search Amazon products

Rules: use register (agents), never login | store key in ~/.spongewallet/credentials.json | requests are JSON
Errors: HTTP status + JSON error message

Sponge Wallet API - Agent Skills Guide

This skill is doc-only. There is no local CLI. Agents must call the Sponge Wallet REST API directly.

Why the steps matter (short rationale)

  • Register vs login: agents create a new managed wallet tied to a human owner. That owner must explicitly claim the agent. Login is only for humans who already have an account.
  • Claim URL: ensures the human owner explicitly links the agent to their account and controls allowlists/funding.
  • Credential persistence: the apiKey is returned once (immediately for agent-first mode, or after device approval for standard mode). If you lose it, you must re-register or re-authenticate.

Standard credential storage (required)

Store the API key in one canonical location:

  • ~/.spongewallet/credentials.json

Recommended file contents:

json
{
  "apiKey": "sponge_live_...",
  "claimCode": "ABCD-1234",
  "claimUrl": "https://wallet.paysponge.com/device?code=ABCD-1234"
}

Optional environment export (runtime convenience):

bash
export SPONGE_API_KEY="$(jq -r .apiKey ~/.spongewallet/credentials.json)"

Base URL & Auth

  • Base URL: https://api.wallet.paysponge.com
  • Auth header: Authorization: Bearer <SPONGE_API_KEY>
  • Content-Type: application/json

Quick env setup:

bash
export SPONGE_API_URL="https://api.wallet.paysponge.com"
export SPONGE_API_KEY="$(jq -r .apiKey ~/.spongewallet/credentials.json)"

CRITICAL: AI Agents Must Use register, NOT login

1) Agent Registration (AI agents only)

There are two modes:

  • Standard device flow (default): human must approve before the API key is returned.
  • Agent-first (agentFirst: true): agent receives the API key immediately, and the human can claim later.

Step 1 — Start registration (agent-first recommended)

bash
curl -sS -X POST "$SPONGE_API_URL/api/agents/register" \
  -H "Content-Type: application/json" \
  -d '{
    "name":"YourAgentName",
    "agentFirst": true,
    "testnet": true
  }'

Response includes:

  • verificationUriComplete (claim URL for the human owner)
  • claimCode, deviceCode, expiresIn, interval, claimText
  • apiKey (returned immediately in agent-first mode)

Store apiKey, claimCode, and verificationUriComplete (as claimUrl) in ~/.spongewallet/credentials.json so a human can claim later if context resets.

Step 2 — Send the claim URL to the human owner They log in, optionally post the tweet text, and approve the agent.

Claim link format:

  • verificationUriComplete (example path: /device?code=ABCD-1234)
  • The base URL is the frontend (prod or local), so just pass the full verificationUriComplete to the human.

Step 3 — Poll for completion (standard device flow only)

bash
curl -sS -X POST "$SPONGE_API_URL/api/oauth/device/token" \
  -H "Content-Type: application/json" \
  -d '{
    "grantType":"urn:ietf:params:oauth:grant-type:device_code",
    "deviceCode":"<deviceCode>",
    "clientId":"spongewallet-skill"
  }'

On success, the response includes apiKey. Save it to ~/.spongewallet/credentials.json and use it as SPONGE_API_KEY.

Note: In agent-first mode, you already have the apiKey from Step 1. The device token will remain pending until the human claims.

2) Human Login (existing accounts only)

Phase 1 — Request device code

bash
curl -sS -X POST "$SPONGE_API_URL/api/oauth/device/authorization" \
  -H "Content-Type: application/json" \
  -d '{
    "clientId":"spongewallet-skill",
    "scope":"wallet:read wallet:write transaction:sign transaction:write"
  }'

Phase 2 — Poll for token (same endpoint as agents)

bash
curl -sS -X POST "$SPONGE_API_URL/api/oauth/device/token" \
  -H "Content-Type: application/json" \
  -d '{
    "grantType":"urn:ietf:params:oauth:grant-type:device_code",
    "deviceCode":"<deviceCode>",
    "clientId":"spongewallet-skill"
  }'

Tool Call Pattern

All tool calls are plain REST requests with JSON payloads.

Common headers

bash
-H "Authorization: Bearer $SPONGE_API_KEY" \
-H "Content-Type: application/json" \
-H "Accept: application/json"

Agent ID note: agentId is optional for API key auth. It is only required when using a user session (e.g., Privy-based auth) or when explicitly operating on a different agent.

Tool -> Endpoint Map
ToolMethodPathParams/Body
get_balanceGET/api/balancesQuery: chain, allowedChains, onlyUsdc
get_solana_tokensGET/api/solana/tokensQuery: chain
search_solana_tokensGET/api/solana/tokens/searchQuery: query, limit
evm_transferPOST/api/transfers/evmBody: chain, to, amount, currency
solana_transferPOST/api/transfers/solanaBody: chain, to, amount, currency
solana_swapPOST/api/transactions/swapBody: chain, inputToken, outputToken, amount, slippageBps
base_swapPOST/api/transactions/base-swapBody: chain, inputToken, outputToken, amount, slippageBps
bridgePOST/api/transactions/bridgeBody: sourceChain, destinationChain, token, amount, destinationToken, recipientAddress
get_transaction_statusGET/api/transactions/status/{txHash}Query: chain
get_transaction_historyGET/api/transactions/historyQuery: limit, chain
request_fundingPOST/api/funding-requestsBody: amount, reason, chain, currency
withdraw_to_main_walletPOST/api/wallets/withdraw-to-mainBody: chain, amount, currency
x402_fetchPOST/api/x402/fetchBody: url, method, headers, body, preferred_chain
discover_x402_servicesGET/api/x402/discoverQuery: type, limit, offset, include_catalog
polymarketPOST/api/polymarketBody: action, + action-specific params (see below)
amazon_checkoutPOST/api/checkoutBody: checkoutUrl, amazonAccountId, shippingAddress, dryRun, clearCart
get_checkout_statusGET/api/checkout/{sessionId}Query: agentId (optional)
get_checkout_historyGET/api/checkout/historyQuery: agentId, limit, offset
amazon_searchPOST/api/checkout/amazon-searchBody: query, maxResults, region

Note: request bodies use camelCase (e.g., inputToken, slippageBps).

Polymarket Actions

The polymarket endpoint is a unified tool. Pass action plus action-specific parameters:

ActionDescriptionRequired ParamsOptional Params
statusCheck Polymarket account status and USDC.e balance——
marketsSearch prediction markets—query, limit
positionsView current market positions——
ordersView open and recent orders——
orderPlace a buy/sell orderoutcome, side, size, pricemarket_slug or token_id, order_type
cancelCancel an open orderorder_id—
set_allowancesReset token approvals——
withdrawWithdraw USDC.e from Safe to any addressto_address, amount—

Order params:

  • market_slug: Market URL slug (e.g., "will-bitcoin-hit-100k") — use this OR token_id
  • token_id: Polymarket condition token ID — use this OR market_slug
  • outcome: "yes" or "no"
  • side: "buy" or "sell"
  • size: Number of shares (e.g., 10)
  • price: Probability price 0.0–1.0 (e.g., 0.65 = 65 cents per share)
  • order_type: "GTC" (default), "GTD", "FOK", "FAK"

Scopes: Trade actions (order, cancel, set_allowances, withdraw) require polymarket:trade scope. Read actions (status, markets, positions, orders) require polymarket:read.

Auto-provisioning: The Polymarket Safe wallet is created automatically on first use. No manual setup needed.

Show full SKILL.md (395 more words)Show less
Amazon Checkout

Purchase products from Amazon using a configured Amazon account.

Prerequisites:

  • An Amazon account must be configured via the dashboard or /api/agents/:id/amazon-accounts endpoints
  • A shipping address must be set (inline or via /api/agents/:id/shipping-addresses)

Async workflow:

  1. Initiate checkout with POST /api/checkout — returns a sessionId
  2. Wait ~60 seconds for the initial checkout process
  3. Poll GET /api/checkout/:sessionId every 10 seconds until status is completed or failed

Status progression: pending → in_progress → completed | failed | cancelled

Key options:

  • dryRun: true — stops before placing the order (useful for testing or previewing total cost)
  • clearCart: true — clears the Amazon cart before adding the product (default behavior)

Scopes: Checkout actions require amazon_checkout scope on the API key.

Quick Start

1) Register (agents only)
bash
curl -sS -X POST "$SPONGE_API_URL/api/agents/register" \
  -H "Content-Type: application/json" \
  -d '{
    "name":"YourAgentName",
    "agentFirst": true,
    "testnet": true
  }'

Share the claim URL with your human, then store the apiKey immediately (agent-first). For standard device flow, poll for the token after approval.

2) Check balance
bash
curl -sS "$SPONGE_API_URL/api/balances?chain=base" \
  -H "Authorization: Bearer $SPONGE_API_KEY" \
  -H "Accept: application/json"
3) Transfer USDC on Base
bash
curl -sS -X POST "$SPONGE_API_URL/api/transfers/evm" \
  -H "Authorization: Bearer $SPONGE_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "chain":"base",
    "to":"0x...",
    "amount":"10",
    "currency":"USDC"
  }'

Examples

Swap tokens on Solana
bash
curl -sS -X POST "$SPONGE_API_URL/api/transactions/swap" \
  -H "Authorization: Bearer $SPONGE_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "chain":"solana",
    "inputToken":"SOL",
    "outputToken":"BONK",
    "amount":"0.5",
    "slippageBps":100
  }'
Swap tokens on Base
bash
curl -sS -X POST "$SPONGE_API_URL/api/transactions/base-swap" \
  -H "Authorization: Bearer $SPONGE_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "chain":"base",
    "inputToken":"ETH",
    "outputToken":"USDC",
    "amount":"0.1",
    "slippageBps":50
  }'
Bridge tokens cross-chain
bash
curl -sS -X POST "$SPONGE_API_URL/api/transactions/bridge" \
  -H "Authorization: Bearer $SPONGE_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "sourceChain":"solana",
    "destinationChain":"base",
    "token":"SOL",
    "amount":"0.1",
    "destinationToken":"ETH"
  }'
Check transaction status
bash
curl -sS "$SPONGE_API_URL/api/transactions/status/0xabc123...?chain=base" \
  -H "Authorization: Bearer $SPONGE_API_KEY" \
  -H "Accept: application/json"
Polymarket — Check status
bash
curl -sS -X POST "$SPONGE_API_URL/api/polymarket" \
  -H "Authorization: Bearer $SPONGE_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"action":"status"}'
Polymarket — Search markets
bash
curl -sS -X POST "$SPONGE_API_URL/api/polymarket" \
  -H "Authorization: Bearer $SPONGE_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"action":"markets","query":"bitcoin","limit":5}'
Polymarket — Place an order
bash
curl -sS -X POST "$SPONGE_API_URL/api/polymarket" \
  -H "Authorization: Bearer $SPONGE_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "action":"order",
    "market_slug":"will-bitcoin-hit-100k",
    "outcome":"yes",
    "side":"buy",
    "size":10,
    "price":0.65
  }'
Polymarket — View positions
bash
curl -sS -X POST "$SPONGE_API_URL/api/polymarket" \
  -H "Authorization: Bearer $SPONGE_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"action":"positions"}'
Polymarket — Withdraw USDC.e
bash
curl -sS -X POST "$SPONGE_API_URL/api/polymarket" \
  -H "Authorization: Bearer $SPONGE_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "action":"withdraw",
    "to_address":"0x...",
    "amount":"10.00"
  }'
Amazon Checkout — Initiate purchase
bash
curl -sS -X POST "$SPONGE_API_URL/api/checkout" \
  -H "Authorization: Bearer $SPONGE_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "checkoutUrl":"https://www.amazon.com/dp/B0EXAMPLE",
    "dryRun":true,
    "clearCart":true
  }'
Amazon Checkout — Poll status
bash
curl -sS "$SPONGE_API_URL/api/checkout/<sessionId>" \
  -H "Authorization: Bearer $SPONGE_API_KEY" \
  -H "Accept: application/json"
Amazon Checkout — Get history
bash
curl -sS "$SPONGE_API_URL/api/checkout/history?limit=10" \
  -H "Authorization: Bearer $SPONGE_API_KEY" \
  -H "Accept: application/json"
Amazon — Search products
bash
curl -sS -X POST "$SPONGE_API_URL/api/checkout/amazon-search" \
  -H "Authorization: Bearer $SPONGE_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"query":"wireless mouse","maxResults":5}'
x402 Fetch (auto-pay for paid APIs)
bash
curl -sS -X POST "$SPONGE_API_URL/api/x402/fetch" \
  -H "Authorization: Bearer $SPONGE_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "url":"https://api.paysponge.com/api/services/purchase/svc_abc123/polymarket/markets?search=bitcoin&limit=5",
    "method":"GET",
    "preferred_chain":"base"
  }'

The x402_fetch tool handles the entire payment flow automatically:

  1. Makes the HTTP request to the specified URL
  2. If the service returns 402 Payment Required, extracts payment requirements
  3. Creates and signs a USDC payment using the agent's wallet (Base or Solana)
  4. Retries the request with the Payment-Signature header
  5. Returns the final API response with payment_made and payment_details
Discover x402 services (Bazaar)
bash
curl -sS "$SPONGE_API_URL/api/x402/discover?limit=10" \
  -H "Authorization: Bearer $SPONGE_API_KEY" \
  -H "Accept: application/json"

Returns available x402-enabled services from the Bazaar and Sponge's curated catalog. Use this to find paid APIs before calling x402_fetch.

Chain Reference

Test keys (sponge_test_*): sepolia, base-sepolia, solana-devnet, tempo Live keys (sponge_live_*): ethereum, base, solana

Error Responses

Errors return JSON with an error message and HTTP status:

json
{"error":"message"}
StatusMeaningCommon Cause
400Bad RequestMissing/invalid fields
401UnauthorizedMissing or invalid API key
403ForbiddenAddress not in allowlist or permission denied
404Not FoundResource does not exist
409ConflictDuplicate action
429Rate LimitedToo many requests (back off + retry)
500Server ErrorTransient; retry later

Security

  • Never share your API key in logs, posts, or screenshots.
  • Store your API key in ~/.spongewallet/credentials.json and restrict file permissions.
  • Rotate the key if exposure is suspected.

Built for agents.

© LeoYeAI, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 1 other file in skills/wallet-skills of LeoYeAI/openclaw-master-skills.

  • SKILL.md
  • _meta.json

Open the folder on GitHubat commit e5199b5

Compare with similar skills

Sponge Wallet next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Sponge Wallet compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Sponge Wallet this skillLeoYeAI/openclaw-master-skills2.2k—~4.3kAutomated safety check: PassMIT
Emblemai Crypto Walletsickn33/agentic-awesome-skills47k2 repos~669Automated safety check: PassMIT
Crypto Derivatives StrategiesHKUDS/Vibe-Trading35k—~2.4kAutomated safety check: PassMIT
Agent Load Balancerruvnet/ruflo74k2 repos~3.1kAutomated safety check: PassMIT
Intelligence Transferruvnet/ruflo74k—~877Automated safety check: NotesMIT
Analyzing Ransomware Payment Walletsmukul975/Anthropic-Cybersecurity-Skills34k—~1.9kAutomated safety check: PassApache-2.0

Similar skills

  • Emblemai Crypto Wallet

    sickn33/agentic-awesome-skills

    Crypto wallet management across 7 blockchains via EmblemAI Agent Hustle API.

    47k GitHub starsUsed in 2 repos~669 tokens
    Business, Finance & HRAuto-check passed

  • Crypto Derivatives Strategies

    HKUDS/Vibe-Trading

    Covers three crypto-derivatives approaches: perpetual funding-rate arbitrage, futures term-structure trading in contango and backwardation, and options volatility and Greeks analysis.

    35k GitHub stars~2.4k tokensUpdated yesterday
    Business, Finance & HRAuto-check passed

  • Agent Load Balancer

    ruvnet/ruflo

    Agent skill for load-balancer - invoke with $agent-load-balancer

    74k GitHub starsUsed in 2 repos~3.1k tokens
    DevOps & CloudAuto-check passed

  • Intelligence Transfer

    ruvnet/ruflo

    Publish or fetch learned patterns across projects via IPFS (Pinata) -- the cross-project pattern transfer that hookstransfer enables

    74k GitHub stars~877 tokensUpdated today
    Auto-check: notes

  • Analyzing Ransomware Payment Wallets

    mukul975/Anthropic-Cybersecurity-Skills

    Traces ransomware cryptocurrency payment flows using blockchain analysis tools such as Chainalysis Reactor, WalletExplorer, and blockchain.com APIs, identifying wallet clusters and tracking fund…

    34k GitHub stars~1.9k tokensUpdated 1 mo ago
    SecurityAuto-check passed

  • Load Balancing

    sickn33/agentic-awesome-skills

    Configure load balancers and traffic distribution. An agent skill from sickn33/agentic-awesome-skills.

    47k GitHub starsUsed in 2 repos~2.9k tokens
    DevOps & CloudAuto-check: notes

More from LeoYeAI/openclaw-master-skills

All 1,235 skills in this repo

  • DevOps Pipeline Management

    LeoYeAI/openclaw-master-skills

    Manages pipelines on a DevOps quality and efficiency platform through its OpenAPI: list workspaces and templates, create, update, run and cancel pipelines, and read run records.

    2.2k GitHub stars~4.2k tokensUpdated 2 mo ago
    Auto-check: notes

  • Feishu Document Collaboration

    LeoYeAI/openclaw-master-skills

    Patches OpenClaw's Feishu extension so an edited document triggers an isolated agent session that reads the doc and replies inline, turning it into a live chat space.

    2.2k GitHub stars~2k tokensUpdated 2 mo ago
    Auto-check passed

  • Files Memory System

    LeoYeAI/openclaw-master-skills

    Multi-context memory management system for OpenClaw agents with group-isolated storage, global shared memory, workspace organization, and group-specific skills isolation.

    2.2k GitHub stars~3.8k tokensUpdated 2 mo ago
    Auto-check passed

  • GEO-Claw AI Visibility Agent

    LeoYeAI/openclaw-master-skills

    Runs a brand's AI-search visibility work end to end: diagnosing how AI platforms represent it, repositioning it, producing AI-optimized content and monitoring ongoing mentions.

    2.2k GitHub stars~4.7k tokensUpdated 2 mo ago
    Auto-check passed

  • Google Workspace CLI

    LeoYeAI/openclaw-master-skills

    Installs and authenticates the gws CLI, then automates Gmail, Drive, Sheets, Calendar, Docs, Chat and Tasks with ready-made recipes, persona bundles and security audits.

    2.2k GitHub stars~2.6k tokensUpdated 2 mo ago
    Auto-check: notes

  • HealthFit Health Advisors

    LeoYeAI/openclaw-master-skills

    Runs four advisor roles, a fitness coach, nutritionist, data analyst and TCM practitioner, to build a health profile and track workouts, diet and wellness over time.

    2.2k GitHub stars~4.4k tokensUpdated 2 mo ago
    Auto-check passed

Questions about Sponge Wallet

What does Sponge Wallet do?

Manage crypto wallets, transfers, swaps, and balances via the Sponge Wallet API. Sponge Wallet is an agent skill from LeoYeAI/openclaw-master-skills. Manage crypto wallets, transfers, swaps, and balances via the Sponge Wallet API.

How do I install Sponge Wallet in Claude Code?

Run `npx skills add LeoYeAI/openclaw-master-skills --skill sponge-wallet -a claude-code`. Or copy the skill folder (skills/wallet-skills in LeoYeAI/openclaw-master-skills) into .claude/skills/sponge-wallet in your project. Claude Code loads it when a task matches its description.

How do I install Sponge Wallet in Codex?

Run `npx skills add LeoYeAI/openclaw-master-skills --skill sponge-wallet -a codex`. Or copy the skill folder (skills/wallet-skills in LeoYeAI/openclaw-master-skills) into .agents/skills/sponge-wallet in your project. Codex loads it when a task matches its description.

Can I use Sponge Wallet in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add LeoYeAI/openclaw-master-skills --skill sponge-wallet -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/sponge-wallet, .gemini/skills/sponge-wallet, .github/skills/sponge-wallet and .opencode/skills/sponge-wallet in your project.

What does Sponge Wallet need to run?

Going by SKILL.md and its folder, Sponge Wallet needs the command-line tools its instructions call (curl and jq) and credentials named SPONGE_API_KEY. Our summary lists: A credential in SPONGE_API_KEY.

Does Sponge Wallet access the network?

SKILL.md names 4 domains. In commands or code: api.wallet.paysponge.com, wallet.paysponge.com, amazon.com and api.paysponge.com; the agent is likely to contact these when it follows the instructions. This is read from the text; nothing was executed.

Is Sponge Wallet safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Sponge Wallet use?

Sponge Wallet is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Sponge Wallet use?

About 4.3k tokens (SKILL.md is roughly 17k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Sponge Wallet?

Skills that share tags, products or a category with Sponge Wallet: Emblemai Crypto Wallet (sickn33/agentic-awesome-skills, 47k stars), Crypto Derivatives Strategies (HKUDS/Vibe-Trading, 35k stars), Agent Load Balancer (ruvnet/ruflo, 74k stars) and Intelligence Transfer (ruvnet/ruflo, 74k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Sponge Wallet?

LeoYeAI (a GitHub user) maintains it in LeoYeAI/openclaw-master-skills, which has 2,160 GitHub stars. The repository holds 1,235 skills in this directory. The repository was last updated on July 20, 2026.

Source: LeoYeAI/openclaw-master-skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.