wallet

starchild-ai-agent/official-skills · updated Apr 8, 2026

MDX-style export adds YAML metadata + attribution linking explainx.ai and this canonical listing URL.

$npx skills add https://github.com/starchild-ai-agent/official-skills --skill wallet
0 commentsdiscussion
summary

Multi-chain wallet operations for EVM and Solana with balance queries, transfers, signing, and transaction history.

  • Supports 13 tools across EVM (Ethereum, Base, Arbitrum, Optimism, Polygon, Linea) and Solana, including balance checks, fund transfers, message signing, and transaction history
  • Use wallet_get_all_balances() for complete portfolio visibility across all chains with USD values in a single call
  • Transfers are policy-gated by Privy TEE — only whitelisted addresses and amounts
skill.md

Wallet

Interact with this agent's on-chain wallets. Each agent has one wallet per chain (EVM + Solana). Supports balance queries, transfers (policy-gated), message signing, and transaction history.

Authentication is automatic via Fly OIDC token — no API keys or wallet addresses needed. Wallets are bound to this machine at deploy time.

Available Tools (14)

Multi-Chain Tools

Tool Description
wallet_info Get all wallet addresses and chain types
wallet_get_all_balances PRIMARY TOOL - Get complete portfolio across ALL chains (EVM + Solana) with USD values
wallet_get_policy Get current policy status (enabled/disabled) and rules for a chain

EVM Tools

Tool Description
wallet_balance Get ETH/token balances on a specific chain (requires chain parameter)
wallet_transactions Get recent EVM transaction history
wallet_transfer Sign and broadcast a transaction on-chain (policy-gated). Funds leave the wallet.
wallet_sign_transaction Sign a transaction WITHOUT broadcasting (returns RLP-encoded signed tx, nothing sent on-chain)
wallet_sign Sign a message (EIP-191 personal_sign)
wallet_sign_typed_data Sign EIP-712 structured data (permits, orders, etc.)

Solana Tools

Tool Description
wallet_sol_balance Get SOL/SPL token balances with USD values
wallet_sol_transactions Get recent Solana transaction history
wallet_sol_transfer Sign and broadcast a Solana transaction on-chain (policy-gated). Funds leave the wallet.
wallet_sol_sign_transaction Sign a Solana transaction WITHOUT broadcasting (returns base64 signed tx, nothing sent on-chain)
wallet_sol_sign Sign a message with the Solana wallet

Tool Usage Examples

Check Wallet Info (All Chains)

wallet_info()

Returns: list of wallets with wallet_address and chain_type for each active wallet.

Use this first to see all available wallets before any operations.

EVM — Check Balance

IMPORTANT: Always specify the chain parameter! To check all chains at once, use wallet_get_all_balances instead.

wallet_balance(chain="ethereum")  # Get ALL tokens on Ethereum
wallet_balance(chain="base", asset="usdc")  # Check specific asset on Base
wallet_balance(chain="polygon", asset="pol")  # Polygon requires explicit asset

chain parameter is REQUIRED. Valid chains: ethereum, base, arbitrum, optimism, polygon, linea

Asset naming:

  • For Polygon native token, use "pol" NOT "matic"
  • Use lowercase symbolic names like "usdc", "weth", "usdt"
  • DO NOT pass contract addresses (e.g., "0x..."), use symbols only
  • Omit asset parameter to discover ALL tokens on the specified chain

Known Limitation - Polygon: The Polygon chain requires explicit asset parameters. Instead of:

wallet_balance(chain="polygon")  # ❌ May fail with "eth not supported"

Use:

wallet_balance(chain="polygon", asset="pol")  # ✅ Check POL balance
wallet_balance(chain="polygon", asset="usdc")  # ✅ Check USDC balance

For complete Polygon portfolio, use wallet_get_all_balances() which handles this correctly.

For checking balances across ALL chains in one call, use wallet_get_all_balances() instead.

Multi-Chain — Get All Balances

wallet_get_all_balances()

This is the PRIMARY tool for comprehensive balance checks.

Automatically checks ALL supported chains (Ethereum, Base, Arbitrum, Optimism, Polygon, Linea, Solana) and returns complete portfolio with USD values.

Use this instead of calling wallet_balance() multiple times for different chains.

EVM — Query Transaction History

wallet_transactions()
wallet_transactions(chain="ethereum", asset="eth", limit=10)
wallet_transactions(limit=50)

Defaults: chain="ethereum", asset="eth", limit=20 (max 100).

Returns: list of transactions with tx_hash, from, to, amount, status, timestamp.

EVM — Transfer Funds / Contract Calls

