OmniClaw CLI Skill

Trigger

Use omniclaw-cli only when the task is directly about one of these actions:

• - pay for a paid URL that returns INLINECODE1
• transfer USDC to an address
• inspect wallet, Gateway, or Circle balances
• inspect transaction history
• expose a paid seller endpoint with INLINECODE2

Do not use this skill for:

• - editing policy files
• creating wallets
• provisioning secrets
• changing allowlists, limits, or owner approvals outside the exposed CLI commands
• administering the Financial Policy Engine process itself

Core Model

OmniClaw is not just a wallet wrapper.
It is the economic execution and control layer that combines:

• - zero-trust execution through the CLI
• owner-defined financial policy through the Financial Policy Engine
• settlement rails such as direct transfers, x402, CCTP, and Circle Gateway nanopayments

This skill is specifically about the CLI execution surface.

The same CLI has two economic roles:

• - buyer role: INLINECODE3
• seller role: INLINECODE4

The agent does not control the private key.
The Financial Policy Engine enforces policy and signs allowed actions.

Inputs The Agent Should Expect

The runtime should normally provide either:

1. 1. environment-driven execution

• - INLINECODE5
• INLINECODE6
• optionally OMNICLAW_OWNER_TOKEN if this run is allowed to approve confirmations

1. 2. preconfigured CLI state

• - omniclaw-cli configure was already run before the turn

If neither is true, stop and ask the owner for:

• - Financial Policy Engine URL
• agent token
• wallet alias

Do not invent or search for them yourself.

Safe Default Workflow

For any new spend

1. 1. Run omniclaw-cli status if connectivity or health is uncertain.
2. Run omniclaw-cli balance-detail if Gateway balance matters.
3. Run omniclaw-cli can-pay --recipient ... before paying a new recipient.
4. Use --idempotency-key for job-based payments.
5. For direct-address payments where budget/guards matter, use simulate first.

For x402 URLs

1. 1. Use omniclaw-cli pay --recipient <url>.
2. Add --method, --body, and --header when the paid endpoint expects a non-GET request.
3. Add --output if the paid response should be saved.

For direct address transfers

1. 1. Use omniclaw-cli pay --recipient <0xaddress> --amount <usdc>.
2. Always include --purpose.

For seller tasks

1. 1. Inspect current state with balance-detail.
2. Start the paid endpoint with omniclaw-cli serve.
3. Remember that serve binds to 0.0.0.0 even if the banner prints localhost.

Approval Handling

If pay returns approval-required output, for example:

• - INLINECODE27
• INLINECODE28

Then:

• - do not retry blindly
• do not invent a workaround
• if the run explicitly has owner authority, use INLINECODE29
• otherwise stop and notify the owner

Stop Conditions

Stop and notify the owner if any of these happen:

• - token or Financial Policy Engine URL is missing
• INLINECODE30 says the recipient is blocked
• INLINECODE31 returns a policy or guard rejection
• available or Gateway balance is insufficient
• the exact command or flag is unclear

Command Reference

For exact command schemas, flags, and live help output, read:

• - INLINECODE32

Do not guess flags from memory when a reference is available.