moneydevkit

Other Community

Repo stars 39
Author repo awesome-omni-skill

Interpretation is structured for decision-making; original keeps the upstream SKILL.md unchanged.

Decide Fit First

Core job: Accept payments on any website using moneydevkit. Use when building a site that sells something, adding a checkout/paywall, or i…
Best fit: Use it when the task has reusable inputs, steps, and validation criteria rather than a one-off answer.
Avoid forcing it: If the source lacks commands, platform support, or external-service evidence, keep those fields unknown instead of guessing.

Design Intent

Structure: The skill is organized around “Workflow”, “1. Get credentials”, “2. Pick a framework and follow its guide”, “3. Create products (optional)”, showing how the author expects the agent to judge fit, collect context, and produce verifiable output.
Trigger evidence: Prioritize the author’s wording around when to use it, what context to collect, and what output shape to produce.
Evidence boundary: Author text states facts, repository files prove commands and paths, and Fluxly only adds fit, limits, and usage judgment.

How To Use It

Inputs: Provide target material, scope, expected result, forbidden changes, and validation method.
Invocation: Name moneydevkit directly; if the source includes slash commands, start with the command and then add task context.
Validation: Start small and check whether the result follows “Workflow / 1. Get credentials / 2. Pick a framework and follow its guide” before expanding.

Boundaries And Review

Dependencies: Prepare Vendor-specific API keys before running a full task.
Permissions: Declared permissions include read / write / env-read; ask the agent to state file, command, and rollback boundaries before acting.
Quality bar: A useful result names the deliverable, evidence, and next action. Generic prose means the task needs tighter context.

moneydevkit

Add payments to any web app in under 5 minutes. Two supported frameworks: Next.js and Replit (Express + Vite).

Workflow

1. Get credentials

Option A — MCP:

There are two MCP servers:

Unauthenticated (/mcp/) — for creating a new account and minting credentials
Authenticated (/mcp/account/) — for managing your account after setup (requires OAuth)

To create a new account:

claude mcp add moneydevkit --transport http https://mcp.moneydevkit.com/mcp/

After you have credentials, switch to the authenticated MCP for full account control:

claude mcp add moneydevkit --transport http https://mcp.moneydevkit.com/mcp/account/

Option B — CLI:

npx @moneydevkit/create

Option C — Dashboard: Sign up at moneydevkit.com and create an app.

All options produce two values:

MDK_ACCESS_TOKEN — API key
MDK_MNEMONIC — wallet seed phrase

Add both to .env (or Replit Secrets, Vercel env vars, etc.). Both are required.

2. Pick a framework and follow its guide

Next.js → read references/nextjs.md
Replit (Express + Vite) → read references/replit.md

3. Create products (optional)

For fixed catalog items, create products via the dashboard or MCP:

mcporter call moneydevkit.create-product name="T-Shirt" priceAmount=2500 currency=USD

Then use type: 'PRODUCTS' checkouts with the product ID.

For dynamic amounts (tips, donations, invoices), skip products and use type: 'AMOUNT' directly.

4. Deploy

Deploy to Vercel (Next.js) or Replit. Ensure MDK_ACCESS_TOKEN and MDK_MNEMONIC are set in the production environment.

⚠️ Use printf not echo when piping env vars — trailing newlines cause silent auth failures.

Checkout types

Type	Use case	Required fields
`AMOUNT`	Dynamic amounts, tips, invoices	`amount`, `currency`
`PRODUCTS`	Sell dashboard products	`product` (product ID)

Pricing options

Fixed price — set specific amount (USD cents or whole sats)
Pay what you want — customer chooses amount (set amountType: 'CUSTOM' on product)

Currency

USD — amounts in cents (e.g. 500 = $5.00)
SAT — amounts in whole satoshis

Customers

Collect customer info to track purchases and enable refunds:

await createCheckout({
  // ...checkout fields
  customer: { email: 'jane@example.com', name: 'Jane', externalId: 'user-123' },
  requireCustomerData: ['email', 'name'] // show form for missing fields
})

MCP tools

If the moneydevkit MCP server is connected (authenticated), these tools are available:

