Token导航 LogoToken导航

Agent Skill · 效率

soho-pay(苏荷支付)

soho-pay 用于补充效率相关能力,适合在 OpenClaw 中需要让 Agent 承接效率相关任务时使用。可结合来源仓库、安装命令和原始 README 继续核验具体用法。安装前建议确认权限范围、维护状态,以及是否会触发联网、命令执行或文件读写。

soho-pay 是效率类 Agent Skill,可用宿主为 OpenClaw,通过ClawHub获取,权限为接触敏感数据;许可证为 MIT-0,第三方扫描已通过,按安装量在效率类的 21,003 个 Skill 里排第 4,894。

总安装 12,199周安装 524GitHub Stars 公开资料未说明下载 4,276核验 2026-05-01

安装说明

本站只整理中文说明,不托管安装包,也不代用户安装。
GitHub
许可证
MIT-0
版本
2.0.0

安装方式

通过对话安装

复制提示词发给支持本地命令或 Skills 的 AI 助手,先确认命令和权限,再让它执行。

请帮我安装这个 Agent Skill:soho-pay(苏荷支付)
来源仓库:https://github.com/max-clinch/soho-pay
安装命令:
openclaw skills install soho-pay
安装前请先检查当前环境是否支持对应 CLI,并向我确认将要执行的命令、安装目录、联网范围和文件读写权限;确认后再执行。

命令行安装

复制命令到本机终端执行。该命令会通过 OpenClaw 从第三方来源获取 Skill;本站只展示命令,不托管安装包,也不自动执行。

ClawHubOpenClaw
openclaw skills install soho-pay

这个 Skill 是做什么的

效率类 Skill 把重复的整理、汇总、转换工作交给助手完成,减少手工复制粘贴。

soho-pay 使用 EIP-712 签名在 SOHO Pay 信用层上发起支付。适用于区块链支付和信用交易场景。支持智能合约交互和支付流程自动化。安装方式:openclaw skills install soho-pay,宿主为 OpenClaw。使用前请确认权限范围和维护状态,注意可能涉及加密操作或网络请求。

上手步骤

4 步
  1. 1

    确认自己的宿主工具

    公开资料标注支持 OpenClaw;先确认自己用的是其中之一,再按对应工具的 Skills 目录放置。

  2. 2

    拿到安装命令

    可以直接复制的命令是 openclaw skills install soho-pay;命令里的占位符换成自己的路径或密钥再执行。

  3. 3

    安装后重启宿主

    命令执行完要完全退出宿主工具再打开,让新装的 Skill 被重新扫描到,否则列表里可能看不到。

  4. 4

    按最小权限试用

    它需要接触敏感数据,先在测试目录或测试账号里跑,确认没问题再放到正式项目。

常见问题

6 条

soho-pay 怎么安装?

在终端执行 openclaw skills install soho-pay。装完完全退出宿主工具再打开,让它重新扫描本地 Skill。

soho-pay 支持哪些 AI 工具?

公开资料标注支持 OpenClaw。其他工具只要能读取本地 Skill 目录,一般也能手动放进去,但要自己确认触发方式是否一致。

soho-pay 需要什么权限?

权限级别是接触敏感数据。该 Skill 可能接触密钥、Token、环境变量或敏感配置,应进入高风险复核队列,默认不自动发布。

soho-pay 是免费的吗?

来源标注的许可证是 MIT-0。本站不代收任何费用,也不托管安装包;能否商用、要不要署名,以许可证原文为准。

soho-pay 用的人多吗?

公开数据是累计安装 12,199 次,近一周安装 524 次,下载 4,276 次。这些数字来自第三方目录统计,只能当作热度参考,不代表质量或安全性。

soho-pay 安全吗?

第三方扫描结果为通过,但这只覆盖已知的静态检查项,不能替代自己读一遍源码和安装命令。

值得选的地方和要先想清楚的地方

值得选的地方

  • 专注 OpenClaw 一种宿主,触发方式和使用习惯不用来回切换。
  • 许可证明确为 MIT-0,商用和分发边界好判断。
  • 第三方扫描已通过,常见的高风险行为没有命中。

先想清楚的地方

  • 需要接触敏感数据,装到常用环境前要先评估影响面。
  • 第三方目录整理,版本更新和行为细节以来源仓库为准。

适不适合你

更适合

  • 已经在用 OpenClaw,想直接扩展它能力的人。
  • 需要处理效率类任务、又不想每次都手写提示词的人。
  • 需要许可证清楚、并且有第三方扫描结果的团队项目。

不太适合

  • 环境里有大量密钥、凭证,不方便给第三方 Skill 读取的人。
  • 需要厂商级技术支持和 SLA 的生产系统。

效率类 Skill 对比

