SKILLEMALL.ai
GitHub ↗ RU Sign in

BC trongrid-contract-analysis

Analyze TRON smart contracts including deployment info, ABI methods, transaction patterns, top callers, energy costs, and safety assessment. Use when a user asks about a smart contract, wants to verify contract safety, check what a contract does, identify top callers, or detect potential scams. Covers TRC-20/TRC-721 identification, open-source verification, and risk scoring.

ClawHub Agent Skills author: greason v1.0.2 MIT-0 4 files body ≈ 1 003 tokens Open the sourceclawhub.ai↗ analyzed 3 d ago

As a process C 56/100 · Has gaps — weak spots: result and completion, when it triggers, running it twice

AnalyzerInfrastructuretype and topics are labelled automatically from the skill text
Runs in: OpenClaw Claude / Claude Code ChatGPT / Codex Gemini CLI Cursor GitHub Copilot / VS Code Qwen Code Kimi Code CLI Z.ai (GLM) DeepSeek (Deep Code) Mistral Vibe LangChain (deepagents) Goose OpenCode
JSON
Technical rating
B
88/100
safety, quality, tests
Safety 60%
90
Quality 40%
84
Run on models
none yet
Process rating
C
56/100
Has gaps
Result and completion w 14
0
Progress reporting w 2
0
When it triggers w 12
20
the three weakest of ten parameters · all ten

How to improve

    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 · 10

    ✓ No critical or high findings

    Medium and low: 10
    • low Secrets in code secret-high-entropy-token examples/analyze-usdt-contract.md:6
      High-entropy token-like string (may be an id, hash or a credential) (test fixture / example file)
      Analyze the USDT contract on TRON: TR7N…j6t
      fixture
    • low Secrets in code secret-high-entropy-token examples/analyze-usdt-contract.md:11
      High-entropy token-like string (may be an id, hash or a credential) (test fixture / example file; quoted — discussed, not commanded)
      1. **Contract Info** → `getContractInfo("TR7N…j6t")` → Settings, deployer
      fixturequoted
    • low Secrets in code secret-high-entropy-token examples/analyze-usdt-contract.md:12
      High-entropy token-like string (may be an id, hash or a credential) (test fixture / example file; quoted — discussed, not commanded)
      2. **Contract ABI** → `getContract("TR7N…j6t")` → Full ABI + bytecode
      fixturequoted
    • low Secrets in code secret-high-entropy-token examples/analyze-usdt-contract.md:13
      High-entropy token-like string (may be an id, hash or a credential) (test fixture / example file; quoted — discussed, not commanded)
      3. **Token Info** → `getT…nfo("TR7N…j6t")` → Name, symbol, decimals
      fixturequoted
    • low Secrets in code secret-high-entropy-token examples/analyze-usdt-contract.md:14
      High-entropy token-like string (may be an id, hash or a credential) (test fixture / example file; quoted — discussed, not commanded)
      4. **Transactions** → `getContractTransactions("TR7N…j6t", limit=200)` → Recent calls
      fixturequoted
    • low Secrets in code secret-high-entropy-token examples/check-contract-safety.md:6
      High-entropy token-like string (may be an id, hash or a credential) (test fixture / example file)
      Is the contract TQn9…LSE safe to interact with?
      fixture
    • low Secrets in code secret-high-entropy-token examples/check-contract-safety.md:11
      High-entropy token-like string (may be an id, hash or a credential) (test fixture / example file; quoted — discussed, not commanded)
      1. **Contract Info** → `getContractInfo("TQn9…LSE")` → Deployer, energy settings
      fixturequoted
    • low Secrets in code secret-high-entropy-token examples/check-contract-safety.md:12
      High-entropy token-like string (may be an id, hash or a credential) (detector / deny-list definition; test fixture / example file)
      2. **Contract ABI** → `getContract("TQn9…LSE")` → ABI for method analysis
      detectorfixture
    • low Secrets in code secret-high-entropy-token examples/check-contract-safety.md:13
      High-entropy token-like string (may be an id, hash or a credential) (test fixture / example file; quoted — discussed, not commanded)
      3. **Token Info** → `getT…nfo("TQn9…LSE")` → Check if it's a token
      fixturequoted
    • low Secrets in code secret-high-entropy-token examples/check-contract-safety.md:14
      High-entropy token-like string (may be an id, hash or a credential) (test fixture / example file; quoted — discussed, not commanded)
      4. **Transactions** → `getContractTransactions("TQn9…LSE", limit=100)` → Activity
      fixturequoted

    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 56/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
    • 30Running it twice. 5 mutating operations with no state check
    • 50Failures and branches. 0 branches, has a failure section
    • 60Tools and files. Uses tools (web) that frontmatter does not declare
    • 70Inputs and preconditions. Inputs and preconditions are listed
    • 100Steps. 30 steps
    • 100Consistency. Name and required fields are in place
    • 100Execution cost. Instruction body is 1003 tokens

    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 377: enough signal without eating the budget
    • +4Structure: 12 headings
    • +3Step-by-step instructions: 30 items
    • +4Has examples (1 code blocks)

    Quality base 70; lint remarks subtract, signals add up to 100. Result: 84.

    External checks

    ClawHub: clean
    This is a read-only TRON smart contract analysis skill with no evidence of hidden behavior, credential use, persistence, or account-changing actions.
    LLM: benign (high) · VirusTotal: · 29 May 2026