SkillsAdd

mayarid/skills · Archived

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 verificati…

First seen Aug 5, 2026

Installation

$ npx skills add mayarid/skills --skill mayar-v2
View on skills.sh ↗ GitHub repository ↗

Stronger alternatives

This repository is archived — consider an actively maintained alternative.

mayar Same author
mayarid/mayar-cli

Mayar API & CLI integration skill. - APP INTEGRATION: Use `mayar docs <topic>` to read REST API…

8 installs
More details

Agent compatibility

Declared targets from SKILL.md / docs. Unmarked agents are not listed — the skill may still install via the CLI.

Claude Code Not declared
Cursor Not declared
Codex Not declared
GitHub Copilot Not declared
Windsurf Not declared
Gemini CLI Not declared
Cline Not declared
OpenCode Not declared

Repository health

Stars 13
License LICENSE
Default branch main
Open issues 0
Status Archived

Skill metadata

Parsed from SKILL.md frontmatter.

Version2.3.0
CompatibilityRequires network access to Mayar documentation and API. CLI commands require Node.js 18+ and npx.
More metadata
version
2.3.0

Package contents

Files included with this skill beyond the listing page.

  • skill md SKILL.md 2,723 B
  • docs SUMMARY.md 529 B

History

  1. First seen on skills.sh
  2. First recorded snapshot · 68 installs

SKILL.md

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](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](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](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](references/cli-commands.md) before a live call.

Phase 1 — Discover

Read [playbook/discover.md](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](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](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](playbook/verify.md). Complete the sandbox evidence, regression checks, and handoff before you close the task.