6 个同类
Skill总安装GitHub 星权限许可证扫描
github

GitHub 代码协作 · OpenClaw

7,632,918545需要联网MIT-0通过
nano-pdf

Nano PDF 文档 · OpenClaw

4,249,476231需要联网MIT-0通过
auto-updater

自动更新程序 · OpenClaw

2,964,063386操作浏览器MIT-0通过
video-frames

视频帧 · OpenClaw

2,621,304112需要联网MIT-0通过
gemini

Gemini 助手 · OpenClaw

2,547,39648需要联网MIT-0有提醒
soho-pay

苏荷支付 · 本页

12,199—接触敏感数据MIT-0通过

按安装量取同分类前几名;数字来自第三方目录统计,只作热度参考,不代表质量结论。

SKILL.md 原文

name
sohopay
description
Initiate payments on the SOHO Pay credit layer using EIP-712 signatures.
invocation
manual
require_confirmation
true

SOHO Pay — Credit Layer Payments

This skill orchestrates payments through the SOHO Pay Creditor smart contract using the spendWithAuthorization EIP-712 flow.

This skill is manual-invocation only. It must not be triggered autonomously by a model. Every invocation requires explicit user confirmation.


Architecture — Three-Party Separation

┌──────────────────┐     ┌──────────────────┐     ┌──────────────────┐
│  Wallet Signer   │     │   SoHo (Credit)  │     │   Blockchain     │
│  (user/operator) │     │                  │     │   (Base)         │
│                  │     │  Credit checks   │     │                  │
│  Signs EIP-712   │────▶│  JIT funding     │────▶│  Settlement      │
│  Owns keys       │     │  Authorization   │     │  Creditor.sol    │
│                  │     │                  │     │                  │
│  MPC / HSM /     │     │  NEVER signs     │     │                  │
│  Turnkey / Privy │     │  NEVER holds keys│     │                  │
└──────────────────┘     └──────────────────┘     └──────────────────┘

SoHo is a credit layer only. It does not custody, hold, generate, or control any signing keys or key shards, and it does not produce EIP-712 signatures.

All EIP-712 signatures come from a separate Wallet Signer owned and controlled by the user or agent operator (e.g., MPC provider like Turnkey/Privy/Fireblocks, or a user wallet).

The skill orchestrates between:

  • Wallet Signer — signing (user/operator-controlled)
  • SoHo — credit checks + just-in-time funding (credit layer only)
  • Blockchain — settlement

Usage

node scripts/pay.js <amount> <merchantAddress> [payerAddress]
ArgumentDescription
amountDecimal USDC value (e.g. 10, 0.5)
merchantAddressExplicit 0x-prefixed EVM address (checksummed). Never a name.
payerAddressRequired when SIGNER_PROVIDER=WALLET_SIGNER_REMOTE

Example — Base Sepolia with local key (dev only)

export RPC_URL=https://sepolia.base.org
export CHAIN_ID=84532
export SIGNER_PROVIDER=LOCAL_PRIVATE_KEY
export SOHO_DEV_PRIVATE_KEY=0xabc...

node scripts/pay.js 10 0x1234567890abcdef1234567890abcdef12345678

Example — Base Sepolia with remote wallet signer (production pattern)

export RPC_URL=https://sepolia.base.org
export CHAIN_ID=84532
export SIGNER_PROVIDER=WALLET_SIGNER_REMOTE
export WALLET_SIGNER_SERVICE_URL=https://your-mpc-signer.example.com
export SIGNER_SERVICE_AUTH_TOKEN=sk_live_...

node scripts/pay.js 10 0xMERCHANT... 0xPAYER...

Workflow

  1. Validate config — all env vars checked with Zod at startup; unknown chains rejected.
  2. Parse inputs — amount and explicit merchant address (no name-to-address generation).
  3. Pre-flight credit checks — SoHo credit layer verifies borrower registration, active status, credit limit.
  4. Sign EIP-712 — Wallet Signer (user-controlled) produces signature. SoHo never signs.
  5. Submit tx — call spendWithAuthorization on the Creditor contract.
  6. Return result — transaction hash + block number.

Supported Networks

NetworkChain IDStatus
Base Sepolia84532Supported
Base Mainnet8453Requires SOHO_MAINNET_CONFIRM=YES

Unknown chain IDs are rejected at config validation time.

Contract Addresses (Base Sepolia)

ContractAddress
Creditor0x1867a19816f38ec31ec3af1be15fd7104f161978
Borrower Manager0x76e51158015e869ab2875fa17b87383d8886e93c
USDC (test)0x55b8ff660d4f0f176de84f325d39a773a7a3bda7

Security Model

Key Custody Boundary

