Skillv1.0.0

ClawScan security

Orderly Trading Orders · ClawHub's context-aware review of the artifact, metadata, and declared behavior.

Scanner verdict

SuspiciousMar 7, 2026, 9:51 PM

Verdict: suspicious
Confidence: medium
Model: gpt-5-mini
Summary: The skill's instructions match a trading-order integration (Orderly Network) but the package metadata omits the sensitive credentials and provenance you would expect, which is a noteworthy mismatch.
Guidance: This skill appears to be a how-to for interacting with Orderly Network and will require you to use an Ed25519 trading key, account ID, and public key to sign orders. Before installing or using it: (1) confirm the skill's source and homepage — no provenance is provided here; (2) do not paste your production private key into an untrusted skill or UI — prefer hardware signing or a dedicated signing service; (3) ask the publisher to declare required env vars/primary credential in metadata so you know what will be requested; (4) test with a separate testnet account or with minimal funds first; (5) verify the API domain and signing format against Orderly Network's official docs; and (6) if you need autonomy, remember an agent with access to your trading key can place/cancel orders — limit scope and rotate keys after testing. If the publisher cannot provide a repository or homepage and clear credential instructions, treat the skill as untrusted.

Review Dimensions

Purpose & Capability: noteThe name/description (order placement, modification, cancellation on Orderly Network) aligns with the provided REST and SDK examples that sign requests with Ed25519 keys and call https://api.orderly.org. However the skill has no source/homepage listed (unknown provenance), which reduces trust in the package despite functional alignment.
Instruction Scope: okSKILL.md is scoped to order management: example code shows request signing, fetching symbol rules, and using a React SDK hook. It does not instruct reading arbitrary local config files or unrelated system secrets. The instructions do, however, assume access to an Ed25519 private key, accountId, and public key — expected for trading but not declared in the registry metadata.
Install Mechanism: okNo install spec and no code files are included (instruction-only). This minimizes surface area because nothing will be written to disk by an installer, but also means you must trust the textual instructions and example code.
Credentials: concernThe SKILL.md explicitly requires an Ed25519 signing key (privateKey), accountId, and publicKeyBase58 to sign orders. Yet the registry metadata declares no required env vars or primary credential. That mismatch is concerning: the skill will require sensitive trading credentials in practice but does not declare or constrain them. A user could inadvertently supply credentials to an unverified source.
Persistence & Privilege: okalways is false and there is no install behavior that alters other skills or system-wide settings. The skill can be invoked by the agent (default) but it does not request persistent system presence.