BC tron-x402-payment
Pay for x402-enabled Agent endpoints using TRC20 tokens (USDT/USDD) on TRON
Pay for x402-enabled Agent endpoints using TRC20 tokens (USDT/USDD) on TRON
As a process C 63/100 · Has gaps — weak spots: result and completion, progress reporting
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-tokenSKILL.md:136High-entropy token-like string (may be an id, hash or a credential) (documentation table row)| USDT | Mainnet | `TR7N…j6t` | 6 |
table -
low Secrets in code
secret-high-entropy-tokenSKILL.md:137High-entropy token-like string (may be an id, hash or a credential) (documentation table row)| USDT | Nile | `TXYZ…eBf` | 6 |
table -
low Secrets in code
secret-high-entropy-tokenSKILL.md:138High-entropy token-like string (may be an id, hash or a credential) (documentation table row)| USDT | Shasta | `TG3X…ozs` | 6 |
table -
low Secrets in code
secret-high-entropy-tokenSKILL.md:139High-entropy token-like string (may be an id, hash or a credential) (documentation table row)| USDD | Mainnet | `TXDk…9Hz` | 18 |
table -
low Secrets in code
secret-high-entropy-tokenSKILL.md:230High-entropy token-like string (may be an id, hash or a credential) (documentation table row)| TRON Mainnet | 0x2b6653dc | `eip1…428`, `tron:mainnet` | `TR7N…j6t` | `TXDk…9Hz` |
table
Files scanned: 4. 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") - note
frontmatter-keyunknown frontmatter key "homepage" - note
frontmatter-keyunknown frontmatter key "requires_tools" - note
frontmatter-keyunknown frontmatter key "arguments"
Process rating: all ten parameters 63/100
- 0Result and completion. Does not say what the result is
- 0Progress reporting. Says nothing while it works
- 50When it triggers. No condition that starts the skill
- 50Failures and branches. 0 branches, has a failure section
- 60Tools and files. Uses tools (bash, web, node) that frontmatter does not declare
- 70Inputs and preconditions. Inputs and preconditions are listed
- 100Steps. 33 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 2092 tokens
- 100Running it twice. Mutating operations check current state
- 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)
- +3Description length 75: 120–800 characters recommended
- +3Output format is not stated: the model decides each time
- +1No license
- +2Single-language instructions
- +4Structure: 21 headings
- +3Step-by-step instructions: 33 items
- +4Has examples (6 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 66.