EntityRoleHolds keys?
Wallet SignerProduces EIP-712 signaturesYes — user/operator-controlled
SoHoCredit authorization + JIT fundingNo — credit layer only
This skillOrchestration between the aboveNo — passes typed data to signer

SoHo must NEVER custody, hold, generate, or control any signing keys or key shards.

Wallet Signer Providers

ProviderWhen to useRisk level
WALLET_SIGNER_REMOTEProduction / MainnetLow — keys stay in user's MPC/HSM (Turnkey, Privy, Fireblocks, etc.)
LOCAL_PRIVATE_KEYDev / Testnet onlyHigh — raw key in env
  • Default and recommended: WALLET_SIGNER_REMOTE. The skill sends EIP-712 typed data to the user's wallet signing service and never touches private keys.
  • Dev-only fallback: LOCAL_PRIVATE_KEY is gated to testnet chain IDs. Using it on mainnet requires DEV_ALLOW_LOCAL_KEY=YES and is strongly discouraged.

Mainnet Safety Gate

Transactions on Base Mainnet (CHAIN_ID=8453) are refused unless SOHO_MAINNET_CONFIRM=YES is set. This prevents accidental mainnet spends during development.

Recipient Address Policy

The skill never derives or generates an address from a merchant name. The merchantAddress argument must be an explicit, valid, checksummed EVM address. Any non-address input is rejected with an error.

Invocation Policy

  • invocation: manual — the skill cannot be triggered autonomously.
  • require_confirmation: true — the orchestrator must obtain user confirmation before execution.
  • A runtime guard rejects execution if SOHO_AUTONOMOUS=true is detected in the environment.

Threat Model & Mitigations

ThreatMitigation
Signer compromiseDefault to WALLET_SIGNER_REMOTE (MPC/HSM); keys never leave the user's signing service. Local key gated to testnet only.
Replay attacksRandom 32-byte nonce per transaction; validAfter / expiry window (10 min). On-chain nonce check in Creditor contract.
Wrong merchant addressAddress generation from names removed. Only explicit checksummed EVM addresses accepted; checksum validated before signing.
Accidental mainnet transactionSOHO_MAINNET_CONFIRM=YES safety gate required for chain ID 8453.
Autonomous invocation with signing authorityinvocation: manual in metadata; require_confirmation: true; runtime guard blocks SOHO_AUTONOMOUS=true.
SoHo used as signerArchitecture enforces SoHo = credit-only. No signing key env vars reference SoHo as a signer. Skill never passes keys to SoHo API.
Undeclared env var dependenciesAll env vars declared in skill.json with types and sensitivity flags.
MITM on wallet signer serviceUse HTTPS for WALLET_SIGNER_SERVICE_URL; bearer token auth via SIGNER_SERVICE_AUTH_TOKEN.

Environment Variables

Required (all modes)

VariableExampleDescription
RPC_URLhttps://sepolia.base.orgJSON-RPC endpoint
CHAIN_ID8453284532 (Sepolia) or 8453 (Mainnet)
SIGNER_PROVIDERWALLET_SIGNER_REMOTEWALLET_SIGNER_REMOTE or LOCAL_PRIVATE_KEY

Required for WALLET_SIGNER_REMOTE

VariableDescriptionSensitive
WALLET_SIGNER_SERVICE_URLBase URL of user/operator's wallet signing serviceNo
SIGNER_SERVICE_AUTH_TOKENBearer auth token for the wallet signing serviceYes

SoHo Credit Layer

VariableDescriptionSensitive
SOHO_API_URLSoHo credit-layer API (credit checks, JIT funding)No

Required for LOCAL_PRIVATE_KEY (dev / testnet only)

VariableDescriptionSensitive
SOHO_DEV_PRIVATE_KEYUser/operator's raw hex private key (NOT a SoHo key)Yes

Conditional

VariableWhen required
SOHO_MAINNET_CONFIRMMust be YES when CHAIN_ID=8453
DEV_ALLOW_LOCAL_KEYSet YES to allow local key on non-testnet (dangerous)

Dependencies

Install with:

npm install
PackagePurpose
ethersEVM interactions, EIP-712 signing
dotenvLoad .env files
zodEnv var validation at startup

平台分布

OpenClaw

93.65%
按下载量换算4,004

安全审计

VirusTotal

通过

ClawScan

通过

Static analysis

未展示

权限和风险

接触敏感数据

该 Skill 可能接触密钥、Token、环境变量或敏感配置,应进入高风险复核队列,默认不自动发布。

安装前确认

本站仅展示第三方公开信息,不托管安装包,不提供自动安装或运行环境。安装前应自行审查源码、依赖和命令行为。目前只有一个公开来源,建议同时核对源仓库。

继续浏览同类 Skills