ChainGPT-orgChainGPT-org/chaingpt-claude-skill/skills/tron/SKILL.md

tron

Skill7 starsChanged 53 days agoMITView on GitHub

Tron (TVM) support via the ChainGPT plugin — at parity with the EVM + Solana surfaces. Read balances/resources/tx, research (DexScreener), risk (GoPlus), build UNSIGNED native TRX + TRC-20 transfers (custody-free), SunSwap quotes, JustLend lending, and (when the operator enabled the agent wallet) policy-gated agent-wallet signing. The agent's Tron account uses the SAME key as the EVM agent wallet. Triggers: tron, TRX, TRC-20, USDT on tron, sun swap, sunswap, justlend, tronscan, send TRX, tron balance, tron wallet.

Reads credentials

We split this skill into the rules it gives an agent

2 rules. About 0 are common, 1 is distinctive, and 1 is very specific to this project.

≈0
Common · estimate
Many files like this have a rule of this kind.
≈1
Distinctive · estimate
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.

Common
Distinctive
Very specific

Very specific:
ALWAYS confirm an address with chaingpt_tron_validate_address if unsure — a bad checksum is rejected, but a valid-but-wrong address is not.
line 59
Distinctive:
NEVER use a poisoned address (USDDOLD, old SUN).
line 60

≈ “Common” is an estimate: at least 1 in 5 of the 308,232 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.

Files

SKILL.md

ChainGPT Tron Skill

You operate on Tron, a non-EVM chain (TVM). It is bytecode-compatible with the EVM but the account, address, fee, and transaction layers differ. Key facts:

Addresses are base58 T… (34 chars). The same secp256k1 key controls both an ETH EOA and a Tron account; only the encoding differs (0x41 + Base58Check). So the agent's Tron address is derived from its existing EVM agent wallet — there is no separate _init.
Units: 1 TRX = 1,000,000 SUN (6 decimals). Contract calls burn Energy (capped by fee_limit); transactions burn Bandwidth. Sending to a never-activated address costs ~1.1 TRX.
No OpenOcean/1inch on Tron — DEX routing uses SunSwap; lending uses JustLend.
Custody-free by default: builders return an UNSIGNED tx (sign in TronLink, or via the agent wallet if it is enabled). Mainnet builders require acknowledgeMainnet: true.

Tools

Tool	Purpose
`chaingpt_tron_validate_address`	Validate + show hex/EVM forms (offline)
`chaingpt_tron_balances`	TRX + resources + TRC-20 balances
`chaingpt_tron_token_balance`	One TRC-20 balance (resolves decimals on-chain)
`chaingpt_tron_account_resources`	Bandwidth + energy
`chaingpt_tron_tx_info`	Receipt by txid
`chaingpt_tron_research_token`	DexScreener price/liquidity/volume
`chaingpt_tron_risk_token`	GoPlus security scan
`chaingpt_tron_build_transfer_tx`	Unsigned native TRX transfer
`chaingpt_tron_build_trc20_transfer_tx`	Unsigned TRC-20 transfer
`chaingpt_tron_dex_sunswap_quote`	SunSwap swap quote (read)
`chaingpt_tron_lend_justlend_account`	JustLend liquidity + per-market balances
`chaingpt_tron_lend_justlend_build_tx`	Unsigned JustLend approve/supply/withdraw/borrow/repay
`chaingpt_agent_wallet_tron_address`	Agent's Tron address + TRX balance
`chaingpt_agent_wallet_tron_sign_and_send`	Build + sign + broadcast under the `tron` policy

Pipelines

Send a token (custody-free):

chaingpt_tron_risk_token (optional gate) → chaingpt_tron_build_trc20_transfer_tx (acknowledgeMainnet:true) → sign in TronLink

Autonomous send (agent wallet, off by default): The agent wallet is disabled by default; chaingpt_agent_wallet_* tools exist only if the operator set CHAINGPT_AGENT_WALLET_ENABLED=true. If they are missing, use the unsigned builders and have the user sign.

chaingpt_agent_wallet_tron_address (fund it) → chaingpt_agent_wallet_tron_sign_and_send { kind:"trc20_transfer", token:"USDT", to, amount, memo }

The deterministic tron policy gate enforces the destination allowlist, per-tx + rolling-24h SUN caps, the fee_limit cap, and a memo before signing. Tron signing requires "tron": { "enabled": true } in the policy (fail-closed for policy files that predate Tron). No MCP tool can relax the policy.

Lend on JustLend:

chaingpt_tron_lend_justlend_account → build approve (TRC-20 markets) → build supply → sign

Environment

TRON_PRO_API_KEY — TronGrid key (mainnet keyless is throttled).
TRON_RPC_URL — override the node host. Agent-wallet signing refuses a non-TronGrid host.

Rules

ALWAYS confirm an address with chaingpt_tron_validate_address if unsure — a bad checksum is rejected, but a valid-but-wrong address is not.
NEVER use a poisoned address (USDDOLD, old SUN); the registry blocks them.
Set a slippage-protected minAmountOut before executing any swap; SunSwap V2 quotes are indicative.
TRC-20 supply/repay on JustLend need a prior approve.

Download now (ZIP)

In this repository23 other files it gives its agents.
- aaSkill
- agent-walletSkill
- baseSkill
- bridgeSkill
- chaingptSkill
- dashboardSkill
- debugSkill
- defiSkill
- deploySkill
- driftSkill
- hackathonSkill
- hyperliquidSkill
- playgroundSkill
- polymarketSkill
- researchSkill
- scheduled-autonomySkill
- securitySkill
- solanaSkill
- strategySkill
- tradeSkill
- trustless-agentsSkill
- updateSkill
- x402Skill

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

Reviews can't be read right now.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free