telos-network-skill

An agent skill that makes any coding agent operational on the Telos Network — Telos EVM + Telos Zero (Antelope).

With this skill loaded, an agent can:

• Read Telos EVM state (balances, contracts, receipts) via JSON-RPC / Foundry cast
• Sign and broadcast EVM transactions with correct fixed-gas-price behavior
• Deploy and verify Solidity with Foundry, Hardhat, or viem
• Use system contracts: WTLOS, sTLOS, TelosEscrow, LayerZero endpoints
• Operate the Telos Privacy layer (zkWallet / zkTelos pools, SDK, direct deposits)
• Query and push Telos Zero actions with cleos
• Understand node role topology (nodeos → reth → consensus) without private ops secrets

Default surface: Telos EVM mainnet, chain ID 40.
Testnet (41) and Telos Zero are documented as secondary paths.

Install

Claude Code (project skill via submodule):

cd <your-project>/.claude/skills
git submodule add https://github.com/telosnetwork/telos-network-skill telos-network

Any agent (clone or symlink into your skills directory):

git clone https://github.com/telosnetwork/telos-network-skill /path/to/skills/telos-network

The agent loads telos-network/SKILL.md and follows its decision tree into references/.

Contents

SKILL.md                 orchestrator: triggers, defaults, decision tree, safety
references/
  chain.md               RPCs, chain IDs, explorers, bridges, faucets
  install.md             Foundry, Node, cleos, node software entrypoints
  keys.md                EVM keys, Safe, Zero keys, secret hygiene
  transactions.md        gas, nonces, broadcast, receipts, errors
  queries.md             read-only cast/curl recipes
  contracts.md           system addresses, deploy/verify, sTLOS, LZ
  privacy.md             zkWallet, pools, SDK, direct deposits
  zero.md                Antelope accounts, resources, cleos
  nodes.md               public node architecture + restart order
  brand.md               logos, palette, typography + branding hub link
scripts/
  check-rpc.sh           chainId / head / gasPrice health
  verify-evm-tx.sh       poll receipt + summarize
  send-tlos.sh           native TLOS transfer helper (PK via env)
evals/
  evals.json             regression prompts for skill behavior

Defaults

Setting	Value
Surface	Telos EVM mainnet
Chain ID	40
RPC	https://rpc.telos.net
Explorer	teloscan.io
Privacy UI	zkwallet.telos.net
Bridge	bridge.telos.net
Brand guidelines	telos.net/branding
Zero API	https://mainnet.telos.net
CLI	Foundry cast / forge; cleos for Zero

In scope

• Telos EVM mainnet + testnet
• Telos Zero mainnet + testnet (Antelope)
• System contracts and LayerZero endpoints documented by Telos
• Telos Privacy (zkTelos) developer + operator-facing recipes
• Public node role model
• Brand guidance for agents (telos.net/branding + references/brand.md)

Out of scope

• Other chains’ defaults (Ethereum, Base, etc.) except bridging to/from Telos
• Private operator hosts, passwords, JWT contents, producer keys
• Inventing unofficial logos/wordmarks (use official branding only)
• Legal determinations about privacy compliance in a given jurisdiction

Language

• Prefer Antelope over “EOSIO”
• Prefer Telos EVM in user-facing copy
• Native token: TLOS
• Branding tasks: start at telos.net/branding

Verifying examples

Contract addresses come from official Telos docs and the public token list at authoring time. Before high-stakes use, re-check:

• Network info
• Telos contracts
• Privacy contracts
• Token list

License

MIT — see LICENSE.

Contributing

Issues and PRs welcome.

If you change an address, RPC, or ABI assumption, cite the upstream source (docs commit, Teloscan verified code, or token-list PR). Plausible-looking addresses invented from memory are the most common bug class.