Skillv1.0.5

ClawScan security

Whistle RPC · ClawHub's context-aware review of the artifact, metadata, and declared behavior.

BenignFeb 13, 2026, 4:30 PM

Verdict: benign
Confidence: high
Model: gpt-5-mini
Summary: The skill's requests and runtime instructions are coherent with a paid Solana RPC service: it documents API endpoints, a subscription flow that requires an on‑chain payment, and explicitly instructs the agent to get user approval before signing — there are no unexplained credentials, installs, or file accesses.
Guidance: This skill appears internally consistent with a paid Solana RPC provider, but take these precautions before installing or approving actions: (1) Verify the domain (https://whistle.ninja) and the referenced GitHub repo yourself; (2) Never provide your wallet private key to the agent—sign transactions locally or with your wallet UI; (3) When the agent asks to pay, confirm the exact SOL amount and recipient address out‑of‑band (copy/paste errors and phishing addresses are common); (4) Use a dedicated low‑value wallet for subscription payments as the SKILL.md recommends; (5) Treat any automatic signing/autonomous agent behavior as risky—do not allow the agent to sign without an explicit human confirmation step; (6) If you need stronger assurance, test with a tiny payment on devnet or a disposable wallet first.

Purpose & Capability: okThe name/description (Solana RPC service) match the SKILL.md and tools.json: listed RPC, WebSocket, DEX, and historical endpoints and subscription flow. No unrelated binaries, env vars, or config paths are requested.
Instruction Scope: noteThe SKILL.md instructs the agent to perform three HTTP calls and to request a quote, then perform an on‑chain SOL transfer and activate the subscription. It explicitly requires the agent to ask the human operator for explicit approval before signing any transaction and to use a dedicated low‑value wallet. This is appropriate for the stated purpose, but any user must strictly confirm payments and recipient addresses before approving a transaction.
Install Mechanism: okInstruction-only skill with no install spec and no code files. No packages or archives are downloaded or written to disk, so installation risk is minimal.
Credentials: okThe skill declares no required environment variables or credentials. The described flow uses an API key issued after payment; the SKILL.md does not request private keys or other unrelated secrets. This is proportionate to a paid RPC service.
Persistence & Privilege: okalways is false and the skill does not request persistent system modifications or cross-skill configuration. It can be invoked by the agent (default), which is expected for a network service integration.