Use Circle Wallets
PassAudited by ClawScan on May 1, 2026.
Overview
This is a documentation-only Circle wallet decision guide with no code or credentials, but users should review downstream wallet skills and custody choices before implementation.
This skill appears safe as an instruction-only decision aid. Before using it for real wallet integration, review the specific wallet skill it delegates to, confirm Circle’s current documentation, and decide carefully who should control keys and approve transactions.
Findings (2)
Artifact-based informational review of SKILL.md, metadata, install specs, static scan signals, and capability signals. ClawScan does not execute the skill or run runtime probes.
If implemented, a developer-controlled wallet setup could allow backend systems or agents to move assets without each user approving the action.
The skill explicitly includes a wallet model where the developer/backend controls keys without end-user approval. This is central to the stated purpose, but it is a high-impact custody and authorization decision.
Developer controls (no user approval) -> Developer-controlled wallets
Use developer-controlled wallets only when that custody model is intentional; protect entity secrets, apply transaction limits and audit logs, and prefer user-controlled approval flows when users should retain direct control.
Installing this skill may lead the agent to rely on additional wallet-specific skills for implementation work.
The instruction-only skill routes implementation to other named skills that are not part of this artifact set. The routing is disclosed and purpose-aligned, but the downstream skills determine the actual implementation behavior.
ALWAYS delegate to the specific wallet skill (`use-developer-controlled-wallets`, `use-user-controlled-wallets`, or `use-modular-wallets`) for implementation.
Review and trust the downstream wallet-specific skills before letting an agent use them for code generation, credential handling, or transaction-related workflows.