BC ripley-pocket
API client skill for Ripley Pocket — the M2M micro-payment gateway for AI agents. Use this skill whenever you need to: send or receive payments between AI agents, check an agent's XMR balance, withdraw Monero to an external address, swap XMR cross-chain to BTC/ETH/USDT/LTC, deposit BTC/ETH/USDT/LTC and auto-convert to XMR balance, register a new agent account, or view transaction history. Triggers on any mention of Ripley Pocket, agent payments, XMR/Monero payments, micro-payments between agents, POST /pay, X-API-KEY, deposit swap, fund account with BTC/ETH, or the XMR402 payment protocol. Also use when the user wants to integrate an AI agent with a payment system, fund an agent wallet with non-XMR crypto, or asks about paying for API calls with crypto.
As a process C 55/100 · Has gaps — weak spots: result and completion, inputs and preconditions, consistency
What is at stake
Medium-severity findings: the skill is probably honest, but read what alarmed the scanner.
Below is the worst case for this category. The finding here is medium: the guard saw a sign, not a proof.
The instructions or scripts send data out: environment variables, keys, file contents, chat history. You may never notice, because the agent performs the upload as "part of the task".
If the upload is not needed for the task, remove it: catalogs flag such skills and delist them. If it is needed, name the destination explicitly, say what leaves the machine, and give the user a switch.
How to improve
- Your own cases (evals/evals.json, 4–6 real requests with expected answers): the full check would then run those instead of a model-drafted suite.
- A spec.yaml with trigger phrases and assertions — a behaviour contract for CI; `skilltest init` writes a template.
Guard findings · 3
✓ No critical or high findings
Medium and low: 3
-
medium Exfiltration
net-credential-useSKILL.md:69Credential used in a network call (verify the destination is the intended service)curl $RIPLEY_URL/balance -H "X-API-KEY: $API_KEY"
-
medium Exfiltration
net-credential-useSKILL.md:211Credential used in a network call (verify the destination is the intended service)curl $RIPLEY_URL/deposit/swaps -H "X-API-KEY: $API_KEY"
-
medium Exfiltration
net-credential-useSKILL.md:246Credential used in a network call (verify the destination is the intended service)curl $RIPLEY_URL/swaps -H "X-API-KEY: $API_KEY"
Files scanned: 2. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- note
frontmatter-keyunknown frontmatter key "requiredEnv" - note
frontmatter-keyunknown frontmatter key "primaryEnv" - note
frontmatter-keyunknown frontmatter key "defaultEnv"
Process rating: all ten parameters 55/100
- 0Result and completion. Does not say what the result is
- 0Inputs and preconditions. Does not say what the process needs to start
- 0Progress reporting. Says nothing while it works
- 30Running it twice. 6 mutating operations with no state check
- 40Consistency. Frontmatter name (ripley-pocket) differs from the folder (monero-pocket)
- 60Tools and files. Uses tools (web, python) that frontmatter does not declare
- 70When it triggers. States when to use, but not when not to
- 100Steps. 14 steps
- 100Failures and branches. 4 branches, has a failure section
- 100Execution cost. Instruction body is 3737 tokens
- low 12 top-level sections: this looks like several domains in one skill
Everything here is measured from the skill text rather than judged by a model, so the numbers are checkable. A parameter weighs more when it is a more common reason for the process to stall.
Quality signals
- +5Description has no quoted example phrases that should trigger the skill
- +4Description does not say when NOT to use the skill (false activations)
- +3Output format is not stated: the model decides each time
- -2localhost URLs: will not work for another user
- +1No license
- +2Single-language instructions
- +3Description length 763: enough signal without eating the budget
- +4Structure: 23 headings
- +3Step-by-step instructions: 14 items
- +4Has examples (25 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 79.