How do I install the Mayar V2 skill?

Run npx skillmds@latest add mayarid/mayar-v2 in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Mayar V2 safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Mayar V2?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Mayar V2 free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Mayar V2?

mayarid (@mayarid) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Mayar V2 by mayarid — Agent Skill

Name: Mayar V2
Author: mayarid

Mayar V2

Use this skill when the user wants to integrate Mayar payments or billing into an application—hosted, embedded, or native checkout, payment links, invoices, memberships, subscriptions, credit wallets, licenses, QRIS, or webhooks—or operate their Mayar account from the terminal, including balance, products, customers, transactions, invoices, and webhook administration—or ask what Mayar is, what it does, which payment methods it accepts, or how its features, account setup, and business verification work.

mayarid 035de99 17 files · 49.6 KB Updated Sep 17, 2026

File contents

Mayar

Select one branch from the user request:

BUILD — Add a Mayar integration to an application. This branch includes the UI, server, persistent data, and fulfillment.
OPS — Manage or test a Mayar account from the terminal.
LEARN — Answer a question about Mayar itself. This branch reads documentation and changes nothing.

A live call is an agent command against the Mayar account. Use npx -y mayar@latest for every live call. Application code uses the HTTP API. Read references/cli-commands.md for CLI syntax. If a BUILD documentation fetch or HTTP probe fails, take that CLI path and continue the phase.

LEARN

Read references/product-knowledge.md. Follow only that file. Do not load the BUILD playbook. Do not run CLI commands. Do not change any file.

OPS

Read references/cli-commands.md. Follow the OPS procedure in that file. Do not load the BUILD playbook.

BUILD: strict phase gates

Complete one phase at a time. Do not read the next phase file until you meet the completion criteria for the current phase. Load references/cli-commands.md before a live call.

Phase 1 — Discover

Read playbook/discover.md. Stay in this phase until RECON is complete and all user decisions are recorded.

Phase 2 — Plan

After Discover is complete, read playbook/plan.md. Stay in this phase until you record the schema or a CLI path. The user must also approve the plan and the exact fulfillment operation.

Phase 3 — Implement

After explicit approval, read playbook/implement.md. Stay in this phase until all planned changes are complete and all project checks pass.

Phase 4 — Verify

After Implement is complete, read playbook/verify.md. Complete the sandbox evidence, regression checks, and handoff before you close the task.

---name: mayar-v2description: Use this skill when the user wants to integrate Mayar payments or billing into an application—hosted, embedded, or native checkout, payment links, invoices, memberships, subscriptions, credit wallets, licenses, QRIS, or webhooks—or operate their Mayar account from the terminal, including balance, products, customers, transactions, invoices, and webhook administration—or ask what Mayar is, what it does, which payment methods it accepts, or how its features, account setup, and business verification work.---# MayarSelect one branch from the user request:- **BUILD** — Add a Mayar integration to an application. This branch includes the UI, server, persistent data, and fulfillment.- **OPS** — Manage or test a Mayar account from the terminal.- **LEARN** — Answer a question about Mayar itself. This branch reads documentation and changes nothing.A **live call** is an agent command against the Mayar account. Use`npx -y mayar@latest` for every live call. Application code uses the HTTP API.Read [references/cli-commands.md](references/cli-commands.md) for CLI syntax.If a BUILD documentation fetch or HTTP probe fails, take that CLI path andcontinue the phase.## LEARNRead [references/product-knowledge.md](references/product-knowledge.md). Followonly that file. Do not load the BUILD playbook. Do not run CLI commands. Do notchange any file.## OPSRead [references/cli-commands.md](references/cli-commands.md). Follow the OPSprocedure in that file. Do not load the BUILD playbook.## BUILD: strict phase gatesComplete one phase at a time. Do not read the next phase file until you meet thecompletion criteria for the current phase. Load[references/cli-commands.md](references/cli-commands.md) before a live call.### Phase 1 — DiscoverRead [playbook/discover.md](playbook/discover.md). Stay in this phase untilRECON is complete and all user decisions are recorded.### Phase 2 — PlanAfter Discover is complete, read [playbook/plan.md](playbook/plan.md). Stay inthis phase until you record the schema or a CLI path. The user must alsoapprove the plan and the exact fulfillment operation.### Phase 3 — ImplementAfter explicit approval, read [playbook/implement.md](playbook/implement.md).Stay in this phase until all planned changes are complete and all project checkspass.### Phase 4 — VerifyAfter Implement is complete, read [playbook/verify.md](playbook/verify.md).Complete the sandbox evidence, regression checks, and handoff before you closethe task.

Frequently asked questions