Distribute Tokens

Sends USDC or ETH to recipient lists via the Bankr Wallet API with per-recipient idempotency.

Updated May 25, 2026
One-click install
npx skills add https://github.com/Cbowcrptex/CBOWCRYPTEX --skill distribute-tokens-cbowcrptex
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: Distribute Tokens
Source: https://github.com/Cbowcrptex/CBOWCRYPTEX/tree/main/skills/distribute-tokens
Command: npx skills add https://github.com/Cbowcrptex/CBOWCRYPTEX --skill distribute-tokens-cbowcrptex

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Sending token rewards to many contributors manually risks double-payments on re-runs, failed handle lookups, and partial runs with no recovery trail. This Skill automates batch token distribution on Base with safeguards against duplicate sends and insufficient funds. ## Core Features & Use Cases - Per-recipient idempotency: Persists state in memory/state/distributions.json keyed by list, recipient, and UTC date so a successful transfer is never re-sent, even across crashes or workflow restarts. - Two-phase resolve-then-execute: Validates the API key, wallet write access, and balance (with 5% headroom), resolves Twitter/X handles to EVM addresses via the Bankr Agent API, and prints a full plan before any transfer. - Dry-run and recovery: Preview the entire distribution plan without sending, and resume partial runs safely since state is written after every single transfer. - Use Case: Run weekly contributor payouts by defining a YAML list of handles and addresses, then execute with a single command and receive a summary with Basescan transaction links. ## Quick Start Ask the agent to run the distribute-tokens skill with your list label, for example by saying "distribute tokens to the contributors list" or prefix with "dry-run:" to preview the plan first.

Frequently Asked Questions about Distribute Tokens

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I send tokens to multiple contributors automatically?▼

Define a recipient list in memory/distributions.yml with handles or EVM addresses and amounts, then run the skill with the list label. It resolves handles, validates your balance, and sends each transfer via the Bankr Wallet API with a summary report.

How do I prevent duplicate token payments when re-running a distribution?▼

The skill stores per-recipient idempotency state in memory/state/distributions.json keyed by list, recipient, and UTC date. Any recipient already marked completed that day is skipped with their prior transaction hash, even across crashes or restarts.

Can I preview a token distribution before sending real funds?▼

Yes, pass dry-run:LABEL as the variable to execute only the resolve phase. It outputs the full plan showing resolved addresses, amounts, deduplicated recipients, and failures without performing any transfers.

What happens if my Bankr API key is read-only or rate-limited?▼

A read-only key returns HTTP 403 during preflight and aborts with an error before any send. HTTP 429 rate limits trigger a 60-second wait and one retry; persistent limits abort remaining rows while preserving state for completed transfers.

Which tokens and networks does Bankr token distribution support?▼

The skill supports USDC and native ETH on the Base chain only. USDC uses the contract address 0x833589fcd6edb6e08f4c7c32d4f71b54bda02913, and ETH transfers set the isNativeToken flag with a zero token address.