Toronet Smart Contract Deployment
Deploy Solidity smart contracts to ToroNet using toronetdeploy. Use when the user wants ToroNet deployment commands, help configuring owner and constructor args, guidance on network selection, mainnet token requirements, or Foundry remappings needed before deployment.
Install
$ agentstack add skill-toronet-guidl-toronet-agent-skills-toronet-smart-contract-deployment ✓ scanned · ✓ verified, works with Claude Code, Cursor, and more.
Security review
✓ PassedNo issues found. Passed automated security review. · v0.1.0 How review works →
- ✓ Prompt-injection patterns
- ✓ Secret / credential exfiltration
- ✓ Dangerous shell & filesystem operations
- ✓ Untrusted network calls
- ✓ Known-malicious package signatures
What it can access
- ✓ Network access No
- ✓ Filesystem access No
- ✓ Shell / process execution No
- ✓ Environment & secrets No
- ✓ Dynamic code execution No
From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.
Verified badge
Passed review? Show it. Paste this badge into your README, it links to the public security report.
Links to your public security report.[](https://agentstack.voostack.com/security/report/skill-toronet-guidl-toronet-agent-skills-toronet-smart-contract-deployment) Reliability & compatibility
Declared compatibility
Compatibility is declared by the source manifest. End-to-end runtime verification is coming, see below.
We're building live execution health for every listing: tool-call success rate, median latency, uptime, and last-checked timestamps, measured, not self-reported. It isn't live yet, so we don't show numbers we can't stand behind.
How agent discovery & health will work →About
toronet-smart-contract-deployment
When to use
Use this skill when the user wants to:
- deploy a Solidity contract to ToroNet
- get the correct
toronetdeploycommand or library usage - pass
--owner,--args, or--network - deploy from a Foundry project and configure remappings
- understand when
--tokenis required - troubleshoot ToroNet-specific deployment issues
Do not use this skill for writing the contract itself, frontend integration, or general SDK usage unless directly required to complete a ToroNet deployment task.
Instructions
- Treat
toronetdeployas the default ToroNet deployment path and support both CLI (npx toronetdeploy) and library usage (deployContract). - For CLI usage, make sure the user provides the Solidity file path, contract name, owner address, constructor arguments if needed, and target network.
- For library usage, use the same fields as options and show CommonJS or ESM imports when requested.
- Default the network to
testnetunless the user explicitly asks for mainnet. - If the user is deploying to mainnet, mention that
--tokenis required and is obtained from the ToroNet team. - If the contract comes from a Foundry project, make sure imports and remappings are properly configured in
foundry.tomlbefore deployment. - Prefer copyable commands or code samples.
- If the user provides incomplete deployment details, preserve the ToroNet deployment pattern and show a realistic template with placeholders.
- Keep the answer focused on deployment unless the user explicitly asks for contract design or integration help.
Default workflow
- Identify the contract file and contract name.
- Confirm the owner address.
- Determine whether constructor arguments are required and the target network.
- Determine whether the user wants CLI or library usage.
- Check whether the contract comes from a Foundry project; if so, remind the user to verify remappings in
foundry.toml. - Produce the correct
toronetdeploycommand ordeployContractusage and add only the ToroNet-specific notes needed for successful deployment.
Checks
- file path and contract name are correct
- owner address is present
- constructor args are correctly formatted
- network is set correctly
- mainnet deployment includes
--token - Foundry imports/remappings are configured before deployment
See [the reference guide](references/REFERENCE.md) for the deployment workflow, command patterns, common checks, and ToroNet-specific deployment notes.
If the user is deploying from a Foundry project, also review: assets/foundry.toml.example
Source & license
This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.
- Author: toronet-guidl
- Source: toronet-guidl/toronet-agent-skills
- License: MIT
Install and usage instructions live in the source repository linked above.
Reviews
No reviews yet, be the first.
Write a review
Versions
- v0.1.0 Imported from the upstream source.