Agent Skills Pack

Install-ready Agent Skills that teach coding agents to build MOSS Wallet integrations correctly — core SDK, permissions, React, server verify, paymaster, CLI, Privy migration, and security review.

Eight focused Agent Skills that teach coding agents (Claude Code, Codex, Cursor, Gemini) how to build on MOSS correctly. Each skill is a self-contained SKILL.md module the agent loads on demand for a specific job — keeping it accurate on exact method names, safe defaults, the permission model, and the integration patterns that quietly break things when missed.

The skills are real files, authored alongside these docs and published in the public megaeth-labs/moss-skills marketplace repo (see Install). Hand this pack to any external team implementing or reviewing a MOSS Wallet integration.

The eight skills

Skill	Use it when you are…	Maps to
moss-wallet-sdk	Building core integrations — connect, transfer, contract calls, signing, balances. The entry point that routes to the rest.	Quickstart · Methods
moss-wallet-permissions	Implementing Smart Approvals — grants, silent execution, and AI-agent / automation / checkout flows.	Smart Approvals · AI Agent Guide
moss-wallet-react	Wiring MegaProvider + hooks in a React 19 app, or using the wagmi connector.	React SDK
moss-wallet-server-verify	Verifying wallet ownership on the backend (SIWE or JWT).	Server Verify · Authentication
moss-wallet-paymaster	Configuring gas sponsorship and the partner paymaster endpoint.	Paymaster Guide
moss-wallet-cli	Automating MOSS from a terminal or CI with the mega CLI.	MOSS CLI
moss-wallet-privy-migration	Moving a user's assets from a Privy embedded wallet into MOSS.	Migrating from Privy
moss-wallet-security-review	Auditing an existing integration before launch.	Best Practices · Integration Checklist

Each skill bundles the relevant docs as on-demand references plus small deterministic helper scripts (a permission-policy builder, a secure-context checker, server-verify and paymaster snippets, CLI flag formatters, and a Privy migration planner), so the agent loads exactly what a task needs and nothing more.

Install

The pack is published in the public megaeth-labs/moss-skills marketplace repo.

Claude Code

/plugin marketplace add https://github.com/megaeth-labs/moss-skills.git
/plugin install moss-wallet@moss-skills
/reload-plugins

Use the full https://… URL — the owner/repo shorthand resolves to an SSH URL and fails without GitHub SSH keys configured.

The agent loads the right skill automatically when a task is relevant — e.g. moss-wallet-server-verify when you build backend login. Run /plugin → Installed to see all eight.

Cursor · Codex · Gemini · Copilot

Copy the skills into your project (or ~/.claude/skills for all projects):

git clone https://github.com/megaeth-labs/moss-skills
cp -r moss-skills/moss-wallet/skills/* .claude/skills/

Or download dist/moss-wallet-skills.zip from the repo and unzip -d .claude/skills.

claude.ai

Upload an individual skill archive from the repo's dist/ folder (e.g. moss-wallet-sdk.zip) under Settings → Capabilities → Skills.

mega CLI

The CLI installer is public and ships a bundled skill that updates itself:

curl -fsSL https://account.megaeth.com/install | sh
mega moss update

Why hand this to partners

Three integration failure modes show up repeatedly without this pack:

1. Invented SDK behavior — wrong method names, hallucinated config fields, or made-up response shapes that "look right." The skills pin agents to the real surface (e.g. methods return approved / cancelled / error instead of throwing).
2. Over-broad permissions — wildcard or long-lived grants that are hard to reason about in production, with no revocation plan. The skills encode least-privilege { to, signature } scoping, short expiry windows, and a revoke path.
3. Security gaps found at launch — frontend-owned trust decisions, missing backend verification, and sponsorship endpoints without allowlists, budgets, or rate limits. The skills encode the server-side trust boundary by default.

Each skill captures the production-safe defaults so the agent doesn't have to re-derive them from prompts.

Partner workflow

1. Build with moss-wallet-sdk (and moss-wallet-react for React apps) — first-pass implementation.
2. Add capabilities as needed — moss-wallet-permissions, moss-wallet-server-verify, moss-wallet-paymaster, moss-wallet-cli, or moss-wallet-privy-migration.
3. Security review with moss-wallet-security-review before production.

This pack improves consistency and security posture — it does not replace a full security assessment for your specific product and threat model.

Related

• Best Practices — apply the same principles directly in your integration design.
• Integration Checklist — production rollout checklist for partner launch.
• AI Agent Guide — policy-first patterns and example agent workflows.