> For the complete documentation index, see [llms.txt](https://docs.megaeth.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.megaeth.com/moss-docs/wallet/agent-skills.md).

# Agent Skills Pack

Eight focused [Agent Skills](https://docs.claude.com/en/docs/agents-and-tools/agent-skills/overview) 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](https://github.com/megaeth-labs/moss-skills) marketplace repo (see [Install](#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](/moss-docs/wallet/quickstart.md) · [Methods](/moss-docs/methods/methods.md)                                    |
| `moss-wallet-permissions`     | Implementing Smart Approvals — grants, `silent` execution, and AI-agent / automation / checkout flows.                      | [Smart Approvals](/moss-docs/core-sdk/permissions.md) · [AI Agent Guide](/moss-docs/wallet/ai-agent-guide.md)               |
| `moss-wallet-react`           | Wiring `MegaProvider` + hooks in a React 19 app, or using the wagmi connector.                                              | [React SDK](/moss-docs/react-sdk/overview.md)                                                                               |
| `moss-wallet-server-verify`   | Verifying wallet ownership on the backend (SIWE or JWT).                                                                    | [Server Verify](/moss-docs/wallet/server-verify.md) · [Authentication](/moss-docs/wallet/authentication.md)                 |
| `moss-wallet-paymaster`       | Configuring gas sponsorship and the partner paymaster endpoint.                                                             | [Paymaster Guide](/moss-docs/wallet/paymaster-setup.md)                                                                     |
| `moss-wallet-cli`             | Automating MOSS from a terminal or CI with the `mega` CLI.                                                                  | [MOSS CLI](/moss-docs/wallet/cli.md)                                                                                        |
| `moss-wallet-privy-migration` | Moving a user's assets from a Privy embedded wallet into MOSS.                                                              | [Migrating from Privy](/moss-docs/wallet/privy-migration.md)                                                                |
| `moss-wallet-security-review` | Auditing an existing integration before launch.                                                                             | [Best Practices](/moss-docs/wallet/best-practices.md) · [Integration Checklist](/moss-docs/wallet/integration-checklist.md) |

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**](https://github.com/megaeth-labs/moss-skills) marketplace repo.

### Claude Code

```bash
/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):

```bash
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:

```bash
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.

{% hint style="info" %}
This pack improves consistency and security posture — it does not replace a full security assessment for your specific product and threat model.
{% endhint %}

## Related

* [Best Practices](/moss-docs/wallet/best-practices.md) — apply the same principles directly in your integration design.
* [Integration Checklist](/moss-docs/wallet/integration-checklist.md) — production rollout checklist for partner launch.
* [AI Agent Guide](/moss-docs/wallet/ai-agent-guide.md) — policy-first patterns and example agent workflows.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.megaeth.com/moss-docs/wallet/agent-skills.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.