BC near-getpay
Accept crypto payments (NEAR, USDC, USDT) via a beautiful payment page with PingPay or HOT PAY integration.
As a process C 51/100 · Has gaps — 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 · 8
✓ No critical or high findings
Medium and low: 8
-
low Secrets in code
secret-high-entropy-tokenindex.ts:203High-entropy token-like string (may be an id, hash or a credential) (quoted — discussed, not commanded)Example: ts-node index.ts create-test 10 0x30…77D
quoted -
low Secrets in code
secret-high-entropy-tokenpackage-lock.json:72High-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:143High-entropy token-like string (may be an id, hash or a credential) (detector / deny-list definition)"integrity": "sha5…tdy+f/7ZBx…bag==",
detector -
low Secrets in code
secret-high-entropy-tokenpackage-lock.json:153High-entropy token-like string (may be an id, hash or a credential) (detector / deny-list definition)"integrity": "sha5…asG+Fkr6…2vM+P9eO…k5W+1WL8w==",
detector -
low Secrets in code
secret-high-entropy-tokenpackage-lock.json:258High-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:264High-entropy token-like string (may be an id, hash or a credential) (detector / deny-list definition)"integrity": "sha5…FFX/+gVeY…NlM++NqRc…bqg==",
detector -
low Exfiltration
read-dotenvskill.json:32Reads a .env file (quoted — discussed, not commanded)"Copy .env.example to .env",
quoted -
low Exfiltration
read-dotenvSKILL.md:67Reads a .env filecp .env.example .env
Files scanned: 14. 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 51/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. 9 mutating operations with no state check
- 100Tools and files. No external tools needed
- 100Steps. 48 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 1966 tokens
- 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)
- +3Description length 107: 120–800 characters recommended
- +3Output format is not stated: the model decides each time
- -2localhost URLs: will not work for another user
- -218 emoji in the instructions: noise for the model
- +1No license
- +2Single-language instructions
- +4Structure: 38 headings
- +3Step-by-step instructions: 48 items
- +4Has examples (15 code blocks)
- +3All 2 scripts are documented
Quality base 70; lint remarks subtract, signals add up to 100. Result: 68.
External checks
ClawHub: suspicious
The skill mostly does what it advertises, but it also includes under-disclosed crypto payment execution paths and unsafe credential/public-server guidance that users should review carefully.
LLM: suspicious (high) · VirusTotal: suspicious · 28 May 2026