<2-3 sentences summarising what the project addresses and solves, the target audience, and the benefit.> MetaMask/core is a monorepo consolidating essential packages for MetaMask clients, including the browser extension and mobile app. It provides a shared foundation for wallet functionalities, enabling developers to build and maintain consistent features across different MetaMask products. The repository targets developers and contributors aiming to integrate with or extend MetaMask's core capabilities.

How It Works

The project employs a monorepo architecture, housing a comprehensive suite of modular controllers (e.g., @metamask/accounts-controller, @metamask/network-controller, @metamask/permission-controller). Each controller encapsulates specific wallet logic, promoting code reusability and maintainability. This modular design allows for efficient development and consistent behavior across various MetaMask clients. A notable feature is the integrated agent skills CLI, which simplifies the setup of AI agent integrations for platforms like Claude, Cursor, and OpenAI.

Quick Start & Requirements

• Primary install / run command: yarn skills (installs default stable Core skills). Interactive selection via yarn skills --select.
• Non-default prerequisites and dependencies: Node.js and Yarn are required for development and running scripts. Specific dependencies for individual controllers are detailed within their respective package READMEs.
• Links: Installation and usage instructions are per-package; refer to packages/ for individual READMEs.

Highlighted Details

• Features over 70 distinct controller packages managing diverse wallet aspects, from accounts and assets to network connectivity and permissions.
• Includes a command-line interface (@metamask/skills CLI) for seamless integration with AI agents, supporting platforms like Claude, Cursor, and OpenAI.
• Monorepo structure facilitates code sharing and consistency across MetaMask's ecosystem (extension, mobile).

Maintenance & Community

No specific details regarding maintainers, community channels (e.g., Discord, Slack), or roadmap are provided in the README.

Licensing & Compatibility

The README does not specify a license type. This absence of licensing information presents a significant barrier to assessing commercial use or integration compatibility.

Limitations & Caveats

Detailed installation and usage instructions are fragmented across individual package READMEs, requiring users to navigate the packages/ directory. The lack of a centralized license declaration is a critical omission for adoption decisions.