BC tronlink
Work with TronLink wallet - manage TRX and TRC-20 tokens, stake for energy/bandwidth, vote for super representatives, and interact with TRON dApps.
Work with TronLink wallet - manage TRX and TRC-20 tokens, stake for energy/bandwidth, vote for super representatives, and interact with TRON dApps.
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.
- 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:47High-entropy token-like string (may be an id, hash or a credential) (quoted — discussed, not commanded)contract = client.get_contract('TR7N…j6t')quoted -
low Secrets in code
secret-high-entropy-tokenSKILL.md:58High-entropy token-like string (may be an id, hash or a credential)USDT: TR7N…j6t
-
low Secrets in code
secret-high-entropy-tokenSKILL.md:59High-entropy token-like string (may be an id, hash or a credential)USDC: TEkx…dz8
-
low Secrets in code
secret-high-entropy-tokenSKILL.md:60High-entropy token-like string (may be an id, hash or a credential)BTT: TAFj…Vp4
-
low Secrets in code
secret-high-entropy-tokenSKILL.md:61High-entropy token-like string (may be an id, hash or a credential)JST: TCFL…Zy9
Files scanned: 1. 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
- 0Progress reporting. Says nothing while it works
- 20When it triggers. No condition that starts the skill
- 50Failures and branches. 0 branches, has a failure section
- 60Tools and files. Uses tools (node) that frontmatter does not declare
- 100Steps. 15 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 1154 tokens
- 100Running it twice. No mutating operations
- low 17 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 147: enough signal without eating the budget
- +4Structure: 18 headings
- +3Step-by-step instructions: 15 items
- +4Has examples (12 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 72.