create-app / list-apps / update-app / rotate-api-key — manage apps
create-product / list-products / get-product / update-product / delete-product
create-customer / list-customers / get-customer / update-customer / delete-customer
list-checkouts / get-checkout — view checkout sessions
list-orders / get-order — view completed payments
search-docs — search moneydevkit documentation

Docs

Full documentation: docs.moneydevkit.com

Fluxly profile Author and license come from source; runtime, permissions, and network are Fluxly detections or estimates

Fluxly category: Other
Author-declared agents: No explicit declaration found; this is not inferred or tested compatibility
Static check: 88 / 100 · heuristic scan, not runtime safety proof
Author / version / license: @diegosouzapw · no license declared
Fluxly token estimate: Lean
Fluxly setup estimate: Guided setup
External API key: Required · Vendor-specific
Detected OS requirements: macOS · Linux · Windows
Runtime requirements: Unspecified
Detected file/system behavior: Read-only
Write / modify
Env read
Detected network behavior: External requests
Install commands: None (reference only)

Profile is derived at build time from SKILL.md and install vectors. Subject to drift from author intent.

Heads up: 未限定 allowed-tools，默认拥有全部工具权限。

Output preview moneydevkit.preview

The current SKILL.md does not define a fixed output example.

SKILL.md SKILL.md

# moneydevkit

Add payments to any web app in under 5 minutes. Two supported frameworks: Next.js and Replit (Express + Vite).

## Workflow

### 1. Get credentials

**Option A — MCP:**

There are two MCP servers:
- **Unauthenticated** (`/mcp/`) — for creating a new account and minting credentials
- **Authenticated** (`/mcp/account/`) — for managing your account after setup (requires OAuth)

To create a new account:
```
claude mcp add moneydevkit --transport http https://mcp.moneydevkit.com/mcp/
```

After you have credentials, switch to the authenticated MCP for full account control:
```
claude mcp add moneydevkit --transport http https://mcp.moneydevkit.com/mcp/account/
```

**Option B — CLI:**
```bash
npx @moneydevkit/create
```

**Option C — Dashboard:**
Sign up at [moneydevkit.com](https://moneydevkit.com) and create an app.

All options produce two values:
- `MDK_ACCESS_TOKEN` — API key
- `MDK_MNEMONIC` — wallet seed phrase

Add both to `.env` (or Replit Secrets, Vercel env vars, etc.). Both are required.

### 2. Pick a framework and follow its guide

- **Next.js** → read [references/nextjs.md](references/nextjs.md)
- **Replit (Express + Vite)** → read [references/replit.md](references/replit.md)

### 3. Create products (optional)

For fixed catalog items, create products via the dashboard or MCP:
```
mcporter call moneydevkit.create-product name="T-Shirt" priceAmount=2500 currency=USD
```
Then use `type: 'PRODUCTS'` checkouts with the product ID.

For dynamic amounts (tips, donations, invoices), skip products and use `type: 'AMOUNT'` directly.

### 4. Deploy

Deploy to Vercel (Next.js) or Replit. Ensure `MDK_ACCESS_TOKEN` and `MDK_MNEMONIC` are set in the production environment.

…

Evidence boundary and execution chain

Author text anchors workflow facts; Fluxly only indexes current sections, terms, files, and commands.

sections -> Workflow → 1. Get credentials → 2. Pick a framework and follow its guide → 3. Create products (optional) → 4. Deploy → Checkout types
terms    -> Option A — MCP · Unauthenticated · Authenticated · Option B — CLI · Option C — Dashboard · Next.js · Replit (Express + Vite) · Fixed price
files/cmd -> /mcp/ · /mcp/account/ · MDKACCESSTOKEN · MDKMNEMONIC · .env · type: 'PRODUCTS' · type: 'AMOUNT' · printf
body sha256 -> 3e9843c4b16c

Decide Fit First

Design Intent

How To Use It

Boundaries And Review

moneydevkit

Workflow

1. Get credentials

2. Pick a framework and follow its guide

3. Create products (optional)

4. Deploy

Checkout types

Pricing options

Currency

Customers

MCP tools

Docs

Discussion