BB paygents
Accept crypto payments in AI agent conversations. Generate MetaMask/Trust Wallet deeplinks, verify transactions on-chain, check balances, issue receipts. No custody, no backend, no API keys.
Accept crypto payments in AI agent conversations.
As a process B 68/100 · Nearly there — weak spots: result and completion, when it triggers, running it twice
IntegrationAI and agentsSoftware developmenttype and topics are labelled automatically from the skill text
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 · 15
✓ No critical or high findings
Medium and low: 15
-
low Secrets in code
secret-high-entropy-tokenREADME.md:116High-entropy token-like string (may be an id, hash or a credential) (documentation table row)| Ethereum | `1` | `0xA0…b48` |
table -
low Secrets in code
secret-high-entropy-tokenREADME.md:117High-entropy token-like string (may be an id, hash or a credential) (documentation table row)| Base | `8453` | `0x83…913` |
table -
low Secrets in code
secret-high-entropy-tokenREADME.md:119High-entropy token-like string (may be an id, hash or a credential) (documentation table row)| Base Sepolia (testnet) | `84532` | `0x03…f7e` |
table -
low Secrets in code
secret-high-entropy-tokenreferences/evm-usdc-poc.md:19High-entropy token-like string (may be an id, hash or a credential) (documentation table row)| Ethereum | 1 | `0xA0…b48` |
table -
low Secrets in code
secret-high-entropy-tokenreferences/evm-usdc-poc.md:20High-entropy token-like string (may be an id, hash or a credential) (documentation table row)| Base | 8453 | `0x83…913` |
table -
low Secrets in code
secret-high-entropy-tokenreferences/evm-usdc-poc.md:22High-entropy token-like string (may be an id, hash or a credential) (documentation table row)| Base Sepolia | 84532 | `0x03…f7e` |
table -
low Secrets in code
secret-high-entropy-tokenscripts/evm-payment-link.sh:91High-entropy token-like string (may be an id, hash or a credential) (quoted — discussed, not commanded)1) TOKEN="0xA0…b48" ;;
quoted -
low Secrets in code
secret-high-entropy-tokenscripts/evm-payment-link.sh:92High-entropy token-like string (may be an id, hash or a credential) (quoted — discussed, not commanded)8453) TOKEN="0x83…913" ;;
quoted -
low Secrets in code
secret-high-entropy-tokenscripts/evm-payment-link.sh:94High-entropy token-like string (may be an id, hash or a credential) (quoted — discussed, not commanded)84532) TOKEN="0x03…f7e" ;;
quoted -
low Secrets in code
secret-high-entropy-tokenscripts/evm-verify-tx.sh:62High-entropy token-like string (may be an id, hash or a credential) (quoted — discussed, not commanded)1) TOKEN="0xA0…b48" ;;
quoted -
low Secrets in code
secret-high-entropy-tokenscripts/evm-verify-tx.sh:63High-entropy token-like string (may be an id, hash or a credential) (quoted — discussed, not commanded)8453) TOKEN="0x83…913" ;;
quoted -
low Secrets in code
secret-high-entropy-tokenscripts/evm-verify-tx.sh:65High-entropy token-like string (may be an id, hash or a credential) (quoted — discussed, not commanded)84532) TOKEN="0x03…f7e" ;;
quoted -
low Secrets in code
secret-high-entropy-tokenSKILL.md:122High-entropy token-like string (may be an id, hash or a credential) (documentation table row)| Ethereum | 1 | `0xA0…b48` |
table -
low Secrets in code
secret-high-entropy-tokenSKILL.md:123High-entropy token-like string (may be an id, hash or a credential) (documentation table row)| Base | 8453 | `0x83…913` |
table -
low Secrets in code
secret-high-entropy-tokenSKILL.md:125High-entropy token-like string (may be an id, hash or a credential) (documentation table row)| Base Sepolia | 84532 | `0x03…f7e` |
table
Files scanned: 9. 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 68/100
- 0Result and completion. Does not say what the result is
- 0Progress reporting. Says nothing while it works
- 20When it triggers. No condition that starts the skill
- 30Running it twice. 9 mutating operations with no state check
- 70Inputs and preconditions. Inputs and preconditions are listed
- 100Tools and files. No external tools needed
- 100Steps. 24 steps
- 100Failures and branches. 1 branches, has a failure section
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 1592 tokens
- medium Safety rules and hard prohibitions inside a skill: they belong in the system prompt, here they protect nothing
- low 11 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
- -41 reference files, but SKILL.md never points to them: the model will not open them
- +1No license
- +2Single-language instructions
- +3Description length 190: enough signal without eating the budget
- +4Structure: 14 headings
- +3Step-by-step instructions: 24 items
- +4Has examples (10 code blocks)
- +3All 4 scripts are documented
Quality base 70; lint remarks subtract, signals add up to 100. Result: 71.