How do I install the Bankr Agent - Arbitrary Transactions skill?

Run npx skillmds@latest add enuno/bankr-agent-arbitrary-transactions in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Bankr Agent - Arbitrary Transactions safe to use?

This skill has not completed SkillMD's automated safety review yet. Independent scanners report: SkillSpector: PASS, Skill Scanner: PASS. Capability flags: docs only. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Bankr Agent - Arbitrary Transactions?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Bankr Agent - Arbitrary Transactions free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Bankr Agent - Arbitrary Transactions?

enuno (@enuno) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Bankr Agent - Arbitrary Transactions by enuno

Name: Bankr Agent - Arbitrary Transactions
Rating: 4.2 (5 reviews)
Author: enuno

Bankr Agent - Arbitrary Transactions

This skill should be used when the user wants to "submit a transaction", "execute calldata", "send raw transaction", "submit transaction JSON", or provides a JSON object with to/data/value/chainId fields. Handles raw EVM transaction submission.

enuno Updated Sep 9, 2026 1 repo stars

File contents

Arbitrary Transaction Submission

Submit raw EVM transactions with explicit calldata to any supported chain.

JSON Format

{
  "to": "0x...",
  "data": "0x...",
  "value": "0",
  "chainId": 8453
}

Field	Type	Description
`to`	string	Target contract address (0x + 40 hex chars)
`data`	string	Calldata to execute (0x + hex string)
`value`	string	Amount in wei (e.g., "0", "1000000000000000000")
`chainId`	number	Target chain ID

Supported Chains

Chain	Chain ID
Ethereum	1
Polygon	137
Base	8453
Unichain	130

Prompt Examples

Submit a raw transaction:

Submit this transaction:
{
  "to": "0x1234567890abcdef1234567890abcdef12345678",
  "data": "0xa9059cbb000000000000000000000000recipient00000000000000000000000000000000000000000000000000000000000f4240",
  "value": "0",
  "chainId": 8453
}

Execute calldata on a contract:

Execute this calldata on Base:
{
  "to": "0x833589fcd6edb6e08f4c7c32d4f71b54bda02913",
  "data": "0x095ea7b30000000000000000000000007a250d5630b4cf539739df2c5dacb4c659f2488dffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffff",
  "value": "0",
  "chainId": 8453
}

Send ETH with calldata:

Submit transaction with value:
{
  "to": "0xRecipientAddress...",
  "data": "0x",
  "value": "1000000000000000000",
  "chainId": 1
}

Validation Rules

Field	Validation
`to`	Must be 0x followed by exactly 40 hex characters
`data`	Must start with 0x, can be "0x" for empty calldata
`value`	Wei amount as string, use "0" for no value transfer
`chainId`	Must be a supported chain ID

Common Issues

Issue	Resolution
Unsupported chain	Use chainId 1, 137, 8453, or 130
Invalid address	Ensure 0x + 40 hex chars
Invalid calldata	Ensure proper hex encoding with 0x prefix
Transaction reverted	Check calldata encoding and contract state
Insufficient funds	Ensure wallet has enough ETH/MATIC for gas + value

---name: bankr-agent-arbitrary-transactionsdescription: This skill should be used when the user wants to "submit a transaction", "execute calldata", "send raw transaction", "submit transaction JSON", or provides a JSON object with to/data/value/chainId fields. Handles raw EVM transaction submission.--- # Arbitrary Transaction Submission Submit raw EVM transactions with explicit calldata to any supported chain. ## JSON Format ```json { "to": "0x...", "data": "0x...", "value": "0", "chainId": 8453 } ``` | Field | Type | Description | |-------|------|-------------| | `to` | string | Target contract address (0x + 40 hex chars) | | `data` | string | Calldata to execute (0x + hex string) | | `value` | string | Amount in wei (e.g., "0", "1000000000000000000") | | `chainId` | number | Target chain ID | ## Supported Chains | Chain | Chain ID | |-------|----------| | Ethereum | 1 | | Polygon | 137 | | Base | 8453 | | Unichain | 130 | ## Prompt Examples **Submit a raw transaction:** ``` Submit this transaction: { "to": "0x1234567890abcdef1234567890abcdef12345678", "data": "0xa9059cbb000000000000000000000000recipient00000000000000000000000000000000000000000000000000000000000f4240", "value": "0", "chainId": 8453 } ``` **Execute calldata on a contract:** ``` Execute this calldata on Base: { "to": "0x833589fcd6edb6e08f4c7c32d4f71b54bda02913", "data": "0x095ea7b30000000000000000000000007a250d5630b4cf539739df2c5dacb4c659f2488dffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffff", "value": "0", "chainId": 8453 } ``` **Send ETH with calldata:** ``` Submit transaction with value: { "to": "0xRecipientAddress...", "data": "0x", "value": "1000000000000000000", "chainId": 1 } ``` ## Validation Rules | Field | Validation | |-------|------------| | `to` | Must be 0x followed by exactly 40 hex characters | | `data` | Must start with 0x, can be "0x" for empty calldata | | `value` | Wei amount as string, use "0" for no value transfer | | `chainId` | Must be a supported chain ID | ## Common Issues | Issue | Resolution | |-------|------------| | Unsupported chain | Use chainId 1, 137, 8453, or 130 | | Invalid address | Ensure 0x + 40 hex chars | | Invalid calldata | Ensure proper hex encoding with 0x prefix | | Transaction reverted | Check calldata encoding and contract state | | Insufficient funds | Ensure wallet has enough ETH/MATIC for gas + value |

Frequently asked questions