agentleFS
Sign inStart free
TermiX-officialTermiX-official/cryptoclaw/skills/contract-deployer/SKILL.md

contract-deployer

Skill100 starsChanged 9 months agoMITView on GitHub

Deploy smart contracts (ERC20, ERC721) from templates.

We split this skill into the rules it gives an agent

7 rules. About 0 are common, 7 are distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈7

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Deploy ERC20: Create a new fungible token with custom name, symbol, supply

    line 17
  2. Distinctive:

    Deploy ERC721: Create a new NFT collection

    line 18
  3. Distinctive:

    Verify deployment: Check deployed contract on block explorer

    line 19
  4. Distinctive:

    Contract interaction: Read/write to deployed contracts

    line 20
  5. Distinctive:

    ALWAYS show estimated deployment gas cost before executing

    line 31
  6. Distinctive:

    ALWAYS confirm contract parameters (name, symbol, supply) with user

    line 32
  7. Distinctive:

    Never deploy without explicit confirmation

    line 34

≈ “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

Contract Deployer Skill

Deploy smart contracts (ERC20, ERC721) from templates.

Overview

Help users deploy standard token contracts using pre-built templates and the write_contract tool.

Capabilities

  • Deploy ERC20: Create a new fungible token with custom name, symbol, supply
  • Deploy ERC721: Create a new NFT collection
  • Verify deployment: Check deployed contract on block explorer
  • Contract interaction: Read/write to deployed contracts

Tools Used

  • write_contract - Deploy contract bytecode
  • is_contract - Verify deployment
  • read_contract - Read contract state
  • estimate_gas - Estimate deployment cost

Security Rules

  • ALWAYS show estimated deployment gas cost before executing
  • ALWAYS confirm contract parameters (name, symbol, supply) with user
  • Warn about mainnet deployments (suggest testnet first)
  • Never deploy without explicit confirmation

Example Interactions

User: "Deploy an ERC20 token called MyCoin with 1M supply on BSC" Action: Show deployment parameters, gas estimate, confirm, deploy using ERC20 template

User: "Create an NFT collection on Polygon" Action: Collect name/symbol, show gas estimate, deploy ERC721 template

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.

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