wallet_transfer(to="0xRecipientAddress", amount="1000000000000000000")
wallet_transfer(to="0xRecipientAddress", amount="1000000000000000000", chain_id=8453)
wallet_transfer(to="0xContractAddress", amount="0", data="0xa9059cbb000000...", chain_id=8453)
  • to: Target wallet or contract address (0x...)
  • amount: Amount in wei (not ETH). "1000000000000000000" = 1 ETH. Use "0" for contract calls that don't send ETH.
  • chain_id: Chain ID (default: 1 = Ethereum mainnet, 8453 = Base, 10 = Optimism)
  • data: Hex-encoded calldata for contract calls (e.g. ERC-20 transfer, swap). Optional — omit for simple ETH transfers.
  • gas_limit: Gas limit (decimal string). Optional — Privy estimates if omitted.
  • gas_price: Gas price in wei (decimal string, for legacy transactions). Optional.
  • max_fee_per_gas: Max fee per gas in wei (decimal string, for EIP-1559 transactions). Optional.
  • max_priority_fee_per_gas: Max priority fee in wei (decimal string, for EIP-1559 transactions). Optional.
  • nonce: Transaction nonce (decimal string). Optional — auto-determined if omitted.
  • tx_type: Transaction type integer. 0=legacy, 1=EIP-2930, 2=EIP-1559, 4=EIP-7702. Optional.

Policy enforcement: If a policy is enabled, transfers are gated by Privy TEE policy rules. Policy violations return an error. If no policy is attached (default), all transfers are allowed.

EVM — Sign Transaction (without broadcasting)

wallet_sign_transaction(to="0xRecipientAddress", amount="1000000000000000000")
wallet_sign_transaction(to="0xRecipientAddress", amount="1000000000000000000", chain_id=8453)
wallet_sign_transaction(to="0xContractAddress", amount="0", data="0xa9059cbb000000...", chain_id=8453, tx_type=2, max_fee_per_gas="30000000000", max_priority_fee_per_gas="2000000000")

Same parameters as wallet_transfer, plus max_fee_per_gas and max_priority_fee_per_gas for EIP-1559.

Returns: signed_transaction (RLP-encoded hex), encoding ("rlp")

Use cases: pre-sign transactions for later submission, multi-step flows, external broadcast.

EVM — Sign a Message

wallet_sign(message="Hello World")
wallet_sign(message="Verify ownership of this wallet")

Returns: signature (EIP-191 personal_sign format)

Use cases: prove wallet ownership, sign off-chain messages, create verifiable attestations.

EVM — Sign EIP-712 Typed Data

wallet_sign_typed_data(
  domain={"name": "MyDApp", "version": "1", "chainId": 1, "verifyingContract": "0x..."},
  types={"Person": [{"name": "name", "type": "string"}, {"name": "wallet", "type": "address"}]},
  primaryType="Person",
  message={"name": "Alice", "wallet": "0x..."}
)
  • domain: EIP-712 domain separator (name, version, chainId, verifyingContract)
  • types: Type definitions — mapping of type name to array of {name, type} fields
  • primaryType: The primary type being signed (must exist in types)
  • message: The structured data to sign (must match primaryType schema)

Returns: signature (hex)

Use cases: EIP-2612 permit approvals, off-chain order signing (Seaport, 0x), gasless approvals, structured attestations.

Solana — Check Balance

wallet_sol_balance()
wallet_sol_balance(chain="solana", asset="sol")

All parameters are optional. Returns balances with USD-equivalent values.

Solana — Query Transaction History

wallet_sol_transactions()
wallet_sol_transactions(chain="solana", asset="sol", limit=10)

Defaults: chain="solana", asset="sol", limit=20 (max 100).

Solana — Sign and Send Transaction

wallet_sol_transfer(transaction="<base64-encoded-transaction>")
wallet_sol_transfer(transaction="<base64-encoded-transaction>", caip2="solana:EtWTRABZaYq6iMfeYKouRu166VU2xqa1")
  • transaction: Base64-encoded serialized Solana transaction
  • caip2: CAIP-2 chain identifier (default: "solana:5eykt4UsFv8P8NJdTREpY1vzqKqZKvdp" for mainnet, use "solana:EtWTRABZaYq6iMfeYKouRu166VU2xqa1" for devnet)

Policy enforcement: Same as EVM — if a policy is enabled, transfers are gated by Privy TEE policy rules.

Solana — Sign Transaction (without broadcasting)

wallet_sol_sign_transaction(transaction="<base64-encoded-transaction>")
  • transaction: Base64-encoded serialized Solana transaction

Returns: signed_transaction (base64), encoding ("base64")

Use cases: pre-sign transactions for later submission, multi-step flows, external broadcast.

Solana — Sign a Message

wallet_sol_sign(message="<base64-encoded-message>")

Returns: signature (base64)


Common Workflows

