BC trongrid-transaction-info
Query and decode TRON transactions including status, confirmation, sender/receiver, resource costs, internal transactions, event logs, and failure analysis. Use when a user asks about a transaction hash, wants to check if a transaction succeeded, understand what a transaction did, or debug a failed transaction.
As a process C 62/100 · Has gaps — weak spots: result and completion, when it triggers, progress reporting
How to improve
- 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 · 7
✓ No critical or high findings
Medium and low: 7
-
low Secrets in code
secret-high-entropy-tokenexamples/check-transfer-status.md:32High-entropy token-like string (may be an id, hash or a credential) (test fixture / example file)- From: TUoH…uJM
fixture -
low Secrets in code
secret-high-entropy-tokenexamples/check-transfer-status.md:33High-entropy token-like string (may be an id, hash or a credential) (test fixture / example file)- To: TLsV…Uzy
fixture -
low Secrets in code
secret-high-entropy-tokenexamples/check-transfer-status.md:34High-entropy token-like string (may be an id, hash or a credential) (test fixture / example file)- Contract: TR7N…j6t (USDT)
fixture -
low Secrets in code
secret-high-entropy-tokenexamples/check-transfer-status.md:40High-entropy token-like string (may be an id, hash or a credential) (test fixture / example file)- Recipient: TLsV…Uzy
fixture -
low Secrets in code
secret-high-entropy-tokenexamples/decode-contract-call.md:32High-entropy token-like string (may be an id, hash or a credential) (test fixture / example file)- From: TJmm…PFh
fixture -
low Secrets in code
secret-high-entropy-tokenexamples/decode-contract-call.md:33High-entropy token-like string (may be an id, hash or a credential) (test fixture / example file)- Contract: TKcE…31b (SunSwap V2 Router)
fixture -
low Secrets in code
secret-high-entropy-tokenexamples/decode-contract-call.md:41High-entropy token-like string (may be an id, hash or a credential) (test fixture / example file)- recipient: TJmm…PFh
fixture
Files scanned: 4. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
✓ No remarks against the Agent Skills spec
Process rating: all ten parameters 62/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
- 60Tools and files. Uses tools (web, node) that frontmatter does not declare
- 70Inputs and preconditions. Inputs and preconditions are listed
- 85Steps. 29 steps, 1 vague phrases
- 100Failures and branches. 1 branches, has a failure section
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 1126 tokens
- 100Running it twice. Mutating operations check current state
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 312: enough signal without eating the budget
- +4Structure: 13 headings
- +3Step-by-step instructions: 29 items
- +4Has examples (1 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 84.