MetaMask/skills

COLLECTIONcommunity
v0.1.0MetaMaskMITUpdated 3mo agonpmGitHub

A collection of skills for OpenClaw agents, with implementations and integrations across the MetaMask ecosystem.

Agent skills, rules, and domain knowledge for the MetaMask ecosystem. Two audiences share this repo: 1. dApp / Web3 developers — skills under teach AI agents how to use MetaMask developer libraries (, , OpenCode plugin, etc.). Drop them into your editor/agent and it will operate the tooling correctly. 2. MetaMask product engineers — skills under , , , , etc. carry the conventions and review…

This collection bundles
37 skills

⚠ The trust score below reflects the installer package @metamask/skills only. The bundled units are not individually verified or scanned — review them before use.

Automatically indexed from public sources. Not yet verified by the developer on Forge.Claim this listing →
35kDownloads/wk
16GitHub stars
7Forks
3mo agoLast update
Package
AuthorMetaMask
LicenseMIT
Version0.1.0
Sourcegithub
Trust Status
B
60/100Good
✓Listed in Forge index+10/10
—Publisher identity verified+0/20
→ Publisher: run `forge publish` from the package repo to claim ownership
—Ed25519 publish signature+0/5
→ Included automatically when the publisher runs `forge publish`
—Domain verification+0/5
→ Publisher: host /.well-known/forge.json on the package homepage with { "publisher": "<github-login>" }
—npm Trusted Publishing (Sigstore)+0/5
→ Publish from GitHub Actions with --provenance so the attestation binds this package to this repo
—npm maintainer match+0/5
→ Earned once your identity is verified above and that login is an npm maintainer of this package
✓CVE scan · clean+30/30
✓Static analysis · clean+20/20
Paste into Claude Code, Cursor, or any AI assistant to fix all gaps
StatusCommunity-indexed
PublisherUnverified
SignatureUnsigned
Domain—
Provenance—
Dependencies✓ 0 resolved · none vulnerable
Tool surface—
Security scan✓ Cleanv0.1.0 · 3mo agoHow well does this scan work?
EvalsNone
IndexedJun 14, 2026

Verification confirms publisher identity (repo ownership), not code safety. The security scan covers known CVEs and suspicious install scripts.

Tools

No tool declarations found in the source3mo ago

Forge read 1 source file from the published package tarball and matched no MCP tool registrations. Extraction is pattern-based over shipped source: a server that builds its tool list at runtime, or that ships only bundled or minified code, registers nothing this can see. Treat it as “not detected”, not as “exposes none”.

About

Agent skills, rules, and domain knowledge for the MetaMask ecosystem. Two audiences share this repo: 1. dApp / Web3 developers — skills under teach AI agents how to use MetaMask developer libraries (, , OpenCode plugin, etc.). Drop them into your editor/agent and it will operate the tooling correctly. 2. MetaMask product engineers — skills under , , , , etc. carry the conventions and review heuristics for , , and . These install into consumer repos via a small CLI. Single source of truth,…

Keywords
collection
Alternatives
Comparing tool surfaces…

No dependency coverage

This package was last scanned before Forge began storing the resolved tree. The next scan will record it.