Pre-Transfer Check (EVM)

  1. wallet_info() — Confirm wallets are active
  2. wallet_balance(chain="ethereum") — Check available funds on specific chain (or use wallet_get_all_balances())
  3. wallet_transfer(to="0x...", amount="...") — Execute transfer
  4. wallet_transactions(limit=1) — Confirm transaction status

Pre-Transfer Check (Solana)

  1. wallet_info() — Confirm wallets are active
  2. wallet_sol_balance() — Check available SOL funds
  3. wallet_sol_transfer(transaction="...") — Sign and send transaction
  4. wallet_sol_transactions(limit=1) — Confirm transaction status

Monitor All Wallet Activity

  1. wallet_info() — See all wallets
  2. wallet_get_all_balances() — Complete portfolio across ALL chains (EVM + Solana)
  3. wallet_transactions(limit=20) — Recent EVM activity
  4. wallet_sol_transactions(limit=20) — Recent Solana activity

Prove Wallet Ownership

  1. wallet_info() — Get all wallet addresses
  2. wallet_sign(message="I am the owner of this wallet at timestamp 1234567890") — EVM proof
  3. wallet_sol_sign(message="<base64-encoded-message>") — Solana proof

Wei Conversion Reference (EVM)

Amounts are always in wei (smallest unit). Conversion table:

Amount Wei String
0.001 ETH "1000000000000000"
0.01 ETH "10000000000000000"
0.1 ETH "100000000000000000"
1 ETH "1000000000000000000"
10 ETH "10000000000000000000"

Formula: wei = eth_amount * 10^18

Chain ID Reference (EVM)

Chain ID CAIP-2 Native Asset
Ethereum Mainnet 1 eip155:1 eth
Ethereum Sepolia 11155111 eip155:11155111 eth
Base 8453 eip155:8453 eth
Optimism 10 eip155:10 eth
Arbitrum One 42161 eip155:42161 eth
Polygon 137 eip155:137 pol (NOT "matic")
Linea 59144 eip155:59144 eth

Solana CAIP-2 Reference

Network CAIP-2
Solana Mainnet solana:5eykt4UsFv8P8NJdTREpY1vzqKqZKvdp
Solana Devnet solana:EtWTRABZaYq6iMfeYKouRu166VU2xqa1

Policy & Security

  • Privy TEE enforced: Even if the agent is compromised, transfers that violate policy are rejected at the Privy TEE layer
  • Per-wallet policy: Each chain's wallet has its own independent policy
  • Flexible rules: Policy rules are configured via Privy's rule system (address allowlists, value limits, method restrictions, etc.)
  • Allow-all default: New wallets have NO policy — all transactions are allowed. Policy is opt-in.
  • Once enabled: Policy switches to deny-by-default — only transactions matching ALLOW rules are permitted
  • Pass-through: Policy rules are managed directly via Privy (source of truth), no local cache

Policy is optional and managed by the user through the frontend. The agent can propose policy rules via wallet_propose_policy, but the user must approve before they take effect.

Error Handling

Error Meaning Action
"Not running on a Fly Machine" Wallet requires Fly deployment Cannot use wallet locally
"Policy violation: ..." Transfer rejected by Privy policy Check whitelist and daily limits
"HTTP 404" Wallet not found for this machine Wallet may not be created yet
"HTTP 403" OIDC token invalid or expired Token will auto-refresh, retry
how to use wallet

How to use wallet on Cursor

AI-first code editor with Composer

1

Prerequisites

Before installing skills in Cursor, ensure your development environment meets these requirements:

  • Cursor installed and configured on your development machine
  • Node.js version 16.0+ with npm package manager (verify with node --version)
  • Active project directory or workspace where you want to add wallet
2

Execute installation command

Execute the skills CLI command in your project's root directory to begin installation:

$npx skills add https://github.com/starchild-ai-agent/official-skills --skill wallet

The skills CLI fetches wallet from GitHub repository starchild-ai-agent/official-skills and configures it for Cursor.

3

Select Cursor when prompted

The CLI will show a list of available agents. Use arrow keys to navigate and space to select Cursor:

◆ Which agents do you want to install to?
│ ── Universal (.agents/skills) ── always included ────
│ • Amp
│ • Antigravity
│ • Cline
│ • Codex
│ ●Cursor(selected)
│ • Cursor
│ • Windsurf
4

Verify installation

Confirm successful installation by checking the skill directory location:

.cursor/skills/wallet

Reload or restart Cursor to activate wallet. Access the skill through slash commands (e.g., /wallet) or your agent's skill management interface.

Security & Verification Notice

We perform automated surface-level scans (Gen AI Scanner, Socket, Snyk) during installation. These checks detect common vulnerabilities but do not guarantee complete security. Always review skill source code and verify the publisher's reputation before production use.

Skills execute code in your development environment. Always verify the publisher's identity, review recent commits, and test in isolated environments before production deployment.

