agentleFS
Sign inStart free
daniilganievdaniilganiev/telegram-dev/skills/deploy-testnet/SKILL.md

deploy-testnet

Skill0 starsChanged 36 days agoMITView on GitHub

Prepare and check a TON testnet deployment of the current Acton project — build, tests and local emulation, then the user broadcasts with the exact command given, then an on-chain check. Pass the script path as an argument (defaults to contracts/scripts/deploy.tolk).

  • Reads credentials

The file

We split this skill into the rules it gives an agent

3 rules. About 0 are common, 1 is distinctive, and 2 are 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.

  • 2

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Follow these steps in order and stop at the first failure, explaining it to the user.

    line 10
  2. Very specific:

    Local emulation: Run acton script <script> without --net.

    line 15
  3. Very specific:

    Never run acton script with --net from this skill.

    line 34

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 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

Deploy to TON testnet

Script to deploy: $ARGUMENTS (if empty, use contracts/scripts/deploy.tolk, where Acton templates put it; if it is missing, list *.tolk files under a scripts folder and ask).

Follow these steps in order and stop at the first failure, explaining it to the user.

  1. Preflight. Confirm this is an Acton project (Acton.toml exists); on Windows, that commands run inside WSL. Run acton build and acton test. Do not continue if tests fail.
  2. Local emulation. Run acton script <script> without --net. Check that the printed address, initial state and post-deploy getters look right.
  3. Wallet check. The script names its wallet (for example scripts.wallet("deployer")); acton wallet list must show that name. If it doesn't, give the user the commands to run in their own terminal: acton wallet new --name deployer --version v5r1 --local (add --secure false in WSL, where there is no native key store and the command waits forever) and acton wallet airdrop deployer for free testnet GRAM, or suggest --tonconnect. The user runs them, so the mnemonic never enters the chat. Never ask for, import or handle a mnemonic: the same phrase controls the mainnet wallet too.
  4. API key. Recommend a TON Center key in the project's .env to avoid 429 errors.
  5. Hand over the broadcast. Claude never sends transactions. Summarise network = testnet, script, wallet and value attached, then give the exact command for the user to run in their own terminal: acton script <script> --net testnet (add --tonconnect if chosen). Wait for them to report back.
  6. Verify on chain. Query the testnet TON Center API (telegram-ton/references/chain-reading.md): the contract's transactions and trace, to confirm it is active and the deploy succeeded.
  7. Report. Give the user the contract address, a testnet explorer link, and next steps (wire the address into the Mini App config, run the security review).

Never run acton script with --net from this skill; the plugin's hook blocks it anyway.

Download now (ZIP)

Does it work?

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

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

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