首页 › 龙虾技能列表 › Use Circle Wallets

Use Circle Wallets

v0.1.0

Choose and implement the right Circle wallet type for your application. Compares developer-controlled, user-controlled, and modular (passkey) wallets across...

0· 155·0 当前·0 累计
by @mscandlen3 (Madelyn)·MIT-0
下载技能包
License
MIT-0
最后更新
2026/4/14
安全扫描
VirusTotal
无害
查看报告
OpenClaw
可疑
medium confidence
The skill is mostly a documentation-only decision guide and doesn't ask for credentials or install code, but there are a few small incoherencies (external doc pointer and implicit dependency on other skills) that deserve vetting before use.
评估建议
This is primarily a read-only decision guide and does not itself request credentials or install code, so the immediate risk is low. Before installing/using it: (1) verify the external links (especially https://developers.circle.com/llms.txt and the GitHub README) to ensure they point to legitimate Circle documentation; the llms.txt path looks unusual and should be checked. (2) Confirm that the referenced implementation skills (use-developer-controlled-wallets, use-user-controlled-wallets, use-mo...
详细分析 ▾
✓ 用途与能力
The name/description match the SKILL.md content: it is a decision guide comparing Circle wallet types and directs the agent to trigger more specific wallet skills for implementation. No unusual binaries, env vars, or installs are requested, which is proportionate for a guidance skill.
ℹ 指令范围
The instructions stay within wallet-selection guidance, but they (a) instruct the agent to "TRIGGER" other skills by name (e.g., use-developer-controlled-wallets) which creates an implicit dependency on those skills and their privileges, and (b) include a prominent 'Always read this first' pointer to https://developers.circle.com/llms.txt (an unusual filename) — both warrant verification. The sheet contains strong prescriptive 'ALWAYS/NEVER' rules that could cause the agent to rigidly choose flows; this is stylistic but may lead to surprising behavior if the rest of the skill ecosystem isn't vetted.
✓ 安装机制
Instruction-only skill with no install spec and no code files; nothing will be written to disk or executed by install, which is low risk.
✓ 凭证需求
The skill requests no environment variables, credentials, or config paths — appropriate for a documentation/decision skill. However, because it instructs the agent to invoke other skills, check those skills for credential requests before granting them permission.
ℹ 持久化与权限
The skill is not flagged always:true and uses normal agent invocation. The main privilege-related concern is indirect: it tells the agent to invoke other wallet implementation skills — those downstream skills may require elevated credentials or persistent access, so vet them individually.
安全有层次，运行前请审查代码。

License

MIT-0

可自由使用、修改和再分发，无需署名。

运行时依赖

无特殊依赖

版本

latestv0.1.02026/3/17

- Initial release of the "use-circle-wallets" skill. - Provides a comprehensive comparison of Circle wallet types: developer-controlled, user-controlled, and modular (passkey). - Includes decision guide and implementation patterns for choosing the right custody model, key management, and account types. - Outlines strict rules for wallet selection and integration best practices. - Offers quick scenario-based recommendations and direct links to official Circle documentation.

● 无害

安装命令 点击复制

官方npx clawhub@latest install use-circle-wallets
镜像加速npx clawhub@latest install use-circle-wallets --registry https://cn.clawhub-mirror.com

技能文档

Overview

Circle offers three wallet types -- developer-controlled, user-controlled, and modular -- each with different custody models, account types, key management, and capabilities. This skill helps you pick the right one.

Quick Comparison

Developer-ControlledUser-ControlledModular (Passkey)
CustodyDeveloperUserUser
AuthEntity secret (backend)Social login / email OTP / PINPasskey (WebAuthn)
Account typesEOA, SCAEOA, SCAMSCA only
Gas sponsorshipSCA via Gas StationSCA via Gas StationGas Station or third-party paymaster
Custom modulesNoNoYes
ArchitectureBackend SDK onlyBackend + frontend SDKsFrontend SDK only

Decision Guide

For the latest supported blockchains: https://developers.circle.com/wallets/account-types

Step 1 -- Who controls the keys?

  • Developer controls (no user approval) -> Developer-controlled wallets -> Step 3
  • End user controls -> Step 2

Step 2 -- Auth method?

  • Passkey (WebAuthn biometric) with extensible modules -> Modular wallets -> Step 4
  • Social login, email OTP, or PIN -> User-controlled wallets -> Step 3

Step 3 -- Account type?

  • Solana, Aptos, or NEAR -> EOA (only option)
  • Ethereum mainnet -> EOA (SCA gas costs prohibitive, MSCA not supported)
  • L2 (Arbitrum, Base, Polygon, Optimism, etc.) -> SCA if gas sponsorship or batching needed; EOA if max TPS needed

Step 4 -- Chain check (Modular wallets)

  • Supported: Arbitrum, Avalanche, Base, Monad, Optimism, Polygon, Unichain
  • NOT supported: Ethereum, Solana, Aptos, NEAR. Fall back to user-controlled wallets with SCA.

Example Scenarios

ScenarioDecisionSkill
Payment backend, programmatic payouts, high TPSDeveloper-controlled + EOAuse-developer-controlled-wallets
Consumer app with Google/Apple login, gasless UXUser-controlled + SCA on L2use-user-controlled-wallets
DeFi app with biometric auth, custom modulesModular on L2use-modular-wallets
NFT marketplace on Ethereum L1User-controlled + EOAuse-user-controlled-wallets
AI agent, autonomous multi-chain transactionsDeveloper-controlled + EOAuse-developer-controlled-wallets

Implementation Patterns

Once a wallet type has been determined, TRIGGER the corresponding skill:

  • Developer-controlled -> use-developer-controlled-wallets skill
  • User-controlled -> use-user-controlled-wallets skill
  • Modular (Passkey) -> use-modular-wallets skill

Strict Rules

  • ALWAYS select the wallet type before starting implementation using the comparison table and decision guide above.
  • ALWAYS use EOA on Ethereum mainnet (SCA gas prohibitive, MSCA not supported) and on Solana, Aptos, NEAR (SCA/MSCA not available).
  • ALWAYS prefer SCA or MSCA on L2 chains (Arbitrum, Base, Polygon, Optimism, etc.) when gas sponsorship or batch operations are needed.
  • NEVER mix wallet types in a single user flow -- pick one and use its corresponding skill.
  • ALWAYS delegate to the specific wallet skill (use-developer-controlled-wallets, use-user-controlled-wallets, or use-modular-wallets) for implementation.

Reference Links

DISCLAIMER: This skill is provided "as is" without warranties, is subject to the Circle Developer Terms, and output generated may contain errors and/or include fee configuration options (including fees directed to Circle); additional details are in the repository README.

数据来源：ClawHub ↗ · 中文优化：龙虾技能库
OpenClaw 技能定制 / 插件定制 / 私有工作流定制

免费技能或插件可能存在安全风险，如需更匹配、更安全的方案，建议联系付费定制

了解定制服务