Skip to main content

What you will learn

  • How the OpenClaw adapter connects to ISCL Core
  • How to configure OpenClaw skills to use Clavion for signing
  • How to run the full demo stack with Docker Compose
  • How to write a custom OpenClaw skill that uses Clavion

Overview

The @clavion/adapter-openclaw package provides thin skill wrappers that translate OpenClaw’s skill interface into ISCL TxIntents. When an OpenClaw agent invokes a crypto skill, the adapter constructs a TxIntent and sends it to ISCL Core via the ISCLClient.

Step 1: Start the Docker Compose stack

The easiest way to run OpenClaw + Clavion together is the Docker Compose demo stack:
This starts three services: Verify all services are running:

Step 2: Verify connectivity

Check that ISCL Core is healthy:
Check that the OpenClaw agent can reach ISCL Core:
You should see the ISCLClient health check succeeding on startup.

Step 3: Run a demo transfer

The demo stack includes a pre-configured transfer script:
This script:
  1. Constructs a TxIntent for a USDC transfer on the Anvil fork
  2. Sends it through the OpenClaw skill wrapper
  3. Passes through ISCL’s pipeline (policy, simulation, approval, signing)
  4. Broadcasts to the Anvil fork
  5. Verifies the on-chain balance change

Step 4: Run a demo swap

This executes a WETH → USDC swap through Uniswap V3 on the Anvil fork.

Writing a custom OpenClaw skill

An OpenClaw skill that uses Clavion follows this pattern:

Verification

Docker Compose stack starts with all three services healthy
Demo transfer script completes and tokens move on Anvil
Demo swap script completes with WETH → USDC exchange
Audit trail shows all events correlated by intent ID

Next steps