Back to skill
Skillv1.0.0
ClawScan security
Para Wallet · ClawHub's context-aware review of the artifact, metadata, and declared behavior.
Scanner verdict
SuspiciousFeb 13, 2026, 11:22 PM
- Verdict
- suspicious
- Confidence
- medium
- Model
- gpt-5-mini
- Summary
- The skill's instructions are coherent with a Para REST-based MPC wallet (it only needs an API key), but the published metadata omits the required PARA_API_KEY and the package has no source/homepage — this mismatch and limited provenance warrant caution.
- Guidance
- This skill appears to be a straightforward instruction-only integration for Para's REST MPC wallet, but there are two things to check before installing: (1) confirm the SKILL.md's requirement for PARA_API_KEY matches the registry metadata (the listing currently omits that), and (2) verify the skill's provenance — there's no source or homepage linked. If you proceed, only provide a scoped API key with the minimum permissions, avoid having the agent sign or send sensitive plaintext to the service, test in a sandbox with small amounts, and verify Para's official docs/policies (and ideally the skill author) before trusting it with real funds or secrets.
Review Dimensions
- Purpose & Capability
- noteThe SKILL.md clearly documents creating wallets and signing via Para's REST API and requires a PARA_API_KEY header — this is coherent with the stated purpose. However, the registry metadata in the package listing claims no required env vars/primary credential while the SKILL.md front matter declares openclaw.requires.env: ["PARA_API_KEY"]. That metadata mismatch is unexpected and should be resolved before trusting the skill.
- Instruction Scope
- noteThe runtime instructions only describe HTTP calls to Para endpoints (create wallet, poll status, sign-raw) using the API key. The skill does not instruct reading local files, other env vars, or modifying system configuration. However, the skill does instruct sending arbitrary data to an external service for signing — which is expected for this functionality but means any sensitive data the agent is asked to sign would be transmitted to api.getpara.com.
- Install Mechanism
- okThis is an instruction-only skill with no install spec and no code files, so nothing is written to disk or downloaded during install — minimal install risk.
- Credentials
- noteThe SKILL.md requires a single API key (PARA_API_KEY), which is proportionate for a REST API integration. The concern is the inconsistency: registry-level requirements list no env vars/primary credential while the SKILL.md requires PARA_API_KEY. Also, because the API key authorizes signing operations, it is a high-value secret and should be managed with least privilege and rotation.
- Persistence & Privilege
- okThe skill does not request always:true, does not modify other skills, and has no install-time hooks. It does allow autonomous invocation (platform default), so if installed the agent could call the external API when invoked — combine that with the API key risk noted above.