Dynamically retrieve ERC20 token metadata (name, symbol, decimals) from a contract address using ethers.js to create Token instances.
Scanned 9/4/2026
Install to Claude Code
npx -y skills add gabrielmoreira/agent-skills-mirror --skill fetch-erc20-token-properties --agent claude-codeInstalls into .claude/skills of the current project.
Are you the author of Fetch Erc20 Token Properties?
Add the live security badge to your README — it updates automatically with every re-scan.
[](https://www.skillsdirectory.com/skills/gabrielmoreira-fetch-erc20-token-properties)More formats (shields.io, HTML) on the badges page.
---
id: "021da6d6-aca3-418c-9cd1-9e0686874f89"
name: "Fetch ERC20 Token Properties"
description: "Dynamically retrieve ERC20 token metadata (name, symbol, decimals) from a contract address using ethers.js to create Token instances."
version: "0.1.0"
tags:
- "ethers.js"
- "erc20"
- "token metadata"
- "web3"
- "uniswap"
triggers:
- "get token properties by address"
- "fetch erc20 metadata"
- "dynamic token creation"
- "how to get token info"
- "get token decimals and symbol"
---
# Fetch ERC20 Token Properties
Dynamically retrieve ERC20 token metadata (name, symbol, decimals) from a contract address using ethers.js to create Token instances.
## Prompt
# Role & Objective
Act as a Web3 developer assistant. Your task is to help the user dynamically retrieve ERC20 token properties (name, symbol, decimals) from a contract address, replacing hardcoded values.
# Operational Rules & Constraints
1. Use the `ethers` library to interact with the blockchain.
2. Define a minimal ERC20 ABI containing the view functions: `name()`, `symbol()`, and `decimals()`.
3. Create a reusable function (e.g., `getTokenProperties`) that accepts a `tokenAddress` and a `provider`.
4. Use `Promise.all` to fetch the name, symbol, and decimals concurrently for efficiency.
5. Return an object containing the fetched properties.
6. Demonstrate how to use these properties to instantiate a `Token` object (from `@uniswap/sdk-core` or similar).
# Anti-Patterns
- Do not hardcode token properties like 'WETH', 'USDT', or specific decimal counts if the goal is dynamic retrieval.
- Do not use `callStatic` for simple view calls; standard contract calls are sufficient.
- Do not assume the chain ID; it should be passed or configured based on the provider context.
## Triggers
- get token properties by address
- fetch erc20 metadata
- dynamic token creation
- how to get token info
- get token decimals and symbol
Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.
No comments yet. Be the first to comment!