MetaMask Smart Accounts KIt
Security checks across malware telemetry and agentic risk
Overview
This is a coherent instruction-only MetaMask development reference, but it covers wallet permissions and on-chain transactions that can move assets if users approve them.
Install this skill only if you want help building MetaMask smart-account features. Before using generated code, verify dependencies, use testnets, check every chain ID, contract, recipient, amount, expiry, and delegate address, and never paste real private keys into examples.
VirusTotal
65/65 vendors flagged this skill as clean.
Risk analysis
Artifact-based informational review of SKILL.md, metadata, install specs, static scan signals, and capability signals. ClawScan does not execute the skill or run runtime probes.
If generated code uses the wrong chain, contract, recipient, amount, or calldata, a user could approve an irreversible transaction.
The skill includes examples for submitting user operations and blockchain transactions. This is expected for MetaMask smart-account development, but these actions can change on-chain state or transfer assets.
const userOpHash = await bundlerClient.sendUserOperation({ ... }) ... const txHash = await delegateWalletClient.sendTransaction({ ... })Use testnets first, verify addresses and amounts, preserve wallet confirmation steps, and require explicit user review before signing or sending transactions.
A delegated or session account may be able to execute permitted transactions for the user until the permission expires.
The advanced-permissions workflow intentionally grants delegated authority to a session account. This is disclosed and purpose-aligned, but it is sensitive account authority.
Session account receives permission to execute on user's behalf
Keep expiries short, set strict token and amount limits, verify the delegate/session address, use caveats where available, and avoid putting real private keys into example code or shared chats.
Installing external packages can introduce dependency risk if the package name, registry, or repository is not the intended one.
The skill instructs users to install external development dependencies. The versions are pinned and relevant to the stated purpose, but package provenance still matters.
npm install @metamask/smart-accounts-kit@0.3.0 ... forge install metamask/delegation-framework@v1.3.0
Verify package names, versions, and repository sources against official MetaMask documentation before installing.
