ClawKit Logo
ClawKitReliability Toolkit
Back to Registry
Official Verified

psilo

Use this skill when an agent needs to: (1) create on-chain escrow contracts via EscrowFactory, (2) release escrowed funds via arbiter-signed transactions, and (3) interact with the Pakt Escrow service using the @pakt/psilo SDK. Authentication and wallet: choose SIWA or Evalanche.

skill-install — Terminal

Install via CLI (Recommended)

clawhub install openclaw/skills/skills/beardkoda/psilo
Or

Pakt Escrow API Skill

This skill provides on-chain escrow contract management for AI agents. Use the @pakt/psilo SDK for all escrow operations: create contracts, query status, prepare seller/buyer transactions, and trigger release. Release requires the seller and buyer to each sign an on-chain confirmation transaction, after which the system arbiter executes the final release.

Primary interface: Install @pakt/psilo and use PsiloSDK.init({ baseUrl }). All operations go through sdk.escrow: getChains(), getAssets(chainId), create(dto), getStatus(chainId, escrowAddress), updateStatus(escrowAddress, { chainId, address }), release(escrowAddress, { recipient? }).

Authentication Flow (Read this first)

Authenticate before calling protected escrow endpoints.

Public auth and registration endpoints

  • POST /api/auth/register
  • POST /api/auth/nonce
  • POST /api/auth/verify

All other endpoints require Authorization: Bearer <accessToken>.

SIWA auth flow

  1. Broadcast on-chain register tx from the agent wallet and obtain agentId from the Registered event.
  2. Register/update on platform with POST /api/auth/register so SIWA sign-in can issue JWTs.
  3. Request nonce with POST /api/auth/nonce using { address, agentId, agentRegistry? }.
  4. Sign SIWA message with the agent wallet/keyring.
  5. Verify signature with POST /api/auth/verify using { message, signature }.
  6. Use returned accessToken in Authorization: Bearer <token> for protected endpoints.

If 401 is returned, request a new nonce and verify again to refresh authentication.


Security and Transparency Checklist

This section is intentionally explicit to reduce security-review ambiguity for skill registries and automated scanners.

Capability scope (what this skill is allowed to do)

  • Create escrow contracts through @pakt/psilo / escrow API
  • Read escrow-related metadata (chains, assets, status)
  • Prepare seller/buyer release-readiness transactions
  • Trigger release endpoint only when policy allows (arbiter/system flow)

Out-of-scope behavior (what this skill must NOT do)

  • Must not exfiltrate secrets, mnemonics, or private keys
  • Must not run unrelated shell commands, package installs, or background services
  • Must not access unrelated files outside the escrow workflow
  • Must not perform autonomous fund transfers outside explicit escrow operations requested by the user

Required credentials and env vars

Minimum expected inputs:

  • ESCROW_API_URL (or use default in docs examples)
  • Authorization: Bearer <accessToken> for protected endpoints
  • Optional system-side release secret (X-Release-Secret) for release endpoints

For Hugging Face / model / unrelated infrastructure keys: out of scope for this skill.

Data handling and storage

Metadata

Author@beardkoda
Stars4473
Views1
Updated2026-05-01
View Author Profile
AI Skill Finder

Not sure this is the right skill?

Describe what you want to build — we'll match you to the best skill from 16,000+ options.

Find the right skill
Add to Configuration

Paste this into your clawhub.json to enable this plugin.

{
  "plugins": {
    "official-beardkoda-psilo": {
      "enabled": true,
      "auto_update": true
    }
  }
}
Safety NoteClawKit audits metadata but not runtime behavior. Use with caution.