moneyclaw-skill

Name: moneyclaw-skill
Author: Matchameleon

135stars1.0kforks

How to install moneyclaw-skill?

matchameleon/moneyclaw/moneyclaw-skill

$npx -y skills add Matchameleon/moneyclaw --skill moneyclaw-skill

Installs into the current project.

Summary

Inspect a MoneyClaw wallet, create bounded payment tasks, and continue user-confirmed payment steps using a prepaid account. Use only when the user clearly asks to use MoneyClaw for their own payments.

Files · 1

View on GitHub

SKILL.md

1	# MoneyClaw
2
3	MoneyClaw helps OpenClaw agents inspect prepaid payment state, create auditable payment tasks, and continue explicitly requested payment steps.
4
5	Primary use case: buyer-side payments for OpenClaw agents.
6
7	## Authentication
8
9	This skill requires one MoneyClaw API key.
10
11	```bash
12	Authorization: Bearer $MONEYCLAW_API_KEY
13	```
14
15	Base URL: `https://moneyclaw.ai/api`
16
17	## Trust Model
18
19	MoneyClaw is designed for real, user-authorized agent payments.
20
21	- use prepaid balances to keep risk bounded
22	- use payment intents as the main auditable execution surface
23	- keep account inbox state inspectable for receipts and account messages
24	- let the user approve the payment step before money moves
25
26	## Approval Model
27
28	Default to dashboard approval unless the account has explicitly enabled agent auto-approval.
29
30	- MoneyClaw accounts expose an account-level `agentAutoApproveEnabled` flag through `GET /api/me`.
31	- When that flag is off, API-key-created payment tasks wait for dashboard approval before spending.
32	- When that flag is on, API-key-created payment tasks can be auto-approved within the merchant and amount scope of the task.
33	- Do not assume agent auto-approval is enabled unless the account state confirms it.
34
35	## Safety Boundaries
36
37	- Only use MoneyClaw for purchases or payment flows explicitly requested by the user. If the account is not clearly configured for agent auto-approval and the user has not explicitly asked for the next payment step, stop and ask.
38	- Only use wallet, card, and billing data returned by the user's own MoneyClaw account.
39	- Respect merchant, issuer, card-network, and verification controls.
40	- Treat fraud checks, KYC, sanctions, geography rules, merchant restrictions, issuer declines, and other payment controls as hard boundaries.
41	- Never fabricate billing identity, cardholder data, addresses, names, phone numbers, or verification information.
42	- If a transaction fails, looks suspicious, or produces conflicting signals, stop and inspect transaction state before retrying.
43	- Prefer prepaid, bounded-risk flows by default.
44	- Never invoke this skill automatically from a shopping, billing, or checkout page. Use it only after an explicit user request to use MoneyClaw.
45
46	## Before Any High-Risk Step
47
48	Before any action that can spend funds, retrieve execution details, or submit a payment step:
49
50	1. Confirm the exact merchant domain.
51	2. Confirm the amount and currency.
52	3. Confirm the user explicitly asked for this exact action, or that the account is clearly configured for agent auto-approval for this scope.
53	4. Stop if that confirmation is missing or ambiguous.
54
55	## Default Buyer Flow
56
57	Use the product in this order:
58
59	1. `GET /api/me` for wallet readiness, deposit address, and inbox context. Fresh accounts may also finish mailbox, deposit-address, and provider setup on this first authenticated read.
60	2. `POST /api/payment-intents` for the exact purchase.
61	3. If `agentAutoApproveEnabled` is off, wait for dashboard approval. If it is on, the API-key task can move directly toward `approved` and `card_ready`. Approved tasks can auto-prepare or reuse the account's hidden execution card when wallet funding is available.
62	On the first hidden-card bootstrap for an account, MoneyClaw may reserve the provider minimum initial deposit onto that shared hidden card even if the current task amount is smaller. Any residual stays on the same hidden card for later tasks.
63	4. Use `GET /api/payment-intents/:intentId/credentials` only when the task is `card_ready` and the user explicitly asked to continue the current payment step.
64	5. After a successful one-time checkout, use `POST /api/payment-intents/:intentId/reconcile` to write the settled charge back into MoneyClaw accounting.
65	6. Inspect payment-task state and wallet transactions before retrying.
66
67	## Load References When Needed
68
69	- Read `references/payment-safety.md` before entering payment details on an unfamiliar merchant, when a checkout keeps failing, or when retry boundaries matter.
70
71	## Core Jobs
72
73	### 1. Check account readiness
74
75	```bash
76	curl -H "Authorization: Bearer $MONEYCLAW_API_KEY" \
77	https://moneyclaw.ai/api/me
78	```
79
80	Important fields:
81
82	- `balance`: wallet balance
83	- `depositAddress`: where to send USDT
84	- `mailboxAddress`: inbox address for receipts and account messages
85	- `agentAutoApproveEnabled`: whether API-key-created payment tasks can auto-approve without a dashboard click
86
87	When the user asks for readiness, report wallet balance, deposit address, inbox state, and whether a payment task can proceed.
88
89	### 2. Create an auditable payment task
90
91	```bash
92	curl -X POST -H "Authorization: Bearer

People who liked this also viewed

6 picks

Type

moneyclaw-skill

135stars1.0kforks

View on GitHub

How to install moneyclaw-skill?

matchameleon/moneyclaw/moneyclaw-skill

$npx -y skills add Matchameleon/moneyclaw --skill moneyclaw-skill

Installs into the current project.

Summary

Files · 1

View on GitHub

SKILL.md

1	# MoneyClaw
2
3	MoneyClaw helps OpenClaw agents inspect prepaid payment state, create auditable payment tasks, and continue explicitly requested payment steps.
4
5	Primary use case: buyer-side payments for OpenClaw agents.
6
7	## Authentication
8
9	This skill requires one MoneyClaw API key.
10
11	```bash
12	Authorization: Bearer $MONEYCLAW_API_KEY
13	```
14
15	Base URL: `https://moneyclaw.ai/api`
16
17	## Trust Model
18
19	MoneyClaw is designed for real, user-authorized agent payments.
20
21	- use prepaid balances to keep risk bounded
22	- use payment intents as the main auditable execution surface
23	- keep account inbox state inspectable for receipts and account messages
24	- let the user approve the payment step before money moves
25
26	## Approval Model
27
28	Default to dashboard approval unless the account has explicitly enabled agent auto-approval.
29
30	- MoneyClaw accounts expose an account-level `agentAutoApproveEnabled` flag through `GET /api/me`.
31	- When that flag is off, API-key-created payment tasks wait for dashboard approval before spending.
32	- When that flag is on, API-key-created payment tasks can be auto-approved within the merchant and amount scope of the task.
33	- Do not assume agent auto-approval is enabled unless the account state confirms it.
34
35	## Safety Boundaries
36
37	- Only use MoneyClaw for purchases or payment flows explicitly requested by the user. If the account is not clearly configured for agent auto-approval and the user has not explicitly asked for the next payment step, stop and ask.
38	- Only use wallet, card, and billing data returned by the user's own MoneyClaw account.
39	- Respect merchant, issuer, card-network, and verification controls.
40	- Treat fraud checks, KYC, sanctions, geography rules, merchant restrictions, issuer declines, and other payment controls as hard boundaries.
41	- Never fabricate billing identity, cardholder data, addresses, names, phone numbers, or verification information.
42	- If a transaction fails, looks suspicious, or produces conflicting signals, stop and inspect transaction state before retrying.
43	- Prefer prepaid, bounded-risk flows by default.
44	- Never invoke this skill automatically from a shopping, billing, or checkout page. Use it only after an explicit user request to use MoneyClaw.
45
46	## Before Any High-Risk Step
47
48	Before any action that can spend funds, retrieve execution details, or submit a payment step:
49
50	1. Confirm the exact merchant domain.
51	2. Confirm the amount and currency.
52	3. Confirm the user explicitly asked for this exact action, or that the account is clearly configured for agent auto-approval for this scope.
53	4. Stop if that confirmation is missing or ambiguous.
54
55	## Default Buyer Flow
56
57	Use the product in this order:
58
59	1. `GET /api/me` for wallet readiness, deposit address, and inbox context. Fresh accounts may also finish mailbox, deposit-address, and provider setup on this first authenticated read.
60	2. `POST /api/payment-intents` for the exact purchase.
61	3. If `agentAutoApproveEnabled` is off, wait for dashboard approval. If it is on, the API-key task can move directly toward `approved` and `card_ready`. Approved tasks can auto-prepare or reuse the account's hidden execution card when wallet funding is available.
62	On the first hidden-card bootstrap for an account, MoneyClaw may reserve the provider minimum initial deposit onto that shared hidden card even if the current task amount is smaller. Any residual stays on the same hidden card for later tasks.
63	4. Use `GET /api/payment-intents/:intentId/credentials` only when the task is `card_ready` and the user explicitly asked to continue the current payment step.
64	5. After a successful one-time checkout, use `POST /api/payment-intents/:intentId/reconcile` to write the settled charge back into MoneyClaw accounting.
65	6. Inspect payment-task state and wallet transactions before retrying.
66
67	## Load References When Needed
68
69	- Read `references/payment-safety.md` before entering payment details on an unfamiliar merchant, when a checkout keeps failing, or when retry boundaries matter.
70
71	## Core Jobs
72
73	### 1. Check account readiness
74
75	```bash
76	curl -H "Authorization: Bearer $MONEYCLAW_API_KEY" \
77	https://moneyclaw.ai/api/me
78	```
79
80	Important fields:
81
82	- `balance`: wallet balance
83	- `depositAddress`: where to send USDT
84	- `mailboxAddress`: inbox address for receipts and account messages
85	- `agentAutoApproveEnabled`: whether API-key-created payment tasks can auto-approve without a dashboard click
86
87	When the user asks for readiness, report wallet balance, deposit address, inbox state, and whether a payment task can proceed.
88
89	### 2. Create an auditable payment task
90
91	```bash
92	curl -X POST -H "Authorization: Bearer

People who liked this also viewed

6 picks

Type