How do I install the Solidity Lsp skill?

Run npx skillmds@latest add modbender/solidity-lsp in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Solidity Lsp safe to use?

This skill has not completed SkillMD's automated safety review yet. Independent scanners report: SkillSpector: PASS, Skill Scanner: PASS. Capability flags: makes network calls. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Solidity Lsp?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Solidity Lsp free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Solidity Lsp?

modbender (@modbender) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Solidity Lsp by modbender — Agent Skill

Name: Solidity Lsp
Rating: 4.5 (4 reviews)
Author: modbender

Solidity Lsp

Solidity language server providing smart contract development support including compilation, linting, security analysis, and code intelligence for .sol files. Use when working with Ethereum smart contracts, Substrate pallets, or any Solidity code that needs compilation, security checks, gas optimization, or code navigation. Essential for ClawChain pallet development.

modbender Updated Sep 9, 2026 12 repo stars

File contents

Solidity LSP

Solidity language server integration providing comprehensive smart contract development support through solc (Solidity compiler) and solhint (linter).

Capabilities

Compilation: Compile Solidity smart contracts with solc
Linting: Static analysis with solhint for best practices and security
Security: Detect common vulnerabilities (reentrancy, overflow, etc.)
Gas optimization: Identify expensive operations
Code intelligence: Syntax highlighting, error detection
Supported extensions: .sol

Installation

Install Solidity compiler and linter:

# Solidity compiler
npm install -g solc

# Solidity linter
npm install -g solhint

Verify installation:

solcjs --version
solhint --version

Usage

Compile Solidity Contract

solcjs --bin --abi contract.sol

Compile with optimization:

solcjs --optimize --bin --abi contract.sol

Lint Contract

Run solhint on a file:

solhint contracts/MyContract.sol

Run on entire project:

solhint 'contracts/**/*.sol'

Security Analysis

solhint includes security rules by default. For advanced security analysis, consider:

# Install slither (requires Python)
pip3 install slither-analyzer

# Run security analysis
slither contracts/

Configuration

solhint Configuration

Create .solhint.json in project root:

{
  "extends": "solhint:recommended",
  "rules": {
    "compiler-version": ["error", "^0.8.0"],
    "func-visibility": ["warn", {"ignoreConstructors": true}],
    "max-line-length": ["warn", 120],
    "not-rely-on-time": "warn",
    "avoid-low-level-calls": "warn",
    "no-inline-assembly": "warn"
  }
}

Hardhat/Foundry Integration

For full development environments, see references/frameworks.md.

Integration Pattern

When developing smart contracts:

Write: Edit Solidity code
Lint: Run solhint to catch issues early
Compile: Use solcjs to verify compilation
Analyze: Run security tools before deployment
Test: Write comprehensive unit tests

Common Issues

Compiler version mismatch: Specify pragma version in contract
Gas optimization: Use view/pure where possible
Security: Never use tx.origin for authentication
Best practices: Follow Checks-Effects-Interactions pattern

More Information

Solidity Documentation
Solhint GitHub
Solidity Security Best Practices
See references/frameworks.md for Hardhat/Foundry setup

---name: solidity-lspdescription: Solidity language server providing smart contract development support including compilation, linting, security analysis, and code intelligence for .sol files. Use when working with Ethereum smart contracts, Substrate pallets, or any Solidity code that needs compilation, security checks, gas optimization, or code navigation. Essential for ClawChain pallet development.--- # Solidity LSP Solidity language server integration providing comprehensive smart contract development support through solc (Solidity compiler) and solhint (linter). ## Capabilities - **Compilation**: Compile Solidity smart contracts with solc - **Linting**: Static analysis with solhint for best practices and security - **Security**: Detect common vulnerabilities (reentrancy, overflow, etc.) - **Gas optimization**: Identify expensive operations - **Code intelligence**: Syntax highlighting, error detection - **Supported extensions**: `.sol` ## Installation Install Solidity compiler and linter: ```bash # Solidity compiler npm install -g solc # Solidity linter npm install -g solhint ``` Verify installation: ```bash solcjs --version solhint --version ``` ## Usage ### Compile Solidity Contract ```bash solcjs --bin --abi contract.sol ``` Compile with optimization: ```bash solcjs --optimize --bin --abi contract.sol ``` ### Lint Contract Run solhint on a file: ```bash solhint contracts/MyContract.sol ``` Run on entire project: ```bash solhint 'contracts/**/*.sol' ``` ### Security Analysis solhint includes security rules by default. For advanced security analysis, consider: ```bash # Install slither (requires Python) pip3 install slither-analyzer # Run security analysis slither contracts/ ``` ## Configuration ### solhint Configuration Create `.solhint.json` in project root: ```json { "extends": "solhint:recommended", "rules": { "compiler-version": ["error", "^0.8.0"], "func-visibility": ["warn", {"ignoreConstructors": true}], "max-line-length": ["warn", 120], "not-rely-on-time": "warn", "avoid-low-level-calls": "warn", "no-inline-assembly": "warn" } } ``` ### Hardhat/Foundry Integration For full development environments, see `references/frameworks.md`. ## Integration Pattern When developing smart contracts: 1. **Write**: Edit Solidity code 2. **Lint**: Run `solhint` to catch issues early 3. **Compile**: Use `solcjs` to verify compilation 4. **Analyze**: Run security tools before deployment 5. **Test**: Write comprehensive unit tests ## Common Issues - **Compiler version mismatch**: Specify pragma version in contract - **Gas optimization**: Use `view`/`pure` where possible - **Security**: Never use `tx.origin` for authentication - **Best practices**: Follow Checks-Effects-Interactions pattern ## More Information - [Solidity Documentation](https://docs.soliditylang.org/) - [Solhint GitHub](https://github.com/protofire/solhint) - [Solidity Security Best Practices](https://consensys.github.io/smart-contract-best-practices/) - See `references/frameworks.md` for Hardhat/Foundry setup

Frequently asked questions