Back to skill
Skillv1.0.1

ClawScan security

Setup Stylus Contracts · ClawHub's context-aware review of the artifact, metadata, and declared behavior.

Scanner verdict

BenignMar 19, 2026, 2:16 PM
Verdict
Benign
Confidence
high
Model
gpt-5-mini
Summary
The skill's instructions, requirements, and actions align with its stated purpose of setting up Stylus smart-contract projects; nothing requested is disproportionate or unrelated, though it performs network installs and requires handling of private keys (which is expected for this task).
Guidance
This skill appears coherent for setting up and deploying Stylus contracts, but take these precautions before running it: (1) Inspect any network installer before piping to sh—review https://sh.rustup.rs yourself or install rustup through a package manager you trust. (2) Verify the OpenZeppelin crate version on crates.io and confirm the referenced GitHub repo if you need upstream guidance. (3) Never pass raw private keys on the command line; keep key files with restrictive permissions (chmod 600) or use a hardware wallet/keystore. (4) Be aware the skill's license is AGPL-3.0-only—review license implications for your project. (5) Prefer running these commands manually in a controlled environment rather than granting an automated agent full autonomy to execute them.

Review Dimensions

Purpose & Capability
okName/description, declared lack of required env/binaries, and SKILL.md are consistent: all steps (install Rust toolchain, add wasm target, install cargo-stylus, create project, add OpenZeppelin crate, build/export ABI, deploy with RPC and private key) are appropriate for a Stylus/OpenZeppelin setup.
Instruction Scope
okInstructions are focused on the stated setup workflow. They do instruct running installers and build/deploy commands and reference an RPC URL and private-key path (required for deployment), but they do not instruct reading unrelated files or exfiltrating data.
Install Mechanism
noteThis is an instruction-only skill (no install spec). It recommends running the standard rustup installer via curl | sh (https://sh.rustup.rs) and cargo install from crates.io — both are common for Rust setups, but downloading & executing a script from the network is a privileged operation and should be done after the user inspects/trusts the source.
Credentials
okThe skill requests no environment variables or credentials itself. The workflow legitimately requires an RPC endpoint and a private-key file for deployment; guidance warns against passing raw keys on the command line and recommends secure file permissions or hardware keystores.
Persistence & Privilege
okalways is false and the skill is user-invocable; it does not request persistent or cross-skill privileges. Autonomous invocation is allowed by platform default but combined with this skill's focused scope does not introduce additional incoherence.