BC trongrid-account-profiling
Analyze any TRON account's assets, token holdings, staking, voting, energy/bandwidth, and transaction patterns. Use when a user asks about a TRON address, wants to check wallet balance, analyze account activity, track whale wallets, or look up what an address holds. Covers TRX balance, TRC-20/TRC-10 tokens, resource usage, delegation, voting rewards, transaction history, and DeFi participation.
As a process C 64/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 · 11
✓ No critical or high findings
Medium and low: 11
-
low Secrets in code
secret-high-entropy-tokenexamples/analyze-whale-account.md:6High-entropy token-like string (may be an id, hash or a credential) (test fixture / example file)Analyze the wallet TLsV…Uzy — what does it hold,
fixture -
low Secrets in code
secret-high-entropy-tokenexamples/analyze-whale-account.md:12High-entropy token-like string (may be an id, hash or a credential) (test fixture / example file; quoted — discussed, not commanded)1. **Validate Address** → `validateAddress("TLsV…Uzy")` → Confirm validfixturequoted -
low Secrets in code
secret-high-entropy-tokenexamples/analyze-whale-account.md:13High-entropy token-like string (may be an id, hash or a credential) (test fixture / example file; quoted — discussed, not commanded)2. **Account Info** → `getAccount("TLsV…Uzy")` → TRX balance, frozen assets, votesfixturequoted -
low Secrets in code
secret-high-entropy-tokenexamples/analyze-whale-account.md:14High-entropy token-like string (may be an id, hash or a credential) (detector / deny-list definition; test fixture / example file)3. **Resources** → `getAccountResource("TLsV…Uzy")` → Energy/bandwidth limitsdetectorfixture -
low Secrets in code
secret-high-entropy-tokenexamples/analyze-whale-account.md:15High-entropy token-like string (may be an id, hash or a credential) (detector / deny-list definition; test fixture / example file)4. **TRC-20 Balances** → `getT…nce("TLsV…Uzy")` → Token holdingsdetectorfixture -
low Secrets in code
secret-high-entropy-tokenexamples/check-account-balance.md:6High-entropy token-like string (may be an id, hash or a credential) (test fixture / example file)What is the balance of TUoH…uJM?
fixture -
low Secrets in code
secret-high-entropy-tokenexamples/check-account-balance.md:11High-entropy token-like string (may be an id, hash or a credential) (test fixture / example file; quoted — discussed, not commanded)1. **Validate** → `validateAddress("TUoH…uJM")`fixturequoted -
low Secrets in code
secret-high-entropy-tokenexamples/check-account-balance.md:12High-entropy token-like string (may be an id, hash or a credential) (test fixture / example file; quoted — discussed, not commanded)2. **Account Info** → `getAccount("TUoH…uJM")` → TRX balance + TRC-10 tokensfixturequoted -
low Secrets in code
secret-high-entropy-tokenexamples/check-account-balance.md:13High-entropy token-like string (may be an id, hash or a credential) (test fixture / example file; quoted — discussed, not commanded)3. **TRC-20 Balances** → `getT…nce("TUoH…uJM")` → Token holdingsfixturequoted -
low Secrets in code
secret-high-entropy-tokenexamples/check-account-balance.md:19High-entropy token-like string (may be an id, hash or a credential) (test fixture / example file)## Account Profile: TUoH…uJM
fixture -
low Secrets in code
secret-high-entropy-tokenSKILL.md:38High-entropy token-like string (may be an id, hash or a credential) (detector / deny-list definition)1. `getD…xV2` — List of addresses this account delegates to / receives from
detector
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 64/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) that frontmatter does not declare
- 70Inputs and preconditions. Inputs and preconditions are listed
- 100Steps. 16 steps
- 100Failures and branches. 1 branches, has a failure section
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 928 tokens
- 100Running it twice. No mutating operations
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 397: enough signal without eating the budget
- +4Structure: 12 headings
- +3Step-by-step instructions: 16 items
- +4Has examples (1 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 84.