agentleFS
Sign inStart free
kukapaykukapay/crypto-skills/skills/token-minter/SKILL.md

token-minter

Skill36 starsChanged 10 months agoMITView on GitHub

Generate, build, and deploy custom ERC20 tokens on EVM networks. Use when users want to create and deploy their own ERC20 tokens with custom parameters like name, symbol, decimals, and initial supply. Supports deployment to various networks including Sepolia testnet and requires Foundry (forge/cast) for blockchain interactions.

The file

We split this skill into the rules it gives an agent

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈3

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 3

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Use the provided script to generate the ERC20 contract code based on user parameters.

    line 23
  2. Very specific:

    Run python scripts/generate_contract.py <name> <symbol> <decimals> <initial_supply> to generate the contract

    line 24
  3. Very specific:

    Create a temporary directory under ./tmp/

    line 28
  4. Very specific:

    Place the generated contract in src/Contract.sol

    line 30
  5. Distinctive:

    Ensure a local cast wallet is created (prerequisite)

    line 37
  6. Distinctive:

    Verify deployment on the target network

    line 42

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

Token Minter

Overview

This skill enables users to create custom ERC20 tokens by collecting parameters, generating Solidity code, setting up a Foundry project, building the contract, and deploying to a target EVM network.

Workflow

Step 1: Collect Information

Collect the following parameters from the user:

  • Token name (e.g., "MyToken")
  • Token symbol (e.g., "MTK")
  • Decimals (default: 18)
  • Initial supply (default: 1000000)
  • Target network (default: sepolia)

Step 2: Generate ERC20 Contract

Use the provided script to generate the ERC20 contract code based on user parameters.

  • Run python scripts/generate_contract.py <name> <symbol> <decimals> <initial_supply> to generate the contract
  • The generated contract uses OpenZeppelin ERC20 standard

Step 3: Initialize Forge Project

  • Create a temporary directory under ./tmp/
  • Initialize a new Foundry project: forge init
  • Place the generated contract in src/Contract.sol

Step 4: Build Contract

  • Install dependencies: forge install OpenZeppelin/openzeppelin-contracts
  • Build the contract: forge build

Step 5: Deploy to Network

  • Ensure a local cast wallet is created (prerequisite)
  • Get RPC URL for target network from https://chainlist.org/rpcs.json
  • Deploy using: forge create --rpc-url <network_rpc> --account <account_name> src/Contract.sol:MyToken --constructor-args <initial_supply> --broadcast
  • Verify deployment on the target network

Prerequisites

  • Foundry installed (forge, cast commands available)
  • Local cast wallet created with cast wallet new
  • Sufficient funds on the deployment account for gas fees

Resources

scripts/

  • generate_contract.py: Python script to generate ERC20 contract code with custom parameters

references/

  • erc20_guide.md: Overview of ERC20 standard, required functions, events, and deployment considerations

assets/

  • ERC20Template.sol: Template Solidity file for ERC20 contract generation

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