List & Monetize Your Skill

Submit your Claude Code skill and start earning

GET_STARTED →

Use Cases

User Story & Requirements Generation

Create detailed user stories, acceptance criteria, and feature specs

Example

Generate user stories for 'password reset feature' with acceptance criteria, edge cases, and test scenarios

Reduce spec writing time by 50%, ensure comprehensive coverage

Competitive Analysis

Research competitors, compare features, identify gaps

Example

Analyze 5 competitor products, create feature comparison matrix, suggest differentiation opportunities

Complete competitive research in 2 hours instead of 2 days

Roadmap Prioritization

Evaluate features using frameworks (RICE, ICE, Kano) and create prioritized backlogs

Example

Score 20 feature ideas using RICE framework, generate prioritized roadmap with rationale

Make data-driven prioritization decisions faster

Stakeholder Communication

Draft PRDs, status updates, and stakeholder presentations

Example

Create executive summary of Q3 roadmap, monthly progress report, feature launch announcement

Save 3-5 hours/week on communication overhead

Implementation Guide

Prerequisites

  • Claude Desktop or compatible AI client
  • Access to product documentation and roadmap tools (Jira, Notion, etc.)
  • Understanding of product management frameworks (RICE, Jobs-to-be-Done, etc.)
  • Stakeholder contact information and communication channels

Time Estimate

30-60 minutes to see productivity improvements

Installation Steps

  1. 1.Install product management skill
  2. 2.Start with user story generation for known feature
  3. 3.Progress to competitive analysis: research 2-3 competitors
  4. 4.Use for roadmap prioritization: apply RICE/ICE scoring
  5. 5.Draft stakeholder communications and refine based on feedback
  6. 6.Build template library for recurring PM tasks
  7. 7.Share effective prompts with product team

Common Pitfalls

  • Not validating competitive research—verify facts before sharing
  • Accepting user stories without involving engineering team
  • Over-relying on frameworks without qualitative judgment
  • Not customizing outputs to company culture and communication style
  • Skipping stakeholder validation of generated requirements

Best Practices

✓ Do

  • +Validate research and competitive analysis with real data
  • +Collaborate with engineering when generating technical requirements
  • +Customize frameworks and templates to your company context
  • +Use skill for first drafts, refine with stakeholder input
  • +Document successful prompt patterns for PM tasks
  • +Combine AI efficiency with human judgment and intuition

✗ Don't

  • Don't publish competitive analysis without fact-checking
  • Don't finalize user stories without engineering review
  • Don't make prioritization decisions solely on AI scoring
  • Don't skip customer validation of generated requirements
  • Don't ignore company-specific context and culture

💡 Pro Tips

  • Provide context: company goals, constraints, customer feedback
  • Ask for alternatives: 'Show 3 ways to prioritize this roadmap'
  • Request stakeholder-specific formatting: 'Executive summary vs. engineering spec'
  • Use skill for 70% generation + 30% customization to company needs

When to Use This

✓ Use When

Use for user story writing, competitive research, roadmap prioritization, stakeholder communication, and PRD drafting. Best for reducing repetitive documentation and research work.

✗ Avoid When

Avoid for strategic product vision (requires deep customer empathy), pricing decisions (needs market and financial expertise), or when face-to-face customer discovery is more valuable than speed.

Learning Path

  1. 1Basic: user stories, feature specs, status updates
  2. 2Intermediate: competitive analysis, prioritization frameworks, PRDs
  3. 3Advanced: product strategy, go-to-market planning, OKR setting
  4. 4Expert: product vision, market positioning, business model innovation

Discussion

Product Hunt–style comments (not star reviews)
  • No comments yet — start the thread.
general reviews

Ratings

4.731 reviews
  • Advait Garcia· Dec 12, 2024

    Useful defaults in wallet — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.

  • Shikha Mishra· Dec 8, 2024

    We added wallet from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.

  • Ama Thompson· Dec 8, 2024

    wallet has been reliable in day-to-day use. Documentation quality is above average for community skills.

  • Anika Smith· Dec 4, 2024

    I recommend wallet for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.

  • Rahul Santra· Nov 27, 2024

    Useful defaults in wallet — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.

  • Ren Singh· Nov 27, 2024

    Solid pick for teams standardizing on skills: wallet is focused, and the summary matches what you get after install.

  • Chinedu Dixit· Nov 3, 2024

    We added wallet from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.

  • Anaya Srinivasan· Oct 22, 2024

    wallet reduced setup friction for our internal harness; good balance of opinion and flexibility.

  • Pratham Ware· Oct 18, 2024

    Registry listing for wallet matched our evaluation — installs cleanly and behaves as described in the markdown.

  • Ren Gonzalez· Oct 18, 2024

    wallet is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.

showing 1-10 of 31

1 / 4