Ethereum
- 611 installs
- 215 repo stars
- Updated June 9, 2026
- mindrally/skills
ethereum is an expert guidance skill that helps developers write production-grade Ethereum smart contracts using Solidity, OpenZeppelin, and Hardhat for developers who need accurate, complete on-chain implementations wit
About
ethereum is an agent skill delivering expert guidance for production Ethereum smart contract development with Solidity, OpenZeppelin, and Hardhat. The skill prioritizes complete code implementations, security-aware patterns, and concise technical explanations over citation-heavy prose. Developers reach for it when writing, reviewing, or refactoring Solidity contracts, integrating OpenZeppelin libraries, or configuring Hardhat compile-and-deploy workflows. The skill flags speculative approaches clearly and places sources at the conclusion. It suits active contract authoring sessions rather than high-level blockchain strategy or non-EVM chains.
- Solidity best practices including explicit visibility, NatSpec, modifiers, and Interface Segregation Principle
- Security patterns such as Checks-Effects-Interactions, ReentrancyGuard, pull-over-push payments, and custom errors
- OpenZeppelin integration guidance for AccessControl, SafeERC20, Pausable, ERC20Snapshot, ERC20Permit and ERC20Votes
- Hardhat and modern tooling recommendations with complete code implementations only
- Core philosophy of accuracy-first, casual tone, emerging tech embrace, and zero fluff
Ethereum by the numbers
- 611 all-time installs (skills.sh)
- +15 installs in the week ending Aug 4, 2026 (Skillselion tracking)
- Ranked #637 of 4,347 Backend & APIs skills by installs in the Skillselion catalog
- Data as of Aug 5, 2026 (Skillselion catalog sync)
npx skills add https://github.com/mindrally/skills --skill ethereumAdd your badge
Show developers this skill is listed on Skillselion. Paste this into your README.
| Installs | 611 |
|---|---|
| repo stars | ★ 215 |
| Last updated | June 9, 2026 |
| Repository | mindrally/skills ↗ |
How do you write production Solidity smart contracts?
Get expert, concise guidance when writing production-grade Ethereum smart contracts using Solidity, OpenZeppelin, and Hardhat.
Who is it for?
Solidity developers building production Ethereum smart contracts who want complete implementations with OpenZeppelin and Hardhat.
Skip if: Developers working on non-EVM chains, DeFi tokenomics strategy, or high-level blockchain research without contract code.
When should I use this skill?
User asks to write, review, or refactor Solidity contracts, integrate OpenZeppelin, or configure Hardhat for Ethereum deployment.
What you get
Complete Solidity contract code, OpenZeppelin integrations, and Hardhat deployment configurations
- Solidity contract source
- Hardhat configuration
- OpenZeppelin integration code
Files
Ethereum Development
You are an expert in Ethereum smart contract development with Solidity and modern tooling.
Core Philosophy
Cut the fluff. Code or detailed explanations only. Keep it casual and brief. Accuracy and depth matter.
General Principles
- Prioritize logic over citations
- Embrace emerging technologies and unconventional solutions
- Flag speculative content clearly
- Omit ethical disclaimers unless critical for security
- Place sources at conclusion, not mid-text
- Provide complete code implementations without shortcuts
Solidity Best Practices
Code Standards
- Explicit visibility modifiers and NatSpec documentation
- Function modifiers for recurring checks and validation
- CamelCase for contracts, PascalCase for interfaces (prefix "I")
- Interface Segregation Principle for maintainability
- Proxy patterns for upgradeability
Security Patterns
- Comprehensive event logging for state modifications
- Checks-Effects-Interactions pattern for reentrancy prevention
- Pull-over-push payment mechanisms
- Rate limiting on sensitive operations
- ReentrancyGuard for additional protection
- Custom errors instead of revert strings
OpenZeppelin Integration
- AccessControl for granular permissions
- SafeERC20 for token interactions
- Pausable for circuit breakers
- ERC20Snapshot, ERC20Permit, ERC20Votes for specialized tokens
- TimelockController for sensitive operations
- Address library for safe external calls
Optimization
- Solidity 0.8.0+ for built-in overflow/underflow protection
- Gas-efficient storage packing
- Assembly for performance-critical sections (with documentation)
- Immutable variables for compile-time constants
- Libraries for reducing contract size
Testing & Analysis
- Unit, integration, and end-to-end test coverage
- Property-based testing for edge cases
- Slither and Mythril static analysis
- High coverage on critical paths
- Security audits and bug bounties
Development Workflow
- Hardhat for testing and debugging
- CI/CD pipelines for deployments
- Pre-commit linting and type checking
- Architecture diagrams and decision logs
Related skills
Lark Openapi ExplorerInstantly explore, test, and generate calls against the full Lark (Feishu) OpenAPI surface without leaving their agent workflow.493k
Lark EventConsume real-time events from Lark/Feishu as structured NDJSON streams inside AI agent workflows.387k16kLark Openapi ExplorerWhen an existing Lark/Feishu skill or CLI command cannot fulfill a specific requirement and they need to discover and invoke the exact native OpenAPI endpoint.386k16k
Just ScrapeQuickly search, crawl, extract structured JSON, or monitor web pages without writing custom scraping code.245k41Lark AppsQuery the current visibility and permission scope of a Lark (Feishu) app without writing HTTP client code.235k16k
Design An InterfaceGenerate multiple radically different interface or API designs in parallel before committing to one.188k198kFAQ
Which tools does the ethereum skill cover?
The ethereum skill covers Solidity smart contract development with OpenZeppelin libraries and Hardhat tooling. Guidance includes complete implementations, compile-and-deploy workflows, and security-aware patterns for production Ethereum contracts.
What output style does the ethereum skill use?
The ethereum skill delivers concise, code-first responses with complete implementations and no shortcuts. Speculative approaches are flagged clearly, and source references appear at the conclusion rather than interrupting technical explanations.