opensea

BENIGN for purpose alignment and install trust, but medium-high operational risk because the skill enables wallet-backed onchain actions, paid calls, and forwarding of wallet credentials to SDK/provider flows. No clear malware or deceptive exfiltration, yet the real-world financial and credential-handling footprint warrants caution.

Purpose and capabilities are aligned with OpenSea marketplace trading, and the referenced repo/docs appear same-org and legitimate. The main concern is not hidden malware but the inherently high risk of granting an AI agent wallet-backed authority to buy, sell, approve, and cross-chain transact NFTs; this makes the skill high security risk despite low evidence of malicious intent.

BENIGN for stated purpose but high-impact. The skill is internally consistent and uses official OpenSea channels, with no clear exfiltration or deceptive install path. Main risk comes from enabling autonomous financial transactions and from credential/signing trust delegated to wallet providers during swap execution.

No direct malicious payload is evident in this YAML fragment (no obfuscation, no obvious exfiltration logic, no shell backdoors). The predominant security concern is supply-chain and CI/CD integrity: the workflow installs and executes a third-party npm CLI at runtime with access to a sensitive token, then publishes the checked-out repository directory to an external registry. This creates a high-impact target—if the CLI, its dependencies, or the repository content/workflow inputs are compromised, unintended or malicious artifacts could be published and the token could potentially be misused. Recommended hardening (not shown here) would include pinning actions by commit SHA, verifying the clawhub CLI provenance/integrity (e.g., lockfiles/signatures), and ensuring only trusted repository contents/tags can trigger publishing.