BD payclaw
Agent-to-Agent USDC payments. Create wallets, send/receive payments, escrow between agents. Built for the USDC Hackathon on Moltbook.
As a process D 43/100 · Unfinished process — weak spots: result and completion, when it triggers, inputs and preconditions
How to improve
- Say in the description WHEN to use the skill ("use when…", example requests): that is the agent's main cue.
For the model run — optional
- 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 · 5
✓ No critical or high findings
Medium and low: 5
-
low Secrets in code
secret-high-entropy-tokenpackage-lock.json:74High-entropy token-like string (may be an id, hash or a credential) (detector / deny-list definition)"integrity": "sha5…xCA+ORZv…wO5/ywWF…Tag==",
detector -
low Secrets in code
secret-high-entropy-tokenpackage-lock.json:131High-entropy token-like string (may be an id, hash or a credential) (detector / deny-list definition)"integrity": "sha5…MfZ+71RA…HvA==",
detector -
low Secrets in code
secret-high-entropy-tokenpackage-lock.json:147High-entropy token-like string (may be an id, hash or a credential) (detector / deny-list definition)"integrity": "sha5…Kxf+MSr9…jrj/FHl8…mYA+ftRkP/3oKQ==",
detector -
low Secrets in code
secret-high-entropy-tokenpackage-lock.json:154High-entropy token-like string (may be an id, hash or a credential) (detector / deny-list definition)"integrity": "sha5…TPG/KSnE…ao6+eXF3…fAT+nCNwQ==",
detector -
low Secrets in code
secret-high-entropy-tokenpackage-lock.json:229High-entropy token-like string (may be an id, hash or a credential) (detector / deny-list definition)"integrity": "sha5…wQp+7C4n…9JQ==",
detector
Files scanned: 8. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
description-no-whendescription does not say WHEN to use the skill (no "use when")
Process rating: all ten parameters 43/100
- 0Result and completion. Does not say what the result is
- 0Inputs and preconditions. Does not say what the process needs to start
- 0Failures and branches. Linear process with no failure handling
- 0Progress reporting. Says nothing while it works
- 20When it triggers. No condition that starts the skill
- 30Running it twice. 3 mutating operations with no state check
- 60Tools and files. Uses tools (web) that frontmatter does not declare
- 100Steps. 19 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 1167 tokens
- medium Safety rules and hard prohibitions inside a skill: they belong in the system prompt, here they protect nothing
- low 13 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
- +1No license
- +2Single-language instructions
- +3Description length 133: enough signal without eating the budget
- +4Structure: 21 headings
- +3Step-by-step instructions: 19 items
- +4Has examples (11 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 72.
External checks
ClawHub: suspicious
PayClaw is a coherent payments skill, but it has high-impact safety issues in command execution, credential handling, and misleading escrow behavior that users should review before installing.
LLM: suspicious (high) · VirusTotal: suspicious · 10 Sept 2026